Actions3
Overview
The node integrates with CleverFlow to create, retrieve, or process runs within a CleverFlow workspace. Specifically for the Create operation, it allows users to create a new run in a specified workspace and workflow by providing relevant data fields. This is useful for automating workflows that require initiating runs in CleverFlow based on external triggers or data inputs.
Practical examples include:
- Automatically starting a new workflow run in CleverFlow when a form is submitted.
- Creating runs with custom data fields populated dynamically from other systems.
- Integrating CleverFlow runs into larger automation pipelines managed by n8n.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | Select the CleverFlow workspace where the run will be created. Can choose from a list or specify an ID via expression. |
| Workflow Name or ID | Select the workflow within the chosen workspace to run. Options depend on the selected workspace. |
| Run Name | Optional name for the new run. If not provided, the run may be unnamed or use a default naming scheme. |
| Data Fields | A collection of key-value pairs representing fields to populate in the run. Each field is selected from available workflow fields and assigned a string value. Multiple fields can be added. |
Output
The node outputs a JSON array containing the result of the run creation. The json output typically includes details about the newly created run such as its identifier, status, and any metadata returned by CleverFlow.
No binary data output is indicated for this operation.
Dependencies
- Requires an API authentication token credential for CleverFlow (configured in n8n credentials).
- Depends on CleverFlow API endpoints to fetch workspaces, workflows, and workflow fields dynamically.
- Network access to CleverFlow's API service is necessary.
Troubleshooting
- Missing or invalid workspace/workflow IDs: Ensure the workspace and workflow IDs are correct and accessible with the provided credentials.
- Field mapping errors: If a specified field does not exist in the selected workflow, the node may error out or skip the field depending on configuration.
- Authentication failures: Verify that the API key or token credential is valid and has sufficient permissions.
- Empty required fields: Required fields must be provided; missing values may cause the API call to fail.
- API rate limits or downtime: Temporary CleverFlow API issues can cause failures; retry after some time or check CleverFlow status.
Common error messages usually relate to invalid parameters or authentication issues and can be resolved by verifying input values and credentials.
Links and References
- CleverFlow Official Documentation (for API and workflow setup)
- n8n Expressions Documentation (for dynamic parameter expressions)