Actions113
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Contacts API Actions
- Inbox API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Custom Attributes Actions
- Canned Response Actions
Overview
This node interacts with the ChatWoot API to retrieve detailed information about a specific contact within an account. It is useful when you need to fetch comprehensive data about a contact, such as their profile details, communication history, or other metadata stored in ChatWoot. Practical scenarios include customer support workflows where agents require quick access to contact details or automation processes that enrich CRM records with up-to-date contact information.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account to which the contact belongs. This identifies the scope for the contact lookup. |
| Id | The unique numeric ID of the contact whose details are being requested. |
Output
The node outputs JSON data containing the full details of the specified contact as returned by the ChatWoot API. This typically includes fields such as contact name, email, phone number, custom attributes, and possibly conversation history or tags associated with the contact.
If the API supports binary data related to contacts (e.g., profile images), the node would also handle binary output accordingly, but this is not explicitly indicated in the provided code.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL for the ChatWoot instance must be configured in the node credentials.
- The node depends on the
@devlikeapro/n8n-openapi-nodepackage for building properties from the OpenAPI specification.
Troubleshooting
- Invalid Account Id or Contact Id: If either ID is incorrect or does not exist, the API will likely return an error or empty response. Verify IDs before running the node.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access contact details.
- Network Issues: Connectivity problems with the ChatWoot server can cause timeouts or failures. Check network settings and ChatWoot server status.
- Unexpected Response Format: If the API changes its response schema, the node might fail to parse the contact details correctly. Updating the OpenAPI spec or node version may be required.