N8N Tools - Tidio APIInstall

Overview

This node integrates with the Tidio API to manage visitor data within a live chat and customer engagement platform. Specifically, the "List Visitors" operation retrieves a list of visitors tracked by Tidio, allowing users to fetch visitor information in bulk with optional filtering and pagination.

Common scenarios where this node is beneficial include:

• Exporting visitor data for analysis or CRM synchronization.
• Monitoring active or recent visitors on a website.
• Automating workflows based on visitor attributes or tags.
• Integrating visitor lists into marketing or support systems.

For example, a user might use this node to retrieve the first 50 visitors who have interacted with their website chat, then filter or tag them for targeted follow-up campaigns.

Properties

Output

The node outputs an array of JSON objects representing visitors retrieved from the Tidio API. Each item corresponds to one visitor and includes all available visitor details as returned by the API, such as visitor ID, name, email, phone, tags, custom properties, and other metadata.

No binary data output is produced by this operation.

Example output structure snippet:

[
  {
    "id": "visitor_12345",
    "name": "John Doe",
    "email": "john.doe@example.com",
    "phone": "+1234567890",
    "tags": ["premium", "newsletter"],
    "customProperties": {
      "source": "website",
      "lastVisit": "2024-06-01T12:34:56Z"
    },
    ...
  },
  ...
]

Dependencies

• Requires an API key credential for authenticating with the Tidio API.
• The node uses specific client ID and client secret credentials for authorization headers.
• The base URL for the Tidio API must be configured in the node credentials.
• The node sends requests through a proxy service hosted at https://n8ntools.io/api/v1/proxy/tidio which requires an additional API key credential.

Troubleshooting

• Authentication errors: Ensure that the API key, client ID, and client secret are correctly configured and valid. Invalid or expired credentials will cause authentication failures.
• Rate limiting or quota exceeded: The Tidio API may limit the number of requests. If you receive rate limit errors, reduce request frequency or increase limits if possible.
• Invalid JSON in custom properties: When using the "Custom Properties" field, ensure the JSON is well-formed. Malformed JSON will cause parsing errors.
• Empty or incomplete results: Check the "Limit" and "Offset" parameters to ensure you are requesting the correct range of visitors.
• Unknown resource or operation errors: These indicate misconfiguration of the node parameters. Verify that "Resource" is set to "Visitor" and "Operation" to "List Visitors".

Links and References

• Tidio API Documentation
• Tidio Live Chat Platform
• n8n Documentation