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 Contacts API of ChatWoot to retrieve detailed information about a specific contact. It is useful when you need to fetch up-to-date data on a contact stored in ChatWoot, such as for customer support, CRM synchronization, or analytics purposes. For example, after creating a contact or receiving a message, you might want to get full details like name, email, phone number, and other metadata associated with that contact.
Properties
| Name | Meaning |
|---|---|
| Inbox Identifier | The unique identifier of the inbox channel from which the contact belongs. |
| Contact Identifier | The unique source ID of the contact whose details you want to retrieve. |
Output
The node outputs JSON data containing the detailed information of the specified contact. This typically includes fields such as contact name, email, phone number, custom attributes, and any other metadata available in ChatWoot for that contact. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL of the ChatWoot instance must be configured in the node credentials.
- The node depends on the ChatWoot REST API being accessible and the provided identifiers being valid.
Troubleshooting
- Invalid Inbox Identifier or Contact Identifier: If either identifier is incorrect or does not exist, the API will likely return an error indicating the resource was not found. Verify the IDs are correct and correspond to existing entities.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to access contact details.
- Network Issues: Connectivity problems or incorrect base URL configuration can cause request failures. Confirm the ChatWoot instance URL is reachable.
- API Rate Limits: Excessive requests may lead to rate limiting; handle such errors by implementing retries or backoff strategies.
Links and References
- ChatWoot API Documentation - Official API docs for reference on endpoints and data structures.