Actions35
- 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 - Delete operation, it deletes a specified canned response from a given account.
Use cases include automating the removal of outdated or irrelevant canned responses in your Chatwoot account, helping keep your response templates clean and up-to-date. For example, if you have a canned response that is no longer valid or needed, this node can programmatically delete it based on its ID.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric ID of the Chatwoot account where the canned response exists. |
| Canned Response ID | The numeric ID of the specific canned response to delete. |
| Continue on Fail | Whether to continue executing subsequent items if this delete operation fails (boolean). |
Output
The output JSON contains a single field indicating success:
{
"success": true
}
This confirms that the canned response was successfully deleted. If the deletion fails and Continue on Fail is false, the node will throw an error stopping execution. If Continue on Fail is true, the node outputs an error message in the JSON under an error key instead.
No binary data is produced by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Chatwoot API.
- The base URL for the Chatwoot instance must be set in the credentials.
- The node makes HTTP DELETE requests to the endpoint
/api/v1/accounts/{accountId}/canned_responses/{cannedResponseId}.
Troubleshooting
Common issues:
- Invalid or missing Account ID or Canned Response ID will cause the API call to fail.
- Insufficient permissions or invalid API credentials will result in authorization errors.
- Network connectivity problems may cause request failures.
Error messages:
"404 Not Found": The specified canned response or account does not exist. Verify IDs."401 Unauthorized"or"403 Forbidden": Check API credentials and permissions.- Other HTTP errors: Inspect the error message returned by the API for details.
To handle errors gracefully, enable the "Continue on Fail" option to allow processing of other items even if one fails.