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
Canned Response → Update Canned Response In Account
AI-generatedOverview
This node interacts with the ChatWoot API to update an existing canned response within a specified account. Canned responses are predefined message templates that can be quickly inserted during conversations, improving efficiency and consistency in communication.
Typical use cases include:
- Updating the content or short code of a canned response to reflect new information or corrections.
- Managing canned responses programmatically as part of customer support workflows.
- Automating updates to multiple canned responses across different accounts.
For example, a support team might use this node to update the message content of a canned response that provides troubleshooting steps, ensuring all agents have the latest instructions.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account where the canned response exists and will be updated. |
| Id | The numeric ID of the specific canned response to update. |
| Content | The new message content for the canned response. |
| Short Code | A short code string for quick access to the canned response (e.g., a shortcut keyword). |
Output
The node outputs JSON data representing the updated canned response object returned by the ChatWoot API. This typically includes fields such as the canned response's ID, updated content, short code, timestamps, and possibly metadata about the account or user who made the update.
No binary data output is expected from this operation.
Dependencies
- Requires an active connection to the ChatWoot API.
- Needs an API authentication token configured in the node credentials to authorize requests.
- The base URL for the ChatWoot instance must be set in the credentials configuration.
Troubleshooting
- Invalid Account Id or Canned Response Id: If the IDs provided do not exist or are incorrect, the API will return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API tokens will cause authorization failures. Ensure the API key credential is correctly configured.
- Empty Content or Short Code: Providing empty strings for content or short code may result in incomplete updates or validation errors. Confirm that required fields are properly filled.
- API Rate Limits: Frequent updates may hit rate limits imposed by the ChatWoot API. Implement retry logic or reduce request frequency if needed.
Links and References
- ChatWoot API Documentation – Official API reference for managing canned responses and other resources.
- ChatWoot Canned Responses Guide – Overview of canned responses usage in ChatWoot.