N8N Tools - Tidio API icon

N8N Tools - Tidio API

Complete Tidio integration - Live chat, AI chatbots, and customer engagement

Actions31

Message → Send Automated Message

AI-generated

Overview

The node integrates with the Tidio API to send automated messages within a specified conversation. It allows sending various types of messages such as text, cards, quick replies, files, and images automatically, typically used in chatbot workflows or customer engagement automation. This is beneficial for scenarios like triggering bot responses, sending follow-up messages, or automating communication without manual intervention.

For example, you can use this node to automatically send a welcome message when a new conversation starts or trigger a predefined bot flow message based on visitor actions.

Properties

Name Meaning
Conversation ID The unique identifier of the conversation where the automated 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 be sent.
Additional Fields A collection of optional fields to customize the message or related data:
- Visitor Name Name of the visitor associated with the message.
- Visitor Email Email address of the visitor.
- Visitor Phone Phone number of the visitor.
- Tags Comma-separated list of tags related to the conversation or message.
- Tag Name Name of a tag to add or remove (used in other operations).
- Custom Properties JSON object containing custom properties to attach.
- Contact Name Full name of the contact related to the message.
- Contact Email Email address of the contact.
- Contact Phone Phone number of the contact.
- Mailing List ID Identifier of a mailing list (used in other operations).
- Bot Flow ID Identifier of the bot flow to trigger.
- 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 listing operations).
- Offset Number of results to skip (used in listing operations).
- Auto Reply Boolean flag to enable automatic replies (used in bot settings).
- Send As Bot Boolean flag indicating if the message should be sent as a bot rather than an operator.

Output

The node outputs a JSON object representing the response from the Tidio API after sending the automated message. This includes details about the message sent, such as its ID, content, type, timestamps, and any metadata returned by the API.

If the operation involves sending files or images, the output confirms the successful upload and message creation but does not directly output binary data.

Example output structure (simplified):

{
  "id": "message_id",
  "conversation_id": "conversation_id",
  "type": "text",
  "content": "Your automated message text",
  "from": "bot",
  "created_at": "timestamp"
}

Dependencies

  • Requires an API key credential for authenticating with the Tidio API.
  • Needs configuration of API URL, client ID, and client secret credentials.
  • Uses HTTP requests to communicate with the Tidio API endpoints.
  • No direct binary data handling; file URLs must be accessible externally.

Troubleshooting

  • Common Issues:

    • Invalid or missing conversation ID will cause the API to reject the request.
    • Incorrect API credentials or expired tokens will result in authentication errors.
    • Sending file or image messages requires a valid publicly accessible file URL.
    • Improperly formatted JSON in custom properties may cause parsing errors.

  • Error Messages:

    • "Unknown message operation": Indicates an unsupported operation was selected; verify the operation name.
    • "Unknown resource": The resource parameter is invalid or not supported.
    • Authentication errors usually mention invalid credentials or unauthorized access; check API keys and secrets.
    • Network or timeout errors suggest connectivity issues with the Tidio API endpoint.

  • Resolutions:

    • Double-check all required parameters, especially conversation ID and message content.
    • Ensure API credentials are correctly set up in n8n.
    • Validate JSON syntax in custom properties before input.
    • Confirm that file URLs are reachable and properly formatted.

Links and References

Discussion