Actions100
- 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
Overview
This node interacts with the ChatWoot API to retrieve a list of inboxes that are contactable for a specific contact within a given account. It is useful in scenarios where you need to determine through which inboxes a particular contact can be reached, such as routing messages, managing communication channels, or automating workflows based on available contact points.
Practical examples:
- Fetching all inboxes where a customer (contact) can be messaged.
- Automating assignment of conversations to available inboxes for a contact.
- Integrating with CRM systems to display or use available contact channels.
Properties
| Display Name | Type | Description |
|---|---|---|
| Account Id | Number | The numeric ID of the account. |
| Id | Number | ID of the contact. |
Both properties are required and must be provided to fetch the contactable inboxes for the specified contact.
Output
The output will be a JSON object containing information about the inboxes that are contactable for the specified contact. The structure typically includes an array of inbox objects, each representing an inbox with its relevant details (such as id, name, type, etc.).
Example output:
{
"inboxes": [
{
"id": 123,
"name": "Support",
"channel_type": "Email",
// ...other inbox fields
},
{
"id": 456,
"name": "Sales",
"channel_type": "Chat",
// ...other inbox fields
}
]
}
Note: The exact fields depend on the ChatWoot API response.
Dependencies
- External Service: Requires access to the ChatWoot API.
- API Credentials: You must configure
chatwootApicredentials in n8n, including the base URL and authentication token. - n8n Configuration: Ensure the node is properly authenticated and has network access to the ChatWoot instance.
Troubleshooting
Common issues:
- Invalid Account Id or Contact Id: If either ID is incorrect or does not exist, the API may return a 404 error or an empty result.
- Authentication Errors: Missing or invalid API credentials will result in authentication errors (e.g., 401 Unauthorized).
- Network Issues: If n8n cannot reach the ChatWoot server, you may encounter connection errors.
Error messages and resolutions:
"401 Unauthorized": Check your API credentials and ensure they are correctly configured in n8n."404 Not Found": Verify that both the Account Id and Contact Id are correct and exist in your ChatWoot instance."Connection refused"or timeout errors: Ensure the ChatWoot API URL is reachable from your n8n environment.