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 ChatWoot API to retrieve information about contactable inboxes associated with a specific contact within an account. It is useful when you need to fetch all inboxes through which a particular contact can be reached, for example, to display communication channels or to route messages appropriately.
A practical scenario includes customer support workflows where agents want to see all available inboxes linked to a contact before initiating communication.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the ChatWoot account to which the contact belongs. |
| Id | The unique numeric ID of the contact whose contactable inboxes are being retrieved. |
Output
The node outputs JSON data representing the list of inboxes that are contactable for the specified contact. This typically includes details such as inbox IDs, names, and possibly other metadata describing each inbox.
No binary data output is involved in this operation.
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 OpenAPI integration.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing incorrect account or contact IDs may result in "not found" errors.
- Network connectivity problems can prevent the node from reaching the ChatWoot API.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- "Resource not found" errors suggest the provided account or contact ID does not exist; double-check these values.
- Timeout or connection errors imply network issues; ensure the ChatWoot server is reachable.