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 allows you to delete an existing Agent Bot in the ChatWoot platform by specifying its unique identifier. It is useful for managing and maintaining your collection of agent bots, especially when certain bots are no longer needed or need to be removed due to updates in your automation strategy.
Practical examples include:
- Removing outdated or deprecated agent bots from your ChatWoot workspace.
- Cleaning up test or temporary bots created during development.
- Automating bot lifecycle management as part of a larger workflow.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the agent bot you want to delete. This is required to specify which bot should be removed. |
Output
The node outputs JSON data representing the response from the ChatWoot API after attempting to delete the specified agent bot. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The node expects the base URL of the ChatWoot instance to be configured in the credentials.
- Internet access to communicate with the ChatWoot API endpoint.
Troubleshooting
Common issues:
- Providing an invalid or non-existent agent bot ID will result in an error response from the API.
- Missing or incorrect API authentication credentials will prevent the node from executing successfully.
- Network connectivity problems can cause timeouts or failures in reaching the ChatWoot service.
Error messages and resolutions:
- "Agent bot not found": Verify that the provided Id corresponds to an existing agent bot.
- "Authentication failed": Check that the API key credential is correctly set up and has sufficient permissions.
- Timeout or network errors: Ensure stable internet connection and that the ChatWoot service URL is reachable.
Links and References
- ChatWoot API Documentation – For detailed information on agent bot management endpoints.
- n8n Documentation – General guidance on using API nodes and managing credentials.