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 inbox within a given account. It is useful when you need to programmatically access inbox data such as its configuration, status, or metadata for automation workflows involving customer support or messaging management.
A practical example would be fetching an inbox's details to display in a dashboard, or to trigger further actions based on the inbox properties (e.g., routing messages, analyzing inbox activity).
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the ChatWoot account where the inbox resides. This identifies the scope of the inbox. |
| Id | The unique numeric ID of the inbox to retrieve. |
Output
The node outputs JSON data representing the full details of the specified inbox. This typically includes all inbox attributes returned by the ChatWoot API, such as inbox name, description, status, and any other metadata associated with that inbox.
No binary data output is involved.
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 inbox IDs will result in "not found" errors.
- Network connectivity problems can prevent the node from reaching the ChatWoot API.
Error messages and resolutions:
- 401 Unauthorized: Check that the API key credential is correctly set and has proper permissions.
- 404 Not Found: Verify that the provided account ID and inbox ID exist and are correct.
- Network Error: Ensure the ChatWoot base URL is reachable and there are no firewall restrictions.