N8N Tools - Tidio APIInstall

Overview

The node integrates with the Tidio API to manage live chat conversations, specifically allowing users to add tags to existing conversations. This operation is useful for categorizing or labeling conversations dynamically based on context, customer type, issue priority, or any custom classification scheme.

Typical use cases include:

• Automatically tagging conversations when certain keywords are detected.
• Organizing conversations by campaign, product interest, or support topic.
• Enabling better filtering and reporting in Tidio by adding meaningful tags during workflow automation.

For example, a support team could tag conversations as "urgent" or "billing" to prioritize and route them accordingly.

Properties

Output

The node outputs a JSON object representing the response from the Tidio API after attempting to add the tag. This typically includes confirmation of the tag addition or details about the updated conversation.

The output structure is:

{
  "json": {
    // Response data from Tidio API regarding the tag addition
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data is produced by this operation.

Dependencies

• Requires an active Tidio API integration with valid credentials including an API key, client ID, and client secret.
• The node uses these credentials to authenticate requests to the Tidio API.
• No additional environment variables are needed beyond the configured credentials in n8n.

Troubleshooting

• Common issues:

  • Invalid or missing Conversation ID: The operation requires a valid conversation ID; ensure it is correctly provided.
  • Missing or empty Tag Name: The tag name must be specified to add a tag.
  • Authentication errors: Verify that the API key and client credentials are correct and have sufficient permissions.
  • Network or API endpoint errors: Check connectivity and that the Tidio API URL is reachable.

• Error messages:

  • "Unknown conversation operation: addTag": Indicates a misconfiguration or typo in the operation parameter.
  • API authentication failures usually return HTTP 401 or 403 errors; recheck credentials.
  • Validation errors from the API if required fields are missing or malformed.

To resolve errors, verify all required parameters, confirm credential validity, and consult Tidio API documentation for specific error codes.

Links and References

• Tidio API Documentation (for detailed API endpoints and usage)
• n8n Documentation (for general node usage and credential setup)