Actions35
- 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 contacts within a specified account. Specifically, the Delete Contact operation allows users to remove a contact by providing the account ID and the contact ID. This is useful in scenarios where you want to clean up or manage your contact list programmatically, such as removing outdated or invalid contacts from your customer support system.
Practical examples include:
- Automatically deleting contacts who have unsubscribed or requested removal.
- Cleaning up test or duplicate contacts after data imports.
- Integrating with other systems to synchronize contact deletions.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric ID of the account to which the contact belongs. |
| Contact ID | The numeric ID of the contact to be deleted. |
| Continue on Fail | Whether the node should continue executing subsequent items if this delete operation fails (true/false). |
Output
The output JSON for the Delete Contact operation is a simple confirmation object indicating success:
{
"success": true
}
This confirms that the contact was successfully deleted. No additional data about the deleted contact is returned.
The node does not output any binary data for this operation.
Dependencies
- Requires an active connection to the Chatwoot API via an API key credential configured in n8n.
- The base URL for the Chatwoot instance must be set in the credentials.
- The user must have appropriate permissions to delete contacts in the specified account.
Troubleshooting
Common issues:
- Invalid or missing Account ID or Contact ID will cause the API request to fail.
- Insufficient permissions or invalid API credentials can result in authorization errors.
- Network connectivity issues may prevent the node from reaching the Chatwoot API.
Error messages:
"404 Not Found": The specified contact or account does not exist. Verify the IDs."401 Unauthorized"or"403 Forbidden": Authentication failed or insufficient permissions. Check API credentials."400 Bad Request": Invalid input parameters. Ensure Account ID and Contact ID are valid numbers.
Resolution tips:
- Double-check that the Account ID and Contact ID are correct and correspond to existing entities.
- Confirm that the API key credential is valid and has necessary access rights.
- Enable "Continue on Fail" if you want the workflow to proceed even if deletion of some contacts fails.