Flow.Documentation
BeginnerWorkflows

End: finish on purpose

5 steps± 4 minVideoVerified 22 Oct 2026
  1. Step 1 · Open Flow and create a workflow
  2. Step 2 · Add End and choose the result
  3. Step 3 · Put the steps in one line and save
  4. Step 4 · Run: successful
  5. Step 5 · End as failed, with a reason

Without End, a workflow stops after its last step and returns all the data it collected on the way. With an End step you decide how it ends: successful, with exactly the result you choose, or failed, with a reason everyone reads back on the run.

Watch the whole guide as a video5 steps in one film
Step 1 / 5

Open Flow and create a workflow

In the portal, under Environments, click Development and there Open; Flow opens in a new tab. There, click ＋ next to General, choose New workflow and give it a name. A new workflow starts with an Event trigger: the point where it begins.

  1. Click Development
Open Flow and create a workflow · Click Development
  1. Click Open ↗
Open Flow and create a workflow · Click Open ↗
  1. Click Add to General
Open Flow and create a workflow · Click Add to General
  1. Click New workflow
Open Flow and create a workflow · Click New workflow
  1. In Workflow name, type Guide · order received
Open Flow and create a workflow · In Workflow name, type Guide · order received
Step 2 / 5

Add End and choose the result

The trigger has sample data of an order, with customer, email and lines. A caller does not need all of that back. Add End and put under What does the workflow return (Code) only what it needs to know; with {{order.reference}} you take over the order number.

  1. Click Add node
Add End and choose the result · Click Add node
  1. Click End
Add End and choose the result · Click End
  1. In Name, type Done
Add End and choose the result · In Name, type Done
  1. Click Code
Add End and choose the result · Click Code
  1. In the result, type `{
Add End and choose the result · In the result, type `{; ; ;
  1. Click the dot of ‘Event trigger’
Add End and choose the result · Click the dot of ‘Event trigger’
  1. Click the dot of ‘Done’
Add End and choose the result · Click the dot of ‘Done’
Step 3 / 5

Put the steps in one line and save

Select the steps (click the first, and the others while holding Shift) and click Align horizontally: they then stand in one line and you read the workflow from left to right; a branch (such as No of an If / Else) gets its own row below. Fit to view puts everything in sight; then Save.

  1. Click ‘Event trigger’
Put the steps in one line and save · Click ‘Event trigger’
  1. Click ‘Done’ while holding Shift
Put the steps in one line and save · Click ‘Done’ while holding Shift
  1. Click Align horizontally
Put the steps in one line and save · Click Align horizontally
  1. Click Fit to view
Put the steps in one line and save · Click Fit to view
  1. Click Save
Put the steps in one line and save · Click Save
Step 4 / 5

Run: successful

The workflow ends at Done and returns only the order number and the status. The customer details from the trigger are no longer in it.

  1. Click Run
Run: successful · Click Run
Run: successful · Status: Completed.
Run: successful · Workflow ended.
Run: successful · order_number: DEMO-1042.
Step 5 / 5

End as failed, with a reason

Under How does the workflow end, choose Failed, with a message, and write down the reason; {{field}} works there too. Run again: the run is now Failed, with your reason. After an If / Else you use this to turn a request down neatly.

  1. Click the step ‘Done’
End as failed, with a reason · Click the step ‘Done’
  1. In How does the workflow end?, choose Failed, with a message
  2. In Message, type Order {{order.reference}} cannot be processed now
End as failed, with a reason · In How does the workflow end?, choose Failed, with a message; In Message, type Order {{order.reference}} cannot be processed now
  1. Click Run
End as failed, with a reason · Click Run
End as failed, with a reason · Status: Failed.
End as failed, with a reason · The reason, with the order number filled in.

This guide was carried out step by step on 22 Oct 2026 by an automated test on Flow (version 3e563176).