N8N Tools - Tidio API icon

N8N Tools - Tidio API

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

Actions31

Conversation → Update Conversation

AI-generated

Overview

The node provides integration with the Tidio API, focusing on managing live chat conversations and related entities such as messages, visitors, contacts, bots, and operators. Specifically, the Update Conversation operation allows users to modify properties of an existing conversation in Tidio.

This operation is useful for scenarios where you want to update metadata or attributes of a chat conversation, such as changing its priority, department assignment, or tags. For example, after receiving a new message from a customer, you might want to escalate the conversation priority to "urgent" or assign it to a specific department automatically.

Practical examples include:

  • Updating the priority of a conversation based on keywords detected in messages.
  • Changing the department handling the conversation when routing chats.
  • Adding or removing tags to categorize conversations dynamically.

Properties

Name Meaning
Conversation ID The unique identifier of the conversation to update (required).
Additional Fields A collection of optional fields to update various conversation properties:
- Visitor Name Name of the visitor associated with the conversation.
- Visitor Email Email address of the visitor.
- Visitor Phone Phone number of the visitor.
- Tags Comma-separated list of tags to set on the conversation.
- Tag Name Name of a tag to add or remove (used in other operations).
- Custom Properties JSON object of custom properties to associate with the conversation.
- Contact Name Full name of the contact linked to the conversation.
- Contact Email Email address of the contact.
- Contact Phone Phone number of the contact.
- Mailing List ID ID of a mailing list (used in contact-related operations).
- Bot Flow ID ID of a bot flow to trigger (used in bot-related operations).
- Status Operator status; options are Online, Offline, Away.
- Department Department name or ID to assign the conversation to.
- Priority Conversation priority; options are 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 to enable automatic replies (used in bot settings).
- Send As Bot Boolean to send messages as bot rather than operator (used in messaging operations).

Output

The output is a JSON object representing the response from the Tidio API after updating the conversation. It typically contains the updated conversation details, including any changed properties such as tags, priority, department, and custom fields.

If the operation fails, the output will contain an error message describing the issue.

No binary data is produced 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 uses an external proxy service (https://n8ntools.io/api/v1/proxy/tidio) to forward requests to the Tidio API.
  • Proper permissions on the Tidio account to update conversations.

Troubleshooting

  • Common issues:

    • Invalid or missing Conversation ID will cause errors.
    • Incorrect API credentials or expired tokens will result in authentication failures.
    • Providing malformed JSON in custom properties may cause parsing errors.
    • Trying to update unsupported fields or using invalid values for enums (e.g., priority) can lead to API rejections.

  • Error messages:

    • "Unknown conversation operation": Indicates an unsupported operation was requested.
    • "Unknown resource": The specified resource is not recognized.
    • API authentication errors usually mention invalid credentials or unauthorized access.

  • Resolutions:

    • Verify that the Conversation ID exists and is correct.
    • Check API credentials and refresh if necessary.
    • Validate JSON syntax for custom properties before submitting.
    • Use only supported values for enumerated fields like priority and status.

Links and References

Discussion