nodes / builtin / flow
Stop and Error
Stop the workflow and throw an error
Stop the run on purpose, with an error message you write.
What it does
Section titled “What it does”When data reaches Stop and Error, the node fails right away with your message. The run stops and shows as failed, as if any other step had failed. Nothing can be connected after it.
The message comes from a field named message in Fields. Without one, the error reads Error throwed by : <Stop and Error node>.
A failure from this node behaves like any other failure: a Try / Catch around it sends it to the Catch branch, and an Error Trigger workflow can react to it.
When to use it
Section titled “When to use it”- Stop when the data is wrong: after an IF, end the run if a required field is empty.
- Stop when a page didn’t load what you expected, instead of saving empty results.
- Make a run show as failed, with a clear reason, so an error workflow can alert you.
To simply drop items without failing, use Filter, or leave an IF branch unconnected.
Inputs and settings
Section titled “Inputs and settings”| Setting | Type | What it does |
|---|---|---|
| Fields (required) | Key-value pairs |
Add a field with the key message and your text as the value. Expressions work, so the message can say what went wrong, for example No price found for {{ $input.url }}. Other keys are ignored.
Outputs
Section titled “Outputs”This node has no output port: nothing runs after it on this branch.
Dependencies and credentials
Section titled “Dependencies and credentials”None. This node needs no connection and has no slots for other nodes.
Example workflow
Section titled “Example workflow”Stop when a page has no price:
- Get Element Data with Output field name
pricereads the price on the open page. - IF with the condition
{{ $input.price }}(String) Is Empty. - From True: Stop and Error with a field
messageset toNo price found on this page. - From False: Google Sheets appends the price.
Common issues
Section titled “Common issues”- The error says
Error throwed by : <Stop and Error node>. No field is named exactlymessage. Rename the key (it is case-sensitive). - The run fails even though the data looks fine. Data reached Stop and Error, so check the IF or Switch in front of it: open the run and see which branch the item took.
Related nodes
Section titled “Related nodes”- Try / Catch: handle the failure in a separate branch.
- Error Trigger: run a workflow when another one fails.
- IF: decide when to stop.