Actions113
- 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
- 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
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, such as routing messages or 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 inbox object retrieved from the ChatWoot API. This typically includes all relevant inbox details such as its name, description, status, and any other metadata provided by the API.
No binary data output is expected from 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 ChatWoot REST API being accessible and the specified account and inbox IDs being valid.
Troubleshooting
- Invalid Credentials: If authentication fails, verify that the API key and base URL are correctly set in the node credentials.
- Resource Not Found: Errors indicating the inbox or account does not exist usually mean the provided IDs are incorrect or the user lacks permission.
- Network Issues: Timeouts or connection errors suggest network problems or incorrect API endpoint URLs.
- Missing Required Parameters: Ensure both "Account Id" and "Id" fields are provided and are valid numbers.
Links and References
- ChatWoot API Documentation - Official API docs for reference on inbox endpoints and data structure.