Actions113
- 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
- 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
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 the configuration or metadata of a particular custom filter, for example, to display its settings in a UI, audit filters, or use the filter details in further automation workflows.
Practical examples include:
- Retrieving a custom filter's criteria to apply conditional logic in subsequent workflow steps.
- Auditing or reporting on existing custom filters within an account.
- Synchronizing filter configurations between ChatWoot and other systems.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the ChatWoot account to which the custom filter belongs. |
| Custom Filter Id | The numeric ID of the specific custom filter whose details are to be retrieved. |
Output
The node outputs JSON data representing the detailed information of the specified custom filter. This typically includes all properties and settings defined for that filter in ChatWoot, such as filter criteria, name, status, and any other metadata provided by the API.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The node uses the base URL configured in the credentials to make requests.
- The ChatWoot API must be accessible from the environment where n8n runs.
Troubleshooting
- Invalid Account Id or Custom Filter Id: If either ID is incorrect or does not exist, 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 API endpoint can cause request failures. Check network access and proxy settings if applicable.
- API Rate Limits: Excessive requests may lead to rate limiting; handle such errors by implementing retries or backoff strategies.
Links and References
- ChatWoot API Documentation (for detailed API endpoints and data structures)
- n8n Documentation (for general usage of nodes and credentials)