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 single "View" object by its unique identifier. It is useful when you need to fetch specific data about a particular view, including optionally nested related objects up to two levels deep. Typical use cases include displaying detailed view information in dashboards, integrating view data into other workflows, or performing conditional logic based on view properties.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the View object to retrieve. This is required. |
| Depth | Determines how much related nested data to include in the response: - 0: Only the primary View object. - 1: The View plus its directly related objects. - 2: The View, its related objects, and their related objects (two levels deep). |
Output
The node outputs JSON data representing the requested View object. The structure includes the primary View's fields and, depending on the Depth parameter, may also include nested related objects. The exact shape depends on the API response but generally contains all relevant details of the View and its relationships as specified.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Twenty API.
- The base URL for the API is configured via credentials.
- The node uses the Twenty API version 1.0.3 OpenAPI specification internally.
Troubleshooting
- Missing or invalid Id: If the Id property is empty or incorrect, the API will likely return an error indicating the object was not found. Ensure the Id is correct and corresponds to an existing View.
- Authentication errors: If the API key credential is missing or invalid, authentication will fail. Verify that the API key is correctly set up in n8n credentials.
- Depth parameter misuse: Providing an unsupported depth value might cause unexpected results or errors. Use only 0, 1, or 2 as allowed.
- Network or API downtime: Connectivity issues or API service interruptions can cause request failures. Check network connectivity and API status.
Links and References
- Twenty API Documentation (Assumed official docs for further details)
- n8n Documentation on Creating Custom Nodes