Actions113
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Canned Response Actions
- Custom Attributes Actions
- 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
Overview
This node interacts with the Contacts API of a chat or customer engagement platform to retrieve detailed information about a specific contact. It is useful in scenarios where you need to fetch up-to-date contact details based on identifiers obtained from previous operations, such as after creating a contact or linking an inbox channel.
Practical examples include:
- Fetching contact profile data to display in a CRM dashboard.
- Retrieving contact metadata before sending personalized messages.
- Synchronizing contact details between systems.
Properties
| Name | Meaning |
|---|---|
| Inbox Identifier | The unique identifier for the inbox channel, obtained from the API inbox channel setup. |
| Contact Identifier | The unique source ID of the contact, obtained when the contact was created previously. |
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 other metadata associated with the contact in the system.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the
@devlikeapro/n8n-openapi-nodepackage for OpenAPI integration.
Troubleshooting
- Missing or invalid Inbox Identifier or Contact Identifier: Ensure both identifiers are correctly provided and correspond to existing entities in the system.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API endpoint issues: Confirm the base URL is correct and the API service is reachable.
- Unexpected response structure: If the API changes, the node might fail to parse the response; updating the node or its OpenAPI spec may be necessary.