Test a Workflow
Test a Workflow in stages: choose a useful Trigger record, check mappings and conditions, test the receiving Actions, and finally verify a fresh event after activation. These checks answer different questions and can have different effects in connected apps.
Prepare the test
Use a Draft or a controlled copy of the Workflow. Select test resources and recognizable sample values before testing write operations. Confirm which account, workspace, channel, spreadsheet, or record each Action targets.
In the Trigger's Test stage, use Test step or Retest step, select an item under Choose an item to test, and inspect Record data. Continue makes that record available to downstream tests. The selected record does not limit which matching events an active Workflow receives.
A Live record comes from captured or retrieved data. An example is useful for preparing the graph but does not prove the provider delivered an event. Retest after changing the event, account, or selected resource; saved samples can describe an older configuration. See Triggers.
Know what each test does
| Control or check | Effect |
|---|---|
| Insert data | Shows available saved data for mapping. Opening it does not execute the producing Action. |
| Filter Test step | Evaluates the sample and reports Would continue or Would stop. It does not execute downstream Actions. |
| Formatter or JSON Patch test | Computes the output for the supplied sample; it does not execute the next Action. |
| Loop Preview items | Resolves the item list without running the Loop's Steps. |
| Loop Test step | Tests Steps on the first item. Actions make real requests; nested Loops test the first item at each level. |
| Only new items preview | Checks sample IDs without reading or changing saved deduplication history. |
| Action or AI Test step | Can call the real service, change data, send messages, or consume usage, even in a Draft. |
| Delay and Destination built-in previews | Simulate waiting and transport delivery; they do not prove actual timing or delivery. |
Test the actual mode you need. A successful preview of one item does not verify a full list, and a skipped test does not prove an Action succeeded.
Check data and decisions first
Open each receiving Step's Configure stage and review constants, From flow fields, and inserted text values. Check the selected upstream Step and whether the input expects a number, list, object, or text.
Test normal input, a missing optional field, an empty list, zero or false where valid, and a boundary that changes a Filter or Path decision. Confirm both the selected and skipped routes. Use Data mapping, Filters, and Paths for the relevant controls.
Test Actions and Loops deliberately
Before Test step, review the effective input and destination. After the call, inspect the output and the result in the provider. If the call times out, check the provider before retesting: it may already have created the row, message, or other result.
For a Loop, distinguish Preview items from Test the Loop on the first item. Save changes before the first-item test. It uses selected test data, or the latest available webhook run when no record is selected. Delays and Destinations are simulated, and Steps after the Loop are not called. See Loops.
Use Auto-validate
Open More Workflow actions → Auto-validate to check the graph and run tests. It leaves the Workflow's activation status unchanged, but it can execute real Actions and AI calls. Delays are simulated. Only new items uses a stateless preview and does not execute subsequent Steps on that route.
Validation results opens saved checks. Opening the report does not rerun them; Check again does. Inspect individual results and warnings rather than treating a green badge as proof of a fresh, complete execution. A badge can also reflect a test that was skipped.
Verify a normal execution
When ready, activate the Workflow and produce a fresh matching event. In Run history, confirm its version, Trigger input, selected routes, mapped Action inputs, and provider results. Verify actual Delay timing and Only new items behavior through normal runs.
For list processing, check multiple items and an item that fails. For repeated events, verify your duplicate prevention. If execution fails, use the retry guide to choose the smallest appropriate recovery scope.