Skip to Content
Docs are being rebuilt — start at Introduction → How it works.
AutomationWorkflows (Flows)Testing a workflow

Testing a workflow

Use manual execution to test an active workflow before relying on it for recurring or event-based automation.

What you can do here

  • Run an active workflow from the Flows tab.
  • Provide optional JSON execution parameters.
  • Trigger another run from the execution history page.
  • Open execution details and inspect step input and output.

How to run from the Flows tab

  1. Open Automation from the sidebar.
  2. Stay on the Flows tab.
  3. Find a workflow with the Active status.
  4. Click Execute.
  5. Leave Execution Parameters empty for a normal manual run, or enter a JSON object if the workflow expects parameters.
  6. Click Execute Workflow.
Execute Workflow dialog where optional JSON execution parameters can be entered before running a workflow
FieldRequiredAccepted valuesWhat it controls
Execution ParametersNoValid JSON object, or blankCustom input passed into the workflow execution.

How to run from execution history

  1. Open the workflow’s execution history.
  2. Click Trigger Execution.
  3. Wait for the execution table to refresh.
  4. Open the new run from the actions menu when you need details.
Execution History page with Trigger Execution available above the execution table

How to review the result

  1. In execution history, open the actions menu for a run.
  2. Click View Details.
  3. Review Started At, Duration, Triggered By, and Resources.
  4. Expand Workflow Steps rows to compare the step input and output.
Execution Details page with an expanded workflow step showing input and output payloads

Debug checklist

  • If Execute says Not Active, open the flow in the builder and activate it before testing.
  • If a step output is empty, inspect the previous step input first.
  • If a run fails, compare it with the most recent completed execution.
  • If manual parameters are needed, use valid JSON and keep the payload small while testing.