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
Contacts → Contact Delete
AI-generatedOverview
This node interacts with the ChatWoot API to delete a specific contact from an account. It is useful in scenarios where you need to programmatically remove contacts, such as cleaning up outdated or invalid contact records, automating data management workflows, or integrating contact deletion into larger customer support or CRM processes.
For example, if you have a list of contacts that should no longer receive communications or be tracked, this node can automate their removal by specifying the account and contact IDs.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account from which the contact will be deleted. |
| Id | The numeric ID of the contact to delete. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this would include confirmation of successful deletion or details about any error encountered. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL for the ChatWoot instance must be configured in the node credentials.
- The node uses the ChatWoot REST API endpoint for deleting contacts.
Troubleshooting
Common issues:
- Invalid or missing account ID or contact ID will cause the API call to fail.
- Incorrect or expired API authentication token will result in authorization errors.
- Network connectivity problems may prevent the node from reaching the ChatWoot API.
Error messages:
- Authorization errors typically indicate issues with the API key or permissions.
- "Contact not found" errors suggest the specified contact ID does not exist under the given account.
- Validation errors occur if required parameters are missing or malformed.
To resolve these, verify that the account and contact IDs are correct, ensure the API key is valid and has sufficient permissions, and check network connectivity.
Links and References
- ChatWoot API Documentation (for detailed API endpoints and usage)
- n8n documentation on creating custom nodes