Actions31
- Conversation Actions
- Message Actions
- Visitor Actions
- Contact Actions
- Bot Actions
- Operator Actions
Message → Send Message
AI-generatedOverview
The node enables sending messages within a conversation in the Tidio live chat platform. It supports various message types including text, card, quick reply, file, and image messages. This node is useful for automating customer engagement by programmatically sending messages to visitors or customers during active conversations. For example, it can be used to send personalized greetings, automated bot responses, file attachments, or interactive quick reply buttons to enhance communication efficiency.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The unique identifier of the conversation where the message will be sent. |
| Message Type | The type of message to send. Options: Text, Card, Quick Reply, File, Image. |
| Message Text | The textual content of the message to send. |
| Additional Fields | Optional extra fields to customize the message or conversation context, including: |
| - Visitor Name | Name of the visitor involved in the conversation. |
| - Visitor Email | Email address of the visitor. |
| - Visitor Phone | Phone number of the visitor. |
| - Tags | Comma-separated list of tags related to the conversation. |
| - Tag Name | Name of a tag to add or remove from the conversation. |
| - Custom Properties | JSON object with custom properties to attach. |
| - Contact Name | Full name of the contact associated with the conversation. |
| - Contact Email | Email address of the contact. |
| - Contact Phone | Phone number of the contact. |
| - Mailing List ID | Identifier of a mailing list to add contacts to. |
| - Bot Flow ID | Identifier of a bot flow to trigger in the conversation. |
| - Status | Operator status options: Online, Offline, Away. |
| - Department | Department name or ID related to the conversation. |
| - Priority | Priority level of the conversation. Options: Low, Normal, High, Urgent. |
| - Limit | Maximum number of results to return (used in some operations). |
| - Offset | Number of results to skip (used in some operations). |
| - Auto Reply | Boolean flag to enable automatic replies. |
| - Send As Bot | Boolean flag to send the message as a bot rather than an operator. |
Output
The node outputs a JSON object representing the response from the Tidio API after sending the message. This typically includes details about the sent message such as its ID, content, type, timestamps, and sender information. If the operation fails, the output contains an error message describing the issue.
If binary data (such as files or images) is sent, the node does not output the binary content itself but handles the file via URL references.
Dependencies
- Requires an API key credential for authenticating with the Tidio API.
- Needs configuration of API URL, client ID, and client secret credentials for access.
- Uses an external proxy service endpoint (
https://n8ntools.io/api/v1/proxy/tidio) to forward requests to the Tidio API. - Requires internet connectivity to communicate with the Tidio API endpoints.
Troubleshooting
Common Issues:
- Invalid or missing conversation ID will cause failures when attempting to send messages.
- Incorrect API credentials or expired tokens will result in authentication errors.
- Sending unsupported message types or malformed JSON in custom properties may cause request rejections.
- Network issues or proxy service downtime can prevent successful API calls.
Error Messages:
"Unknown message operation": Indicates an unsupported or misspelled operation was selected.- Authentication errors usually mention invalid credentials or unauthorized access.
- Validation errors may indicate missing required parameters like
conversationIdormessageText.
Resolutions:
- Verify all required input fields are correctly filled.
- Ensure API credentials are valid and have necessary permissions.
- Check network connectivity and proxy service availability.
- Validate JSON syntax in custom properties before use.