Actions36
- Account Actions
- Canned Response Actions
- Contact Actions
- Conversation Actions
- Inbox Actions
- Label Actions
- Message Actions
- Team Actions
- Webhook Actions
Overview
This node interacts with the Chatwoot API to manage various resources such as accounts, contacts, conversations, messages, inboxes, canned responses, webhooks, teams, and labels. Specifically, for the Inbox - Get operation, it retrieves detailed information about a specific inbox by its numeric ID.
Use cases include:
- Fetching inbox details to display or process in workflows.
- Integrating Chatwoot inbox data into other systems or automations.
- Monitoring or auditing inbox configurations programmatically.
Example: You want to get the configuration and status of an inbox with ID 5 to decide how to route incoming messages in your workflow.
Properties
| Name | Meaning |
|---|---|
| Inbox ID | The numeric ID of the inbox to retrieve. |
| Continue on Fail | Whether the node should continue processing subsequent items if this operation fails. |
| Debug Logging | Enables detailed console logs showing request URLs, headers, and responses for debugging. |
Output
The output is a JSON object representing the inbox details as returned by the Chatwoot API. This typically includes fields such as inbox name, type, channel information, and other metadata related to the inbox.
If multiple input items are processed, the output will be an array of such JSON objects, one per item.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Chatwoot API.
- The node expects the base URL of the Chatwoot instance and an account ID configured in the credentials.
- Network access to the Chatwoot API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing API authentication token will cause authorization errors.
- Incorrect inbox ID (non-existent or mistyped) will result in a "not found" error from the API.
- Network connectivity problems can cause request failures.
Error messages:
- HTTP request errors will be logged if debug logging is enabled.
- If the node throws an error, enabling "Continue on Fail" allows the workflow to proceed while capturing the error message in the output JSON under
error.
Resolution tips:
- Verify that the API key credential is correctly set up and has permissions to access inbox data.
- Confirm the inbox ID exists in your Chatwoot account.
- Enable debug logging to see detailed request/response info for troubleshooting.