🇬🇧 EN

🛑 Stop

Explicitly terminates the workflow run with a specified status — completed or failed. Use at the end of conditional branches to signal definitive outcomes clearly.

Category: Flow Control · Type identifier: stop

Overview

When a workflow reaches a Stop node, execution ends immediately. No further steps are executed regardless of what comes after it in the graph or the linear sequence. The run is recorded in the run history with the status and message you specify.

While a workflow that simply "runs out of steps" also finishes, the Stop node makes the intention explicit. This is especially important at the end of conditional branches, where you want to be clear about whether the branch represents a successful outcome, a deliberate early exit, or an error condition.

Stop is most commonly placed at the end of the false branch of a Logic Gate, at the end of each arm of a Switch, and anywhere you detect an unrecoverable error and want to surface a clear failure message in the run log.

Stop produces no output. Because execution terminates immediately, there are no output variables to reference in subsequent steps — there are none.

Configuration

Field	Status	Description
Status	Required	`completed` — the run finishes and is marked as successful. Use this for intentional early exits where everything went as expected. `failed` — the run finishes and is marked as failed. Use this for error conditions or business rule violations that should be visible as failures in the run history.
Message	Optional	A human-readable explanation logged alongside the run result. Visible in the run detail view. Supports `{{ variable }}` references. Keep it short and informative — this is what you will read when reviewing run history.

Output Data

None. The Stop node terminates execution. It does not produce any output variables.

Example Usage

Reject a workflow run when approval is denied

An approval workflow checks whether a reviewer has approved a request. If they have rejected it, the workflow should stop and record a clear failure message.

Add a Logic Gate node that checks:
Field: {{ review.output.decision }} Operator: equals Value: rejected
Connect the true port (decision equals rejected) to a Stop node.
Configure the Stop node:
Status: failed Message: Request rejected by {{ review.output.reviewer_name }} on {{ review.output.reviewed_at }}
Connect the false port (not rejected) to the next step in the approval workflow, which fulfils the request.

Early exit on missing data

Before processing an order, verify that the required fields are present. If critical data is missing, stop cleanly rather than allowing downstream steps to fail with cryptic errors.

// Logic Gate: order.output.customer_id is null → true branch → Stop Status: failed Message: Order {{ trigger.output.order_id }} is missing a customer ID. Processing aborted.

Tips & Notes

Use failed status for business rule violations. A failed status makes the run stand out in run history and can trigger alerting integrations. Reserve it for conditions that genuinely need attention.
Use completed for deliberate early exits. If you intentionally skip the rest of the workflow because nothing needs to happen (for example, "no orders to process today"), mark it as completed so it does not appear as an error.
Include context in the message. A message like "User not eligible" is less useful in run history than "User 4821 not eligible: plan is free, required premium". Use {{ variable }} references to embed dynamic values.
Not required at the end of every workflow. You only need a Stop node when you want to explicitly control the status or message. If a workflow just runs out of steps normally, it is automatically recorded as completed.

Related Nodes

Logic Gate — the most common node to place before a Stop, routing based on a condition.
Switch — place a Stop at the end of each Switch branch that should terminate execution.