Actions36
- Account Actions
- Canned Response Actions
- Contact Actions
- Conversation Actions
- Inbox Actions
- Label Actions
- Message Actions
- Team Actions
- Webhook Actions
Overview
This node integrates with the Chatwoot API to manage canned responses within a Chatwoot account. Specifically, the Create operation for the Canned Response resource allows users to add new predefined message templates (canned responses) that can be reused in conversations or messages.
Typical use cases include:
- Automating common replies in customer support workflows.
- Quickly inserting frequently used phrases or instructions.
- Standardizing communication by using consistent response templates.
For example, a user might create a canned response with the short code "greeting" and content "Hello! How can I assist you today?" to quickly reply to new customer inquiries.
Properties
| Name | Meaning |
|---|---|
| Short Code | The unique short code identifier for the canned response (e.g., "greeting"). |
| Content | The full text content of the canned response (e.g., "Hello! How can I assist you today?"). |
| Continue on Fail | Whether the workflow should continue executing subsequent nodes if this operation fails. |
| Debug Logging | Whether to output detailed request and response information to the console for debugging. |
Output
The node outputs JSON data representing the created canned response as returned by the Chatwoot API. This typically includes fields such as the ID of the canned response, its short code, content, timestamps, and other metadata provided by Chatwoot.
No binary data is produced by this operation.
Dependencies
- Requires an active connection to the Chatwoot API via an API key credential.
- The node expects the Chatwoot account ID and base URL to be configured in the credentials.
- Network access to the Chatwoot instance's API endpoint is necessary.
Troubleshooting
- Invalid JSON Errors: Not applicable for this operation since it uses structured fields, but if extended to custom JSON, ensure valid JSON syntax.
- Authentication Failures: Ensure the API key credential is correctly set up with valid access tokens and account ID.
- API Endpoint Issues: Verify the base URL is correct and accessible.
- Continue on Fail: If enabled, errors will not stop the workflow but will be output as error messages in the node's JSON output.
- Debug Logging: Enable this property to see detailed logs of HTTP requests and responses, which helps diagnose issues like malformed requests or unexpected API responses.