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 Canned Response resource with the Get Many operation, it retrieves multiple canned responses associated with a Chatwoot account.
Use cases include automating customer support workflows by fetching predefined canned responses that agents can use to reply quickly to common queries. For example, a support team might use this node to pull all available canned responses and display them in a dashboard or use them in automated messaging flows.
Properties
| Name | Meaning |
|---|---|
| Continue on Fail | Whether the node should continue processing subsequent items if this operation fails. |
| Debug Logging | Whether to output detailed request and response information to the console for debugging. |
These properties control error handling behavior and logging verbosity during execution.
Output
The node outputs an array of JSON objects, each representing a canned response retrieved from the Chatwoot API. Each item corresponds to one canned response and includes fields such as:
id: Numeric ID of the canned response.short_code: The short code identifier for the canned response.content: The text content of the canned response.- Other metadata fields as returned by the Chatwoot API.
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 and account ID to be configured in the credentials.
- Uses HTTP requests to communicate with the Chatwoot REST API endpoints.
Troubleshooting
- Invalid JSON Errors: If custom JSON input is used elsewhere (not in this operation), invalid JSON will cause errors. Ensure JSON syntax is correct.
- Authentication Errors: Missing or incorrect API keys will result in authentication failures. Verify credentials are correctly set up.
- API Endpoint Errors: Incorrect account IDs or resource IDs may cause 404 or other HTTP errors. Confirm IDs are valid.
- Continue on Fail: Enabling "Continue on Fail" helps avoid complete workflow failure when some items cause errors.
- Debug Logging: Enable debug logging to see detailed HTTP request/response info in the console, useful for diagnosing issues.