Actions31
- Conversation Actions
- Message Actions
- Visitor Actions
- Contact Actions
- Bot Actions
- Operator Actions
Visitor → Get Visitor
AI-generatedOverview
The "Get Visitor" operation of the "Visitor" resource in this node allows you to retrieve detailed information about a specific visitor by their unique visitor ID. This is useful for scenarios where you want to fetch visitor data such as name, email, phone number, tags, custom properties, and other metadata stored in the Tidio live chat system.
Practical examples include:
- Fetching visitor details to personalize chat interactions or marketing campaigns.
- Retrieving visitor information to analyze customer behavior or segment users.
- Integrating visitor data into CRM or support systems for enhanced customer service.
Properties
| Name | Meaning |
|---|---|
| Visitor ID | The unique identifier of the visitor whose information you want to retrieve (required). |
| Additional Fields | Not applicable for "Get Visitor" operation; included for other operations on visitors. |
Output
The output JSON contains the full visitor information as returned by the Tidio API. This typically includes fields such as:
- Visitor's unique ID
- Name, email, and phone number (if available)
- Tags associated with the visitor
- Custom properties defined for the visitor
- Other metadata related to the visitor's activity and profile
The output is structured as a JSON object representing the visitor's data. There is no binary data output for this operation.
Example output snippet (simplified):
{
"id": "visitor123",
"name": "John Doe",
"email": "john.doe@example.com",
"phone": "+1234567890",
"tags": ["premium", "newsletter"],
"customProperties": {
"lastPurchase": "2024-05-01"
}
}
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 internal proxy service endpoint (
https://n8ntools.io/api/v1/proxy/tidio) to forward requests to the Tidio API.
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 making the request.
- Authentication Errors: Ensure that the API key, client ID, and client secret are correctly configured and valid.
- Network Issues: Connectivity problems to the proxy or Tidio API can cause failures. Check network access and proxy availability.
- Malformed JSON in Custom Properties: For operations involving custom properties (not "Get Visitor"), ensure JSON strings are well-formed to avoid parsing errors.
Common error messages:
"Unknown visitor operation": Occurs if an unsupported operation is selected."Unknown resource": Happens if the resource parameter is invalid.- API authentication errors indicating invalid or missing credentials.