N8N Tools - Tidio API icon

N8N Tools - Tidio API

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

Actions31

Contact → Update Contact

AI-generated

Overview

This node integrates with the Tidio API to manage contact information within a customer engagement and live chat platform. Specifically, the "Update Contact" operation allows users to modify existing contact details such as name, email, phone number, and other custom properties. This is useful for keeping contact records up-to-date in automated workflows, CRM synchronization, or customer support scenarios.

Practical examples include:

  • Automatically updating a contact’s email or phone number when new data is received from a form submission.
  • Enriching contact profiles with additional tags or custom properties based on user interactions.
  • Adjusting contact information before triggering targeted marketing campaigns or chatbot flows.

Properties

Name Meaning
Contact ID The unique identifier of the contact to update (required).
Additional Fields A collection of optional fields to update on the contact:
- Contact Name Full name of the contact.
- Contact Email Email address of the contact.
- Contact Phone Phone number of the contact.
- Visitor Name Name of the visitor associated with the contact.
- Visitor Email Email address of the visitor.
- Visitor Phone Phone number of the visitor.
- Tags Comma-separated list of tags to assign to the contact.
- Tag Name Name of a tag to add or remove (used in other operations).
- Custom Properties JSON object containing any custom properties to set on the contact.
- Mailing List ID ID of the mailing list (used in other operations).
- Bot Flow ID ID of the bot flow to trigger (used in other operations).
- Status Operator status; options are Online, Offline, Away (used in operator-related operations).
- Department Department name or ID (used in conversation operations).
- Priority Conversation priority; options are Low, Normal, High, Urgent (used in conversation ops).
- Limit Maximum number of results to return (used in list operations).
- Offset Number of results to skip (used in list operations).
- Auto Reply Boolean to enable automatic replies (used in bot settings).
- Send As Bot Boolean to send message as bot rather than operator (used in message operations).

For the "Update Contact" operation, only these fields are relevant:

  • Contact ID (required)
  • Contact Name
  • Contact Email
  • Contact Phone

Output

The node outputs a JSON object representing the response from the Tidio API after attempting to update the contact. This typically includes the updated contact details or an error message if the update failed.

Example output structure:

{
  "id": "contact-id",
  "name": "Updated Contact Name",
  "email": "updated.email@example.com",
  "phone": "+1234567890",
  "tags": ["tag1", "tag2"],
  "custom_properties": {
    "key1": "value1"
  }
}

No binary data output is produced by this operation.

Dependencies

  • Requires an active Tidio API key credential configured in n8n.
  • Needs API URL, client ID, and client secret credentials for authentication.
  • The node sends requests through a proxy service hosted at https://n8ntools.io/api/v1/proxy/tidio using an API key for that proxy.

Troubleshooting

  • Common issues:

    • Invalid or missing Contact ID will cause the API to reject the request.
    • Malformed JSON in custom properties may cause parsing errors.
    • Insufficient permissions or invalid API credentials will result in authorization errors.
    • Network connectivity issues to the proxy or Tidio API endpoint.

  • Error messages:

    • "Unknown contact operation": Indicates an unsupported operation was selected.
    • "error": "<message>": Generic error returned from the API or node execution failure.

  • Resolutions:

    • Verify the Contact ID is correct and exists in Tidio.
    • Ensure custom properties JSON is valid.
    • Confirm API credentials are correctly set and have required permissions.
    • Check network access and proxy configuration.

Links and References

Discussion