The canvas
When you open a workflow, you land on the canvas — a zoomable, pannable workspace where your steps appear as connected cards. Each card shows the step type, a summary of its configuration, and its connection to the next step. You can drag cards to rearrange them and zoom with the scroll wheel or the zoom controls in the bottom-right corner. The sidebar on the right opens whenever you click a step, showing its full configuration panel. Changes auto-save as you edit.Creating a workflow
Open the Workflows tab
From your form’s detail page, click the Workflows tab. Then click New workflow to open a blank canvas.Give your workflow a name in the top-left field — something like “Notify team on new lead” works better than the default “Untitled workflow” when you’re managing several at once.
Add a trigger
Every workflow begins with a trigger. Click the + Add trigger card at the top of the canvas to open the trigger picker.Choose the trigger that fits your use case — for example, Form submitted to fire on every new submission, or Form submitted with condition to target specific responses. See Triggers for the full list.After selecting a trigger, configure any required options in the sidebar (such as the field condition to match) and click Save trigger.
Add your first action step
Click + below the trigger card to open the action picker. Available action types:
Select an action, complete its configuration in the sidebar, and click Save step.
| Action | What it does |
|---|---|
| Send email | Send a plain-text or HTML email to one or more addresses |
| Webhook | POST submission data to any URL |
| Integration | Connect to a native integration (Slack, Google Sheets, HubSpot, etc.) |
| Delay | Wait a set amount of time before continuing |
| Condition branch | Split the workflow into two paths based on a logical condition |
Connect additional steps
After saving a step, click + at the bottom of that card to add the next step in the sequence. You can chain as many steps as needed.When you use a Condition branch step, two output paths appear — one for when the condition is
true and one for false. Click + on each path independently to build out separate branches.Use submission data in your steps
Most action fields support variable substitution. Type Variables are resolved at runtime with the actual values from each submission, so one workflow template works for every response.
{{ in any text field to open the variable picker, which lists every field from your form plus metadata like submission timestamp and respondent IP address.Common variables:Field variable names match the field key set in the form builder, not the label displayed to the respondent. To check a field’s key, open the field settings in the form builder and look under Field key.
Test the workflow
Before enabling your workflow, test it against a real or sample submission to confirm every step behaves as expected.
- Click Test workflow in the top toolbar.
- Choose a recent submission from your form, or click Use sample data to generate placeholder values.
- Click Run test. Each step will execute in sequence and show a green check (success) or red X (failure) alongside a detailed log.
Enable the workflow
Once you’re satisfied with the test results, toggle the Enabled switch in the top-right corner of the canvas to turn the workflow on. The status indicator turns green, and the workflow will start firing on new trigger events immediately.To pause a workflow without deleting it, toggle the same switch off. All steps and configuration are preserved.
Enabling and disabling workflows
You can enable or disable any workflow from:- The canvas — use the toggle in the top-right corner.
- The Workflows tab — use the toggle in the workflow list without opening the canvas.
Managing multiple workflows
A single form can have multiple workflows, each with its own trigger. For example, you might have one workflow that fires on every submission to log data to Google Sheets, and a second workflow that fires only when a respondent selects “Enterprise” in a plan picker to notify your sales team in Slack. Workflows run independently and in parallel — the completion of one does not affect another. If two workflows have the same trigger, both will fire for each matching event.Viewing run history
Click Run history in the top toolbar to see a log of every time the workflow has fired. Each entry shows:- The submission that triggered the run
- The timestamp
- Whether all steps succeeded or any step failed
- Per-step logs including the data sent and the response received
