Actions31
- Conversation Actions
- Message Actions
- Visitor Actions
- Contact Actions
- Bot Actions
- Operator Actions
Conversation → List Conversations
AI-generatedOverview
The node integrates with the Tidio API to manage live chat conversations. Specifically, the List Conversations operation retrieves a list of chat conversations from the Tidio platform. This is useful for scenarios where you want to monitor ongoing or past customer interactions, analyze chat activity, or automate workflows based on conversation data.
Practical examples include:
- Fetching recent conversations to display in a dashboard.
- Exporting conversation data for reporting or analytics.
- Triggering follow-up actions based on conversation status or tags.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional filters and parameters to refine the list of conversations returned. These include: |
| - Visitor Name: Filter by visitor's name | |
| - Visitor Email: Filter by visitor's email | |
| - Visitor Phone: Filter by visitor's phone number | |
| - Tags: Comma-separated list of tags to filter conversations | |
| - Tag Name: Name of a tag to add or remove (not typically used in listing) | |
| - Custom Properties: JSON object with custom properties | |
| - Contact Name: Full name of the contact | |
| - Contact Email: Email address of the contact | |
| - Contact Phone: Phone number of the contact | |
| - Mailing List ID: ID of mailing list | |
| - Bot Flow ID: ID of bot flow to trigger | |
| - Status: Operator status; options are Online, Offline, Away | |
| - Department: Department name or ID | |
| - Priority: Conversation priority; options are Low, Normal, High, Urgent | |
| - Limit: Maximum number of results to return (default 50) | |
| - Offset: Number of results to skip (default 0) | |
| - Auto Reply: Enable automatic replies (boolean) | |
| - Send As Bot: Send message as bot rather than operator (boolean) |
Output
The output is a JSON array containing the list of conversations retrieved from the Tidio API. Each item in the array represents a conversation object with details such as conversation ID, visitor info, tags, status, priority, department, and other metadata as provided by the API.
No binary data is output by this operation.
Example output structure (simplified):
[
{
"id": "conversation_id_123",
"visitor": {
"name": "John Doe",
"email": "john@example.com",
"phone": "+123456789"
},
"tags": ["support", "vip"],
"status": "online",
"priority": "normal",
"department": "sales",
...
},
...
]
Dependencies
- Requires an API key credential for authenticating with the Tidio API.
- The node uses a proxy service hosted at
https://n8ntools.io/api/v1/proxy/tidioto forward requests. - Necessary credentials include client ID and client secret for Tidio API access.
- The user must configure these credentials within n8n before using the node.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Exceeding rate limits imposed by the Tidio API may result in request failures.
- Providing invalid filter values (e.g., malformed JSON in custom properties) can cause errors.
Error messages:
"Unknown conversation operation": Indicates an unsupported operation was selected; verify the operation name."Unknown resource": Indicates an invalid resource was specified.- Network or proxy errors may occur if the proxy service is unreachable.
Resolutions:
- Double-check API credentials and ensure they are correctly set up.
- Validate all input fields, especially JSON-formatted custom properties.
- Monitor API usage to avoid hitting rate limits.
- Ensure network connectivity to the proxy endpoint.