Actions35
- Account Actions
- Canned Response Actions
- Contact Actions
- Conversation Actions
- Inbox Actions
- Label Actions
- Message Actions
- Team Actions
- Webhook Actions
Overview
The node interacts with the Chatwoot API to perform various operations on different resources. Specifically, for the Inbox - Get operation, it retrieves detailed information about a specific inbox within a given account. This is useful when you want to fetch metadata or configuration details of an inbox, such as its name, type, or settings.
Common scenarios:
- Fetching inbox details to display in dashboards or reports.
- Validating inbox existence before sending messages or creating conversations.
- Synchronizing inbox data with other systems.
Example:
You have multiple inboxes set up in your Chatwoot account (e.g., support, sales). Using this node, you can retrieve the details of the "support" inbox by specifying its numeric ID and the account ID, then use that data downstream in your workflow.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric ID of the Chatwoot account containing the inbox. |
| Inbox ID | The numeric ID of the inbox to retrieve details for. |
| Continue on Fail | Whether to continue executing subsequent items if this operation fails (true/false). |
Output
The output is a JSON object representing the inbox details as returned by the Chatwoot API. It typically includes fields such as:
- Inbox ID
- Inbox name
- Inbox type (e.g., email, website widget)
- Configuration settings
- Associated channels or integrations
- Timestamps and metadata
The exact structure depends on the Chatwoot API response for the inbox resource.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Chatwoot API via an API key credential configured in n8n.
- The base URL of the Chatwoot instance must be set in the credentials.
- Network access to the Chatwoot API endpoint.
Troubleshooting
Common issues:
- Invalid or missing Account ID or Inbox ID parameters will cause the API request to fail.
- Incorrect API credentials or base URL will result in authentication errors.
- Network connectivity problems may cause timeouts or unreachable host errors.
Error messages:
"404 Not Found": The specified inbox or account does not exist. Verify IDs."401 Unauthorized"or"403 Forbidden": Authentication failure; check API key and permissions."400 Bad Request": Malformed request, possibly due to invalid parameter types.
Resolutions:
- Double-check that the Account ID and Inbox ID are correct and correspond to existing entities.
- Ensure the API key credential is valid and has sufficient permissions.
- Confirm the Chatwoot base URL is correctly configured.
- Enable "Continue on Fail" if you want the workflow to proceed despite individual item failures.