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 single workflow by its unique identifier. It is useful when you need to fetch the configuration or metadata of a specific workflow within your automation environment. For example, you might use this node to inspect a workflow's settings before making updates or to verify its structure during debugging.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the workflow you want to find. |
| Depth | Determines how much related nested data to include in the response: |
| - 0: Only the primary workflow object information. | |
| - 1: The workflow plus its directly related objects (no further nesting). | |
| - 2: The workflow, its directly related objects, and their related objects (two levels of nesting). |
Output
The output JSON contains the detailed data of the requested workflow. Depending on the selected depth, it includes the workflow's core properties and optionally nested related objects such as linked executions, triggers, or other associated entities. This enables comprehensive inspection of the workflow's structure and relationships.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential to authenticate requests to the external service providing workflow data.
- The node uses a base URL configured via credentials to connect to the API endpoint.
- No additional external dependencies are required beyond the provided API access.
Troubleshooting
- Invalid or missing Id: If the workflow ID is incorrect or not provided, the node will fail to find the workflow. Ensure the ID is accurate and non-empty.
- Insufficient permissions: Authentication failures may occur if the API key lacks rights to read workflows. Verify that the API key has appropriate access.
- Depth parameter misuse: Setting an unsupported depth value could lead to unexpected results or errors. Use only 0, 1, or 2 as specified.
- Network issues: Connectivity problems with the API endpoint can cause request failures. Check network availability and API server status.
Links and References
- API Documentation for Workflow Retrieval (replace with actual link if available)
- n8n Documentation on Working with Workflows