Actions3
Overview
The node "CleverFlow" integrates with the CleverFlow platform to manage workflow runs. Specifically, the Process Tally Form operation processes webhook data received from a Tally form submission and creates a corresponding run in CleverFlow.
This operation is useful when you want to automate the ingestion of form responses collected via Tally into CleverFlow workflows for further processing or automation. For example, after a user submits a survey or registration form on Tally, this node can automatically create a new run in CleverFlow representing that submission, enabling downstream automation such as notifications, data enrichment, or analytics.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | Select or specify the CleverFlow workspace where the run will be created. |
| Workflow Name or ID | Select or specify the workflow within the chosen workspace to associate the run with. |
| Run Name | Optional name for the created run. Defaults to a combination of the Tally form name and response ID if not specified. |
| Input Type | Choose how to process the incoming Tally webhook data: - Direct Webhook Data: Use the entire input data directly. - JSON Field: Extract data from a specific JSON field in the input. |
| JSON Field | (Shown only if Input Type is "JSON Field") The name of the JSON field containing the Tally webhook data to process. |
| Skip Invalid Fields | If enabled, fields from the Tally form that cannot be mapped to CleverFlow fields will be skipped instead of causing an error. |
| Skip Empty Values | If enabled, fields with empty values will not be sent to CleverFlow, preventing creation of runs with empty data fields. |
Output
The node outputs a JSON array containing the result of the processed Tally form run creation in CleverFlow. Each item in the output corresponds to one processed form submission and includes details about the created run.
The exact structure depends on the CleverFlow API response but typically includes identifiers, status, and metadata about the created run.
No binary data output is produced by this operation.
Dependencies
- Requires an active CleverFlow account and API access.
- Requires an API authentication credential configured in n8n to connect to CleverFlow.
- The node dynamically loads available workspaces and workflows from CleverFlow to populate selection options.
- The node expects to receive webhook data from Tally forms, either directly or nested inside a JSON field.
Troubleshooting
- Invalid or missing workspace/workflow IDs: Ensure the selected workspace and workflow exist and are accessible with the provided API credentials.
- Malformed webhook data: If the input data does not match expected Tally webhook format, the node may fail to map fields correctly. Verify the webhook payload structure.
- Field mapping errors: If "Skip Invalid Fields" is disabled, unmapped fields will cause errors. Enable skipping invalid fields to avoid failures due to unexpected form fields.
- Empty values handling: If important fields are empty and "Skip Empty Values" is enabled, those fields won't be sent, which might lead to incomplete runs. Adjust this setting based on your data quality needs.
- API authentication errors: Check that the API key or token credential is valid and has sufficient permissions.