N8N Tools - Tidio API icon

N8N Tools - Tidio API

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

Actions31

Visitor → Update Visitor

AI-generated

Overview

The "Update Visitor" operation in this node allows you to modify existing visitor data within the Tidio live chat and customer engagement platform. This includes updating basic visitor information such as name, email, and phone number, as well as setting custom properties defined by JSON objects.

This operation is useful for keeping visitor profiles up-to-date with the latest information, enriching visitor data for better personalization, or integrating visitor updates from other systems. For example, if a visitor provides new contact details during a chat session, you can update their profile automatically. Similarly, you can add custom attributes like user preferences or behavior tags to enhance targeting and analytics.

Properties

Name Meaning
Visitor ID The unique identifier of the visitor whose data you want to update (required).
Visitor Name The updated name of the visitor.
Visitor Email The updated email address of the visitor.
Visitor Phone The updated phone number of the visitor.
Tags Comma-separated list of tags associated with the visitor (not used directly in update).
Tag Name Name of a tag to add or remove (not used directly in update).
Custom Properties A JSON object containing any custom properties to set on the visitor profile.
Contact Name Full name of the contact related to the visitor (not used directly in update).
Contact Email Email address of the contact (not used directly in update).
Contact Phone Phone number of the contact (not used directly in update).
Mailing List ID ID of a mailing list (not used directly in update).
Bot Flow ID ID of a bot flow to trigger (not used directly in update).
Status Operator status (online, offline, away) (not used directly in update).
Department Department name or ID (not used directly in update).
Priority Conversation priority (low, normal, high, urgent) (not used directly in update).
Limit Maximum number of results to return (not used directly in update).
Offset Number of results to skip (not used directly in update).
Auto Reply Enable automatic replies (not used directly in update).
Send As Bot Send message as bot rather than operator (not used directly in update).

Note: For the "Update Visitor" operation, only the following fields are actually used to build the update payload:

  • Visitor Name (visitorName)
  • Visitor Email (visitorEmail)
  • Visitor Phone (visitorPhone)
  • Custom Properties (customProperties parsed from JSON)

Other additional fields exist but are not applied in this operation.

Output

The output is a JSON object representing the response from the Tidio API after attempting to update the visitor. It typically contains the updated visitor data or an error message if the update failed.

Example structure:

{
  "id": "visitor-id",
  "name": "Updated Visitor Name",
  "email": "updated.email@example.com",
  "phone": "+1234567890",
  "custom_properties": {
    "key1": "value1",
    "key2": "value2"
  },
  ...
}

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 URL, client ID, and client secret credentials.
  • The node uses an external proxy service endpoint (https://n8ntools.io/api/v1/proxy/tidio) to forward requests to the Tidio API.
  • Proper permissions on the Tidio account to update visitor data.

Troubleshooting

  • Invalid Visitor ID: If the visitor ID does not exist or is incorrect, the API will return an error. Verify the visitor ID before running the update.
  • Malformed Custom Properties JSON: The customProperties field must be valid JSON. Invalid JSON will cause parsing errors. Use a JSON validator to ensure correctness.
  • Authentication Errors: Ensure that the API key, client ID, and client secret are correctly configured and have sufficient permissions.
  • API Rate Limits: Frequent updates may hit rate limits imposed by Tidio. Implement retry logic or reduce request frequency if needed.
  • Unexpected Fields Ignored: Only certain fields are accepted for update; others in "Additional Fields" are ignored for this operation. Make sure to use supported fields.

Links and References

Discussion