Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node operation updates a single "View Filter Group" object in the connected system via the Twenty API. It allows users to modify properties of an existing filter group, such as its logical operator, position within a parent group, and hierarchical relationships. This is useful when managing complex filtering criteria for views, enabling dynamic adjustment of how data is filtered and grouped.
Practical examples include:
- Changing the logical operator (AND, OR, NOT) to alter how filters combine.
- Reassigning a filter group to a different parent group to restructure nested filters.
- Updating the position of a filter group within its parent to control evaluation order.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the View Filter Group object to update. This is required to specify which filter group will be modified. |
| Depth | Determines the level of nested related objects included in the response after update: 0 returns only the primary object; 1 includes directly related objects; 2 includes related objects of those related objects. |
| View Id | Identifier of the view to which this filter group belongs. |
| Parent View Filter Group Id | Identifier of the parent filter group under which this filter group is nested. Useful for organizing filter groups hierarchically. |
| Logical Operator | The logical operator used by this filter group to combine its filters. Options are AND, OR, or NOT, controlling how multiple filters are evaluated together. |
| Position In View Filter Group | Numeric position indicating the order of this filter group within its parent group. This controls the sequence in which filter groups are applied or displayed. |
Output
The node outputs JSON data representing the updated View Filter Group object. The structure reflects the current state of the filter group after the update, including any nested related objects depending on the specified depth. No binary data output is involved.
Dependencies
- Requires an active connection to the Twenty API with appropriate authentication credentials (e.g., an API key or token).
- The node uses HTTP requests to interact with the API endpoint responsible for updating View Filter Groups.
- Proper configuration of the API base URL and authentication in n8n credentials is necessary.
Troubleshooting
- Missing or invalid Id: The update operation requires a valid filter group ID. Ensure the Id property is correctly set; otherwise, the API will reject the request.
- Invalid logical operator value: Only "AND", "OR", or "NOT" are accepted. Using other values will cause errors.
- Incorrect nesting or parent ID: Setting a non-existent parent filter group ID may result in failure or unexpected behavior.
- API authentication errors: Verify that the API credentials are valid and have sufficient permissions to perform update operations.
- Depth parameter misuse: Providing an unsupported depth value might lead to incomplete or excessive data in the response.
Links and References
- Twenty API Documentation (general reference for API endpoints and data models)
- n8n Documentation (for configuring credentials and using HTTP request nodes)