Actions31
- Conversation Actions
- Message Actions
- Visitor Actions
- Contact Actions
- Bot Actions
- Operator Actions
Contact → List Contacts
AI-generatedOverview
This node integrates with the Tidio API to manage contacts within a live chat and customer engagement platform. Specifically, the "List Contacts" operation retrieves a list of contact records from Tidio, allowing users to fetch multiple contacts with pagination support.
Common scenarios where this node is beneficial include:
- Synchronizing contact data from Tidio into other systems or CRMs.
- Generating reports or analytics based on contact information.
- Automating workflows that require bulk access to contact lists.
For example, a user might use this node to pull the first 50 contacts, then process or filter them in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Collection of optional parameters to refine the request: |
| - Visitor Name | Name of the visitor |
| - Visitor Email | Email address of the visitor |
| - Visitor Phone | Phone number of the visitor |
| - Tags | Comma-separated list of tags |
| - Tag Name | Name of the tag to add/remove |
| - Custom Properties | Custom properties as JSON object |
| - 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 the mailing list |
| - Bot Flow ID | ID of the bot flow to trigger |
| - Status | Operator status; options: Online, Offline, Away |
| - Department | Department name or ID |
| - Priority | Conversation priority; options: Low, Normal, High, Urgent |
| - Limit | Maximum number of results to return (pagination limit) |
| - Offset | Number of results to skip (pagination offset) |
| - Auto Reply | Enable automatic replies (boolean) |
| - Send As Bot | Send message as bot rather than operator (boolean) |
For the "List Contacts" operation, the relevant input properties are primarily Limit and Offset to control pagination.
Output
The node outputs an array of JSON objects representing the contacts retrieved from Tidio. Each item in the output corresponds to one contact record returned by the API.
The structure of each contact JSON object typically includes fields such as:
- Contact ID
- Name
- Phone
- Tags
- Custom properties
The exact fields depend on the Tidio API response for contacts.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Tidio API.
- The node uses specific client ID and client secret headers for authentication.
- Requires configuration of the Tidio API base URL and credentials within n8n.
- The node sends requests through a proxy service hosted at
https://n8ntools.io/api/v1/proxy/tidiowhich requires an additional API key.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Exceeding rate limits imposed by the Tidio API may result in errors.
- Incorrect pagination parameters (
limitoroffset) may lead to empty or incomplete results.
Error messages:
"Unknown contact operation": Indicates an unsupported operation was requested; verify the operation name.- HTTP errors related to authorization or connectivity should be checked by validating credentials and network access.
- JSON parsing errors in custom properties indicate malformed JSON input.
Resolutions:
- Ensure all required credentials are correctly set up in n8n.
- Validate JSON inputs for custom properties before execution.
- Adjust pagination parameters to valid ranges.