N8N Tools - Tidio API icon

N8N Tools - Tidio API

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

Actions31

Bot → Trigger Bot

AI-generated

Overview

The node provides integration with the Tidio live chat and chatbot platform, specifically focusing on triggering chatbot flows ("Trigger Bot" operation under the "Bot" resource). This operation allows users to programmatically start a chatbot flow for a specified visitor in Tidio.

Common scenarios where this node is beneficial include:

  • Automatically initiating a chatbot conversation when a visitor performs a specific action on a website.
  • Triggering targeted chatbot flows based on visitor data or external events.
  • Integrating chatbot triggers into broader automation workflows to enhance customer engagement.

For example, you could use this node to trigger a welcome bot flow for a visitor who just signed up on your site, passing along their visitor ID and selecting the appropriate bot flow to engage them.

Properties

Name Meaning
Additional Fields Collection of optional fields to customize the bot trigger:
- Visitor Name Name of the visitor (string)
- Visitor Email Email address of the visitor (string)
- Visitor Phone Phone number of the visitor (string)
- Tags Comma-separated list of tags (string)
- Tag Name Name of the tag to add/remove (string)
- Custom Properties Custom properties as JSON object (JSON)
- Contact Name Full name of the contact (string)
- Contact Email Email address of the contact (string)
- Contact Phone Phone number of the contact (string)
- Mailing List ID ID of the mailing list (string)
- Bot Flow ID ID of the bot flow to trigger (string) — required for triggering a bot
- Status Operator status; options: Online, Offline, Away
- Department Department name or ID (string)
- Priority Conversation priority; options: Low, Normal, High, Urgent
- Limit Maximum number of results to return (number)
- Offset Number of results to skip (number)
- Auto Reply Enable automatic replies (boolean)
- Send As Bot Send message as bot rather than operator (boolean)

For the "Trigger Bot" operation, the key property is Bot Flow ID, which specifies which chatbot flow to activate. The visitor ID is also required but provided separately as an input parameter.

Output

The node outputs a JSON object representing the response from the Tidio API after attempting to trigger the bot flow. The structure typically includes details about the triggered flow and confirmation of the action.

Example output JSON structure (simplified):

{
  "flow_id": "string",
  "visitor_id": "string",
  "status": "success",
  "message": "Bot flow triggered successfully"
}

If an error occurs, the output JSON will contain an error field with the error message.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Tidio API.
  • Needs configuration of the Tidio API URL, client ID, and client secret credentials.
  • Uses an external proxy service (https://n8ntools.io/api/v1/proxy/tidio) to forward requests to the Tidio API.
  • Requires network access to the proxy endpoint and Tidio API.

Troubleshooting

  • Missing Bot Flow ID: If the Bot Flow ID is not provided, the API call will fail. Ensure this property is set correctly.
  • Invalid Visitor ID: Providing an incorrect or non-existent visitor ID will cause the trigger to fail.
  • Authentication Errors: Incorrect or expired API credentials will result in authentication failures. Verify API keys and secrets.
  • Network Issues: Failure to reach the proxy or Tidio API endpoints can cause timeouts or connection errors.
  • Malformed Custom Properties: If custom properties JSON is invalid, the request will fail. Validate JSON syntax before input.

Common error messages:

  • "Unknown bot operation: triggerBot" — indicates a misconfiguration or unsupported operation.
  • "Error: Unauthorized" — check API credentials.
  • "Error: Bad Request" — verify all required parameters are correctly set.

To resolve issues, double-check all required inputs, ensure valid credentials, and confirm network connectivity.

Links and References

Discussion