N8N Tools - Tidio APIInstall

Overview

This node integrates with the Tidio API to manage chatbot flows and triggers. Specifically, the Get Bot Flows operation retrieves the list of available bot flows configured in a Tidio account. This is useful for workflows that need to dynamically access or display existing chatbot flows, for example, to trigger specific bots based on user interactions or to audit/configure chatbot setups.

Practical examples:

• Automatically fetching all chatbot flows to present options in a UI or decision logic.
• Using the retrieved bot flow IDs to trigger specific chatbots in subsequent workflow steps.
• Monitoring or syncing chatbot configurations between Tidio and other systems.

Properties

Note: The provided properties JSON includes many fields, but for the Get Bot Flows operation only limit and offset from Additional Fields are relevant as query parameters.

Output

The output is a JSON object representing the response from the Tidio API endpoint /v1/bot/flows. It contains the list of bot flows available in the connected Tidio account.

Typical structure (example):

{
  "flows": [
    {
      "id": "string",
      "name": "string",
      "description": "string",
      "status": "active" | "inactive",
      ...
    },
    ...
  ],
  "total": 123,
  "limit": 50,
  "offset": 0
}

• flows: Array of bot flow objects with details such as ID, name, description, and status.
• total: Total number of bot flows available.
• limit: Number of results returned (as requested).
• offset: Offset used in the query.

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 base URL and client credentials (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 read bot flows.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials will cause authentication errors.
  • Incorrect or missing client ID/secret may result in authorization failures.
  • Network connectivity problems to the proxy or Tidio API endpoints.
  • Requesting too large a limit may cause API rate limiting or errors.

• Error messages:

  • "Unknown bot operation: getBotFlows": Indicates the operation parameter was not recognized; ensure the operation is set exactly to "getBotFlows".
  • HTTP 401 Unauthorized or 403 Forbidden: Check API key and client credentials.
  • JSON parsing errors on custom properties: Ensure any JSON input fields are valid JSON.

• Resolution tips:

  • Verify all credentials and API keys are correctly configured in n8n.
  • Use reasonable values for limit and offset.
  • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

• Tidio API Documentation (for detailed API endpoints and parameters)
• n8n Documentation (for general usage of custom nodes and credentials)