N8N Tools - Tidio APIInstall

Overview

This node integrates with the Tidio API to manage contact information within a customer engagement and live chat platform. Specifically, the "Get Contact" operation retrieves detailed information about a single contact by their unique ID. This is useful in scenarios where you want to fetch up-to-date contact details for use in workflows such as personalized messaging, CRM updates, or analytics.

Practical examples include:

• Retrieving a contact's email and phone number before sending a targeted marketing message.
• Fetching contact details to enrich customer support tickets.
• Using contact data to trigger conditional workflow branches based on contact attributes.

Properties

Output

The output is a JSON object representing the contact's details as returned by the Tidio API. It typically includes fields such as the contact's name, email, phone number, tags, custom properties, and other metadata associated with the contact.

Example structure (fields may vary):

{
  "id": "contact-id",
  "name": "Full Name",
  "email": "email@example.com",
  "phone": "+1234567890",
  "tags": ["tag1", "tag2"],
  "custom_properties": {
    "property1": "value1",
    "property2": "value2"
  },
  ...
}

No binary data output is produced 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, authenticated via an API key.

Troubleshooting

• Common issues:

  • Invalid or missing Contact ID will cause the API request to fail.
  • Incorrect or expired API credentials will result in authentication errors.
  • Network connectivity problems can prevent reaching the proxy or Tidio API endpoints.

• Error messages:

  • "Unknown contact operation: getContact": Indicates a misconfiguration of the operation parameter; ensure "Get Contact" is selected.
  • Authentication errors usually mention invalid credentials or unauthorized access; verify API keys and client secrets.
  • If the contact ID does not exist, the API may return a 404 error indicating the contact was not found.

• Resolutions:

  • Double-check that the Contact ID is correct and exists in the Tidio system.
  • Verify that all required credentials are properly set up and valid.
  • Ensure network access to the proxy endpoint and Tidio API is not blocked by firewalls.

Links and References

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