Actions113
- 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
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Contacts API Actions
- Inbox API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Custom Attributes Actions
- Canned Response Actions
Overview
This node operation updates an existing canned response within a specified account in the ChatWoot system. Canned responses are predefined message templates that agents can quickly insert during conversations to save time and maintain consistency. This operation is useful when you need to modify the content or shortcut code of a canned response without creating a new one.
Practical examples:
- Updating the text of a canned response to reflect new company policies.
- Changing the short code for easier access by support agents.
- Correcting typos or adding additional information to an existing canned response.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account where the canned response exists and will be updated. |
| Id | The unique identifier of the canned response to update. |
| Content | The new message content for the canned response. |
| Short Code | A short code string used for quick access to the canned response. |
Output
The node outputs JSON data representing the updated canned response object as 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 involved in 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.
Troubleshooting
- Invalid Account Id or Canned Response Id: If either ID does not exist or is 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 credentials will cause authorization failures. Ensure the API key/token is correctly configured.
- Empty Content or Short Code: While these fields are optional, providing empty strings might overwrite existing values with blanks. Confirm intended changes before updating.
- API Rate Limits: Frequent updates may hit rate limits imposed by ChatWoot. Handle errors gracefully and consider retry mechanisms.