Actions113
- 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
- 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
Overview
This node integrates with the ChatWoot API to add a new canned response to a specified account. Canned responses are predefined message templates that can be quickly inserted into conversations, improving efficiency and consistency in customer support or communication workflows. This node is useful for automating the management of canned responses within ChatWoot accounts, such as adding new quick-reply messages programmatically.
Practical examples:
- Automatically creating standardized replies for common customer inquiries.
- Bulk uploading multiple canned responses from an external source.
- Integrating with other systems to dynamically generate and add canned responses based on user input or events.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the ChatWoot account where the canned response will be added. |
| Content | The message content of the canned response to be saved. |
| Short Code | A short code string used for quick access to this canned response within ChatWoot UI. |
Output
The node outputs JSON data representing the result of the API call to add the canned response. This typically includes details about the newly created canned response such as its ID, content, short code, timestamps, and any metadata returned by the ChatWoot API.
No binary data output is involved.
Dependencies
- Requires an active ChatWoot API credential configured in n8n, including the base URL and an API authentication token.
- Depends on the ChatWoot REST API being accessible and the provided account ID being valid.
- Uses standard HTTP headers for JSON content type and accepts JSON responses.
Troubleshooting
- Invalid Account ID: If the account ID does not exist or the authenticated user lacks permission, the API will return an error. Verify the account ID and credentials.
- Missing Required Fields: Ensure that the "Account Id" and "Content" fields are provided; otherwise, the request may fail validation.
- API Authentication Errors: Check that the API key/token is correctly set up and has sufficient permissions.
- Network Issues: Confirm network connectivity to the ChatWoot API endpoint.
- Error Messages: Common errors include 401 Unauthorized (invalid credentials), 404 Not Found (account or endpoint not found), and 400 Bad Request (invalid input). Review the error message details for guidance.