N8N Tools - Tidio API icon

N8N Tools - Tidio API

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

Actions31

Conversation → Assign Conversation

AI-generated

Overview

The node integrates with the Tidio API to manage live chat conversations, operators, visitors, contacts, messages, and chatbot flows. Specifically, the Assign Conversation operation under the Conversation resource assigns a conversation to a specified operator. This is useful in customer support scenarios where incoming chats need to be routed or reassigned to particular agents for handling.

Practical examples include:

  • Automatically assigning new conversations to available support agents.
  • Reassigning ongoing conversations to specialized operators based on topic or priority.
  • Managing workload distribution among team members by programmatically controlling conversation ownership.

Properties

Name Meaning
Conversation ID The unique identifier of the conversation to assign.
Operator ID The unique identifier of the operator (agent) to whom the conversation will be assigned.
Additional Fields Not used specifically in this operation but available for other operations.

Output

The output JSON contains the response from the Tidio API after attempting to assign the conversation. Typically, it includes details about the updated conversation state, such as the assigned operator information and any status changes.

Example structure (simplified):

{
  "id": "conversation_id",
  "operator_id": "assigned_operator_id",
  "status": "active",
  "tags": [...],
  "priority": "normal",
  ...
}

No binary data is output by this operation.

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 sends requests through a proxy service (https://n8ntools.io/api/v1/proxy/tidio) using the provided API key.

Troubleshooting

  • Error: Unknown conversation operation: assignConversation
    Occurs if the operation name is misspelled or not supported. Ensure the operation is exactly assignConversation.

  • Authentication errors
    If credentials are invalid or missing, the API will reject requests. Verify that the API key, client ID, and client secret are correctly configured.

  • Invalid Conversation ID or Operator ID
    The API may return errors if the IDs do not exist or are malformed. Double-check the IDs passed to the node.

  • Network or Proxy issues
    Since requests go through a proxy, network problems or proxy downtime can cause failures. Check connectivity and proxy availability.

Links and References

Discussion