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 interacts with the ChatWoot API to retrieve detailed information about a single custom filter associated with a specific account. It is useful when you need to fetch and display or process the configuration details of a particular custom filter within an automation workflow. For example, you might use this node to verify filter settings before applying them elsewhere or to audit filter configurations programmatically.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account to which the custom filter belongs. |
| Custom Filter Id | The numeric ID of the custom filter whose details you want to retrieve. |
Output
The node outputs JSON data containing the detailed information of the specified custom filter. This typically includes all properties and settings defined for that filter in ChatWoot. The output can be used downstream in workflows for decision-making, logging, or further processing.
No binary data output is produced 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 depends on the
@devlikeapro/n8n-openapi-nodepackage and the bundled OpenAPI specification (openapi.json) for request construction.
Troubleshooting
- Invalid Account Id or Custom Filter Id: If the IDs provided do not exist or are incorrect, the API will likely return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access custom filters.
- Network Issues: Connectivity problems to the ChatWoot instance URL will cause request failures. Check network access and URL correctness.
- Malformed Input: Providing non-numeric values for the IDs may cause validation errors.
Links and References
- ChatWoot API Documentation (for understanding custom filter endpoints)
- n8n Documentation (for general usage of API nodes and credentials)