Actions31
- Conversation Actions
- Message Actions
- Visitor Actions
- Contact Actions
- Bot Actions
- Operator Actions
Operator → Get Operator
AI-generatedOverview
This node integrates with the Tidio API to manage operators (agents) within a live chat and customer engagement platform. Specifically, the "Get Operator" operation retrieves detailed information about a specific operator by their unique ID.
Use cases include:
- Fetching operator details for display or processing in workflows.
- Integrating operator data into CRM or support systems.
- Automating assignment or status updates based on operator info.
For example, you might use this node to get an operator's profile before assigning them to a conversation or to verify their current status.
Properties
| Name | Meaning |
|---|---|
| Operator ID | The unique identifier of the operator whose details you want to retrieve. |
| Additional Fields | A collection of optional fields that can be used across multiple operations but are not specifically required for "Get Operator". |
Note: For the "Get Operator" operation, only the Operator ID is required. The "Additional Fields" collection includes many optional parameters relevant to other operations but does not affect this operation.
Output
The output is a JSON object containing the operator's details as returned by the Tidio API. This typically includes:
- Operator identification data (ID, name).
- Status information (online, offline, away).
- Department or team association.
- Other metadata related to the operator's profile.
The exact structure depends on the Tidio API response but generally provides comprehensive operator information.
No binary data output is involved in 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.
- The node uses an external proxy service (
https://n8ntools.io/api/v1/proxy/tidio) to forward requests to the Tidio API. - Proper credentials must be set up in n8n to allow authenticated API calls.
Troubleshooting
- Invalid Operator ID: If the provided operator ID does not exist or is malformed, the API will return an error. Verify the ID is correct.
- Authentication Errors: Missing or incorrect API keys, client ID, or client secret will cause authentication failures. Ensure credentials are properly configured.
- Network Issues: Connectivity problems to the proxy or Tidio API endpoint may cause request failures.
- API Rate Limits: Excessive requests might be throttled by the Tidio API; handle such errors gracefully.
- Unexpected Response Structure: Changes in the Tidio API could alter the response format, requiring updates to the node or workflow.
If an error occurs, the node returns an error message in the JSON output unless "Continue On Fail" is enabled, which allows the workflow to proceed.
Links and References
- Tidio API Documentation (official API docs)
- n8n Documentation (for general node usage and credential setup)