N8N Tools - Tidio API icon

N8N Tools - Tidio API

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

Actions31

Conversation → Get Conversation

AI-generated

Overview

The node integrates with the Tidio API to manage live chat conversations. Specifically, the Get Conversation operation retrieves detailed information about a single conversation by its ID. This is useful for scenarios where you want to fetch the current state, metadata, or details of a specific chat session between an operator and a visitor.

Practical examples include:

  • Fetching conversation details to display in a dashboard.
  • Retrieving conversation data before updating or closing it.
  • Using conversation info to trigger follow-up workflows or analytics.

Properties

Name Meaning
Conversation ID The unique identifier of the conversation to retrieve.
Additional Fields A collection of optional fields that can be used across various operations (not used directly in Get Conversation).

Note: For the Get Conversation operation, only the Conversation ID is required and used.

Output

The output is a JSON object containing the full details of the requested conversation as returned by the Tidio API. This typically includes:

  • Conversation metadata (ID, status, priority, department).
  • Visitor and contact information linked to the conversation.
  • Tags associated with the conversation.
  • Any custom properties or additional data stored on the conversation.

The node does not output binary data for this operation.

Example output structure (simplified):

{
  "id": "string",
  "status": "online" | "offline" | "away",
  "priority": "low" | "normal" | "high" | "urgent",
  "department": "string",
  "visitor": {
    "id": "string",
    "name": "string",
    "email": "string",
    "phone": "string"
  },
  "contact": {
    "id": "string",
    "name": "string",
    "email": "string",
    "phone": "string"
  },
  "tags": ["tag1", "tag2"],
  "customProperties": {}
}

Dependencies

  • Requires an API key credential for authenticating with the Tidio API.
  • Needs configuration of the Tidio API URL, client ID, and client secret.
  • The node uses an external proxy service (https://n8ntools.io/api/v1/proxy/tidio) to forward requests to the Tidio API.
  • Proper credentials must be set up in n8n for the node to function.

Troubleshooting

  • Error: Unknown conversation operation — Ensure the operation parameter is correctly set to getConversation.
  • Invalid Conversation ID — Verify that the provided conversation ID exists and is correct.
  • Authentication errors — Check that the API key, client ID, and client secret are valid and properly configured.
  • Network or proxy issues — Since the node uses an external proxy, network connectivity or proxy downtime may cause failures.
  • Malformed JSON in additional fields — Although not used in this operation, if additional fields are supplied elsewhere, ensure JSON syntax is correct.

If the node throws errors, enabling "Continue On Fail" can help process multiple items without stopping the entire workflow.

Links and References

Discussion