Ant Text Automation (Preview)
Sends an Ant Text Template from your email account, when triggered. You can use data provided by your flow, as merge fields in your template.
This connector is available in the following products and regions:
| Service | Class | Regions |
|---|---|---|
| Logic Apps | Standard | All Logic Apps regions except the following: - Azure Government regions - Azure China regions - US Department of Defense (DoD) |
| Power Automate | Premium | All Power Automate regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Power Apps | Premium | All Power Apps regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Contact | |
|---|---|
| Name | Ant Text Support |
| URL | https://www.anttext.com/contact |
| support@anttext.com |
| Connector Metadata | |
|---|---|
| Publisher | Insight Office |
| Website | https://www.anttext.com |
| Privacy policy | https://anttext.com/privacy |
| Categories | Communication;Website |
Introduction
Ant Text Automation empowers you to seamlessly access your Ant Text Email Templates within Power Automate Flows. Send your customized email templates created in the Ant Text Add-in in Outlook directly from within your Power Automate Flow. This capability streamlines your automation processes involving email communication, enabling you to deploy your meticulously crafted templates with Ant Text Email Templates, akin to Outlook. The primary advantage lies in automated processes and the use of email templates without doing any code, offering significant time savings for your business operations.
Prerequisites
You will need the following to proceed:
- Ant Text Business Subscription
- Email associated with Ant Text Business subscription
- Ant Text Business License Key Number
- Give consent in your Outlook client to Ant Text
- Key Phrase to send emails using the connector
NOTE! For pricing refer to Ant Text Pricing Page
How to get credentials
To obtain the credentials necessary for using the Ant Text Automation connector, follow these steps:
- Purchase Ant Text Business Subscription: Ensure you have an active Ant Text Business subscription. If you haven't subscribed yet, you can sign up for a 30-day trial through Microsoft AppSource.
- Associate Your Email: After purchasing the Ant Text Business subscription, your email will be automatically associated with it.
- Receive License Key: Upon subscription, you will receive a license key number via email. This key is essential for activating and using the connector.
- Obtain KeyPhrase: In the email containing your license key, you will also receive a KeyPhrase. This KeyPhrase is required for sending emails using the connector.
- Installation Consent: Give consent in your Outlook client to Ant Text. This step ensures seamless integration between Ant Text and Outlook, enabling efficient email communication.
By following these steps, you'll be equipped with the necessary credentials to utilize the Ant Text Automation connector effectively in your Power Automate workflows.
Get started with your connector
To begin using the Ant Text Automation connector effectively, follow these steps:
- Acquire Credentials: Ensure you have the necessary credentials to use the connector. This includes your Ant Text Business Subscription, License Key, and Key Phrase. These credentials are essential for authentication and accessing your Ant Text Email Templates. Refer to the "How to get credentials" section.
- Explore Pre-made Email Templates and create one of your own: You have access to pre-existing demo templates within Outlook after installation, allowing you to focus solely on testing the main product right away. This is not the case for the connector. To use templates with Ant Text Automation you must first create your own template manually. One way to fast forward this process is to copy-paste the demo template to an empty template you started creating. Please refer to point 5 for further instructions.
- Configure Your Flow: In Power Automate Designer, begin by selecting a trigger of your choice for your flow as the starting point. Ant Text Automation must be integrated as a step within your flow for automated email sending. Ensure that you are familiar with the concept of "Merge Fields" within Ant Text Email Templates Add-in (Read more about Merge Fields), as they play a crucial role in personalizing your emails. Please refer to point 5 for further instructions.
- Configuring the Connector: In Power Automate Designer add a new step to your flow and search for the "Ant Text Automation" connector. Add it and follow on screen instructions. Fill in the required fields at the minimum save the flow and run your first test with a trigger of choice.
- Important Further Reading: For additional information and resources.
Familiarize yourself with our main product to maximize the benefits of the connector.
If you have any questions or require assistance, feel free to reach out to our support team via email support@anttext.com
Known Issues and Limitations
While using the Ant Text Automation connector, please be aware of the following known issues and limitations:
- Functionality Scope: Currently, the Ant Text Automation connector only supports sending emails. We are continuously working to expand the functionality of the connector to provide more features in future releases.
- Merge Fields Constraints: Merge fields within the connector can only accept string values, and they are limited to a maximum of 20 fields per email template. Ensure that your merge fields are formatted correctly, and that the data provided matches the expected string format.
- Manual Configuration: If necessary, manual configuration of the connector is possible and may require technical expertise, especially when deploying it as a custom connector. Ant Text Automation is open sourced on GitHub in Microsoft's PowerPlatformConnectors repository. Follow the provided deployment instructions carefully to avoid any configuration errors.
- Merge Field Substitution: If merge fields are specified in the email template but not filled within the connector, they will remain in the original format within the sent email. This might result in unexpected outcomes if not managed properly.
- Compatibility Issues: Ensure compatibility between your Power Automate Flow and the Ant Text Automation connector. Compatibility issues may arise if your flow design or data sources are not aligned with the connector's requirements.
- Dependency on Ant Text Business Subscription: The connector requires a valid Ant Text Business subscription and associated email for authentication. Without these credentials, you will not be able to use the connector effectively.
Common Errors and Remedies
Here are some common errors that you may encounter while using the Ant Text Automation connector, along with their remedies:
- Authentication Failure: If you encounter authentication failure, double-check your Ant Text Business subscription email and license key/API key. Ensure that the credentials provided are accurate and entered correctly in the connector configuration.
- Merge Field Mismatch: If the merge fields specified in your email template do not match the merge fields filled within the connector, the email may not be sent as expected. Verify that the merge fields are correctly mapped and filled with the appropriate data.
- Connector Unavailability: If the connector is not available in your Power Automate environment or if you encounter connectivity issues, ensure that the connector is properly deployed and enabled. Refer to the deployment instructions for manual deployment or contact support for assistance.
- Template Selection Error: If you are unable to select an email template from the drop-down list within the connector configuration, ensure that you have the necessary permissions and that the templates are properly configured in your Ant Text Email Templates Add-in in Outlook.
- Unexpected Behaviour: If you experience any unexpected behaviour or errors while using the connector, as a first check, make sure that your Ant Text Add-in in Outlook is working as Expected. Ant Text Add-in needs consent to operate, if that is not done, you will get all sorts of errors and misbehaviour. Please reach out to our support team for further assistance. Provide detailed information about the issue encountered, including any error messages and screenshots, if possible, for prompt resolution.
FAQ
1. What are the common use cases for the connector?
Common use cases for the Ant Text Automation connector include automated email notifications, personalized customer communications, and email marketing campaigns. Users can leverage the connector to streamline repetitive email tasks and improve communication efficiency within their workflows.
2. How can I troubleshoot common errors encountered while using the connector?
If you encounter common errors such as authentication failure or merge field mismatch, double-check your credentials and ensure proper configuration of merge fields. Refer to the troubleshooting section in the documentation for detailed guidance on resolving common errors and issues.
3. Can I use the connector without a paid subscription?
No, the Ant Text Automation connector requires a valid Ant Text Business subscription for authentication and access to email templates. Without an Ant Text Business subscription, you will not be able to use the connector effectively.
4. How can I get further assistance or support?
If you have further questions or need assistance, you can reach out to our support team via email. Our team is dedicated to providing prompt assistance and ensuring a smooth experience with the Ant Text Automation connector.
5. What are Merge Fields and how do they work?
Merge Fields are placeholders within email templates that allow for dynamic content insertion, enabling personalized communication with recipients. In the context of the Ant Text Automation connector, Merge Fields play a crucial role in customizing email templates sent through Power Automate Flows or Outlook. In short, here's how they work:
- Definition: Merge Fields are anchor points within email templates created using the Ant Text Email Templates Add-in. These placeholders are identified by specific syntax, typically enclosed within square brackets, such as
[#MergeFieldName#],[#MergeFieldUser#]etc. - Customization: Users can create and edit email templates within the Ant Text Email Templates Outlook Add-in, inserting Merge Fields to represent dynamic content elements. For example, a Merge Field might represent the recipient's name, company, or any other variable data.
- Connector Integration: When configuring the Ant Text Automation connector within Power Automate, users map Merge Fields from their email templates to corresponding data sources or variables in their flow. During execution, the connector substitutes these Merge Fields with actual data, personalizing each email sent. Email Templates that are going to be used with the Ant Text Automation connector, must follow the exact naming for Merge Fields when typing them into it
- Naming Conventions for Merge Fields: When creating Email Templates for use with the Ant Text Automation connector, it's essential to adhere to specific naming conventions for Merge Fields. The pattern for naming them follows the format
[#FlowFieldN#], whereNrepresents a number from 1 to 20. These placeholders must be accurately named within the email template to match the corresponding Merge Fields inputted into the connector. Ensuring consistency in naming between the email template and the connector configuration is vital for seamless integration and accurate data substitution during email sending.
By leveraging Merge Fields, users can create dynamic and personalized email templates, enhancing communication effectiveness and engagement with recipients.
Creating a connection
The connector supports the following authentication types:
| Default | Parameters for creating connection. | All regions | Not shareable |
Default
Applicable: All regions
Parameters for creating connection.
This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.
| Name | Type | Description | Required |
|---|---|---|---|
| API Key | securestring | Ant Text Business License Key | True |
Throttling Limits
| Name | Calls | Renewal Period |
|---|---|---|
| API calls per connection | 100 | 60 seconds |
Actions
| Send Ant Text Email |
Sends an Ant Text Template from your email account when triggered. You can use data from your flow as merge fields in your template |
Send Ant Text Email
Sends an Ant Text Template from your email account when triggered. You can use data from your flow as merge fields in your template
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Email for Ant Text Business
|
AntTextOwner | True | string |
User Email for Ant Text Business subscription and "from" field |
|
Ant Text License Key
|
AntTextLicenseKey | True | string |
Confirm Your License Key for Ant Text Business subscription |
|
Key Phrase
|
CalledFrom | True | string |
Confirm Ant Text Key Phrase |
|
Choose Ant Text Template
|
TemplateID | True | string |
Select a template (Enter the Ant Text owner and LicenseKey above, before selecting a template) |
|
To
|
To | True | string |
The email address to send to |
|
Save a copy to "Sent Items"
|
SaveCopyToSentItems | string |
Save copy to sent items |
|
|
Importance
|
Importance | string |
Importance |
|
|
FlowField1
|
FlowField1 | string |
[#FlowField1#] |
|
|
FlowField2
|
FlowField2 | string |
[#FlowField2#] |
|
|
FlowField3
|
FlowField3 | string |
[#FlowField3#] |
|
|
FlowField4
|
FlowField4 | string |
[#FlowField4#] |
|
|
FlowField5
|
FlowField5 | string |
[#FlowField5#} |
|
|
FlowField6
|
FlowField6 | string |
[#FlowField6#] |
|
|
FlowField7
|
FlowField7 | string |
[#FlowField7#] |
|
|
FlowField8
|
FlowField8 | string |
[#FlowField8#] |
|
|
FlowField9
|
FlowField9 | string |
[#FlowField9#] |
|
|
FlowField10
|
FlowField10 | string |
[#FlowField10#] |
|
|
FlowField11
|
FlowField11 | string |
[#FlowField11#] |
|
|
FlowField12
|
FlowField12 | string |
[#FlowField12#] |
|
|
FlowField13
|
FlowField13 | string |
[#FlowField13#] |
|
|
FlowField14
|
FlowField14 | string |
[#FlowField14#] |
|
|
FlowField15
|
FlowField15 | string |
[#FlowField15#] |
|
|
FlowField16
|
FlowField16 | string |
[#FlowField16#] |
|
|
FlowField17
|
FlowField17 | string |
[#FlowField17#] |
|
|
FlowField18
|
FlowField18 | string |
[#FlowField18#] |
|
|
FlowField19
|
FlowField19 | string |
[#FlowField19#] |
|
|
FlowField20
|
FlowField20 | string |
[#FlowField20#] |
|
|
Include Ant Text signature
|
IncludeAntTextSignature | string |
Include Ant Text signature |
Returns
- response
- string
Definitions
string
This is the basic data type 'string'.