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 workflow version by its unique identifier. It is particularly useful when you need to fetch metadata or configuration details of a particular version of a workflow, for example, to audit changes, compare versions, or trigger actions based on version-specific data.
A practical use case would be in automation pipelines where workflows evolve over time, and you want to programmatically access a certain version's details to ensure compatibility or to document changes.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the workflow version object you want to retrieve. |
| Depth | Determines how much related nested data to include in the response: - 0: Only the primary workflow version data. - 1: Includes directly related objects. - 2: Includes related objects and their related objects (two levels deep). |
Output
The node outputs JSON data representing the requested workflow version. The structure includes the primary workflow version details and, depending on the Depth property, may also include nested related objects up to two levels deep. This allows flexible retrieval of associated metadata or linked entities without additional requests.
No binary data output is expected from this node.
Dependencies
- Requires an API key credential to authenticate against the Twenty API.
- The node uses the base URL configured via credentials.
- No other external dependencies are indicated.
Troubleshooting
- Missing or invalid Id: If the
Idproperty is empty or incorrect, the API will likely return an error indicating the object was not found. Ensure the correct workflow version ID is provided. - Authentication errors: If the API key or domain credentials are missing or invalid, authentication will fail. Verify that the credentials are correctly set up in n8n.
- Depth parameter misuse: Providing an unsupported depth value might cause unexpected results or errors. Use only 0, 1, or 2 as specified.
- API rate limits or downtime: If the API service is unavailable or rate-limited, the node will throw errors. Check the API status and retry later.
Links and References
- Twenty API Documentation (Assumed official API docs for reference)
- n8n Documentation on Creating Custom Nodes