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 allows you to retrieve detailed information about a specific workflow run by its unique identifier. It is useful when you want to inspect the status, results, or metadata of a particular execution instance of a workflow. For example, you might use this node to fetch the outcome of a workflow triggered earlier, verify its success or failure, or analyze its data for reporting or debugging purposes.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the workflow run you want to find. This is a required string input. |
| Depth | Determines how much related nested information to include in the response: - 0: Only the primary workflow run's information. - 1: Includes the workflow run and its directly related objects. - 2: Includes the workflow run, its related objects, and their related objects as well. |
Output
The node outputs a JSON object representing the workflow run identified by the provided Id. Depending on the selected Depth level, this output can range from basic details about the workflow run to a more comprehensive structure including related entities (such as tasks, executions, or logs) nested up to two levels deep.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential to authenticate requests against the Twenty API.
- The node uses the base URL configured in the credentials to send requests.
- No additional external dependencies are needed beyond the API access.
Troubleshooting
- Invalid or missing Id: If the provided Id does not correspond to any existing workflow run, the node will likely return an error indicating that the object was not found. Verify the Id value before running.
- Authentication errors: Ensure that the API key credential is correctly set up and has sufficient permissions to access workflow run data.
- Depth parameter misuse: Providing an unsupported depth value may cause unexpected responses or errors. Use only 0, 1, or 2 as specified.
- Network issues: Connectivity problems with the API endpoint will result in request failures; check network settings and API availability.
Links and References
- Twenty API Documentation (general reference for the API endpoints and data structures)
- n8n documentation on working with API credentials