Skip to content
LogoLogo

Workflow test runs

A test run runs the draft of a workflow one time, with the trigger input that you give. It shows what each node did. It saves nothing, so you can test a change before you publish it.

Where to start a test run

PageAddressContent
Test run…/workflows/<workflow>/testThe trigger form and the result. Open it with the Test tab of the workflow.

You must have the scope ORGANIZATION_WORKSPACE_UPDATE and each scope that the workflow uses. The page names each scope that you do not have.

Trigger input

TriggerInputMeaning
ActionOne input for each action fieldThe answer to that field. Nodes read it as trigger.action.responses.<key>. If a field is empty and not required, the run sends no answer for it.
EventEntity IDThe entity that the event is about. Nodes read it as trigger.entityId. An empty field uses the workspace.

Each action field gets the input for its type:

FieldInput
TextA text box.
NumberA number box. The value must be a number.
True or falseA checkbox.
RecordA box for JSON. The value must be valid JSON.
Field with optionsA list to choose one option.
Field with many valuesCheckboxes for options, or one value on each line.

A required field must have a value before the test run starts.

What runs

NodeIn a test run
Tool that reads, such as Search leads or an External API GET or HEADRuns.
Tool that writes, such as Create lead, Set lead labels or an External API POSTDoes not run. The result shows the input that it would send.
ConditionRuns, and shows the branch that it took.
WaitDoes not wait.

A later node that reads the output of a skipped node gets no value.

Result

StatusMeaning
SucceededThe node did its work.
SkippedThe tool writes, so the test run did not run it.
FailedThe node failed. The test run stopped at that node, and shows the reason.

Each node shows its input and its output. A test run does not show in Runs, and it does not create or change leads or labels.