Actions3
Overview
The node interacts with CleverFlow to manage "runs," which are workflow executions or process instances within the CleverFlow platform. Specifically, the Get operation retrieves details about a particular run either by its unique identifier (UID) scoped within a workspace or by a numeric run ID.
This node is useful when you want to fetch the status, metadata, or results of a specific run in CleverFlow as part of an automation workflow. For example, after triggering a run creation, you might want to retrieve its current state or output data for further processing or reporting.
Properties
| Name | Meaning |
|---|---|
| Run Identifier Type | Choose how to identify the run: - Run UID (Requires Workspace): Identify by UID within a workspace (e.g., PL-1). - Run ID: Identify directly by numeric ID (e.g., 110796). |
| Workspace Name or ID | Required if using Run UID identification. Select the workspace containing the run. |
| Run UID | The unique string identifier of the run (e.g., PL-1). Required if Run Identifier Type is "uid". |
| Run ID | The numeric identifier of the run (e.g., 110796). Required if Run Identifier Type is "id". |
Output
The node outputs a JSON array containing the retrieved run's data from CleverFlow. This typically includes all relevant information about the run such as its identifiers, status, timestamps, and any associated metadata returned by the CleverFlow API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to CleverFlow via an API key credential configured in n8n.
- The node depends on CleverFlow's REST API endpoints to fetch run data.
- Workspace and run identifiers must be valid and accessible with the provided credentials.
Troubleshooting
- Invalid Run Identifier: If the specified Run UID or Run ID does not exist or is incorrect, the node will likely return an error indicating the run was not found. Verify the identifier and workspace selection.
- Missing Workspace: When using Run UID, the workspace must be specified and valid. Omitting or selecting an incorrect workspace will cause errors.
- Authentication Errors: Ensure the API key credential is correctly set up and has permissions to access the requested workspace and runs.
- Network Issues: Connectivity problems with CleverFlow API endpoints can cause timeouts or failures; check network and API availability.
Links and References
- CleverFlow Official Documentation (for API and run concepts)
- n8n Expressions Documentation (for dynamic property expressions)