N8N Tools - Tidio API icon

N8N Tools - Tidio API

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

Message → Get Messages

AI-generated

Overview

The node integrates with the Tidio API to manage chat conversations and messages within n8n workflows. Specifically, the Get Messages operation under the Message resource retrieves messages from a specified conversation. This is useful for scenarios where you want to fetch chat history or analyze message content programmatically.

Practical examples include:

  • Extracting all messages from a customer support chat to analyze conversation quality.
  • Archiving chat messages for compliance or record-keeping.
  • Triggering downstream automation based on specific message content retrieved.

Properties

Name Meaning
Conversation ID The unique identifier of the conversation from which to retrieve messages (required).
Additional Fields Optional parameters to customize the request:
- Limit Maximum number of messages to return (default 50).
- Offset Number of messages to skip before starting to collect results (default 0).

Output

The output is a JSON object containing the response from the Tidio API endpoint that returns messages for the specified conversation. The structure typically includes an array of message objects with details such as message content, type, sender info, timestamps, and any metadata provided by Tidio.

No binary data output is produced by this operation.

Example output snippet (simplified):

{
  "messages": [
    {
      "id": "msg_123",
      "type": "text",
      "content": "Hello, how can I help you?",
      "from": "operator",
      "timestamp": "2024-01-01T12:00:00Z"
    },
    {
      "id": "msg_124",
      "type": "text",
      "content": "I have a question about my order.",
      "from": "visitor",
      "timestamp": "2024-01-01T12:01:00Z"
    }
  ],
  "limit": 50,
  "offset": 0,
  "total": 100
}

Dependencies

  • Requires an API key credential for authenticating with the Tidio API.
  • Needs configuration of Tidio API URL and client credentials (Client ID and Client Secret).
  • Uses an external proxy service (https://n8ntools.io/api/v1/proxy/tidio) to forward requests to Tidio's API.
  • The node depends on n8n's HTTP request helper to perform API calls.

Troubleshooting

  • Invalid Conversation ID: If the conversation ID is incorrect or does not exist, the API will likely return an error. Verify the conversation ID is valid.
  • Authentication Errors: Missing or invalid API keys or client credentials will cause authentication failures. Ensure credentials are correctly configured.
  • Rate Limits: Excessive requests may be throttled by the Tidio API or proxy service. Implement retries or reduce request frequency.
  • Malformed Additional Fields: Providing invalid values in additional fields like limit or offset may cause errors. Use appropriate types and ranges.
  • Proxy Service Issues: Since the node uses an external proxy, network issues or downtime on the proxy server can affect functionality.

Links and References

Discussion