Actions27
- App Actions
- Account Actions
- Channel Actions
- Message Actions
- Template Actions
- Contact Actions
- Chat Actions
- Tag Actions
- User Actions
- Team Actions
- Webhook Actions
Template → Send Template Message By Contact ID
AI-generatedOverview
This node operation sends a template message to a specific contact identified by their Contact UUID using the Poli API. It is useful for automating communication with contacts by sending predefined message templates, which can include dynamic header and body parameters. For example, a business can send appointment reminders or promotional messages to customers using this operation.
Use Case Examples
- Sending a promotional template message to a customer by specifying their Contact UUID, the account channel UUID, and the template UUID, along with any required header and body parameters.
- Automating customer notifications by sending template messages triggered by events in a workflow.
Properties
| Name | Meaning |
|---|---|
| Contact UUID | The unique identifier of the contact to whom the template message will be sent. |
| Account Channel UUID | The unique identifier of the account channel through which the message will be sent. |
| Template UUID | The unique identifier of the message template to be used for sending the message. |
| Header Parameters | Optional parameters to customize the header of the template message. Each parameter has a type (Text or Date/Time) and a value. |
| Body Parameters | Optional parameters to customize the body of the template message. Each parameter has a type (Text or Date/Time) and a value. |
Output
JSON
messageId- The unique identifier of the sent message.status- The status of the message sending operation (e.g., sent, failed).timestamp- The timestamp when the message was sent.
Dependencies
- Poli API with appropriate API key credentials
Troubleshooting
- Ensure that the Contact UUID, Account Channel UUID, and Template UUID are correctly provided and valid; missing or incorrect IDs will cause errors.
- Verify that the API credentials are correctly configured and have the necessary permissions to send template messages.
- Check the format and types of header and body parameters; incorrect types or malformed values may cause the message sending to fail.
- Common error messages include resource or operation not found errors if the resource or operation parameters are incorrect, and execution errors if the API call fails. These can be resolved by verifying the input parameters and API connectivity.