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
Custom Filters → Delete A Custom Filter
AI-generatedOverview
This node interacts with the ChatWoot API to manage custom filters within an account. Specifically, the "Delete A Custom Filter" operation allows users to remove a custom filter by specifying its unique identifier and the associated account ID. This is useful for automating the cleanup or management of filters in ChatWoot, such as removing outdated or unnecessary filters programmatically.
Practical examples include:
- Automatically deleting custom filters that are no longer relevant based on certain criteria.
- Integrating filter management into broader workflows that maintain ChatWoot accounts.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the ChatWoot account where the custom filter exists. |
| Custom Filter Id | The numeric ID of the specific custom filter to delete. |
Output
The node outputs JSON data representing the response from the ChatWoot API after attempting to delete the specified custom filter. Typically, this will include confirmation of deletion or error details if the operation failed.
If the API supports it, the output may also contain metadata about the deleted filter or status messages. No binary data output is expected for this operation.
Dependencies
- Requires an active connection to the ChatWoot API.
- Needs an API authentication token configured in the node's credentials to authorize requests.
- The base URL for the ChatWoot instance must be provided via credentials.
Troubleshooting
Common issues:
- Invalid or missing Account Id or Custom Filter Id will cause the API call to fail.
- Authentication errors if the API key/token is incorrect or expired.
- Network connectivity problems preventing access to the ChatWoot API endpoint.
Error messages:
- "Unauthorized" or "Authentication failed": Check that the API credentials are correctly set up and valid.
- "Not Found": Verify that the Account Id and Custom Filter Id exist and are correct.
- "Bad Request": Ensure that the input parameters are properly formatted and required fields are provided.
Resolving these typically involves verifying input values, refreshing credentials, and ensuring network access.
Links and References
- ChatWoot API Documentation (for detailed API endpoints and usage)
- n8n documentation on creating and using API credentials