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 interacts with the Twenty API to retrieve detailed information about a specific "View Filter" object by its unique identifier. It is useful when you need to fetch a single view filter's data, including optionally nested related objects, for further processing or decision-making in your workflow.
Common scenarios include:
- Fetching configuration details of a particular view filter to customize UI or reports.
- Retrieving metadata for validation or audit purposes.
- Integrating with other systems that require detailed filter information.
For example, you might use this node to get a view filter by its ID and then use the retrieved data to dynamically adjust subsequent workflow steps based on the filter’s properties.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the view filter object to retrieve. This is required. |
| Depth | Determines how much related nested data to include in the response: - 0: Only the primary view filter object. - 1: Primary object plus directly related objects. - 2: Primary object, directly related objects, and their related objects. |
Output
The node outputs JSON data representing the requested view filter object. The structure includes the main view filter fields and, depending on the Depth property, may also include nested related objects up to two levels deep.
If binary data were involved (not indicated here), it would typically represent files or media associated with the view filter, but this node focuses on JSON data only.
Dependencies
- Requires an API key credential for authenticating requests to the Twenty API.
- The node expects the base URL for the API to be configured via credentials.
- No additional external dependencies are needed beyond the Twenty API access.
Troubleshooting
- Missing or invalid Id: The node requires a valid view filter ID. Ensure the ID is correct and exists in the system.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Depth parameter misuse: Using a depth value outside the allowed range (0, 1, 2) may cause unexpected results or errors.
- Network issues: Check connectivity to the Twenty API endpoint if requests time out or fail.
Links and References
- Twenty API Documentation (replace with actual URL)
- n8n documentation on API node usage