Stop And Error

Description

The Stop And Error node interrupts the execution of the workflow branch by throwing an error with a custom message. It is used to halt the flow when an invalid condition is detected (for example a missing or incorrect value) and to record the reason in the execution trace.

It is equivalent to n8n’s Stop And Error node.

By returning an error, this workflow branch stops (a Floogos convention). The message supports dynamic variables, so it can include values from data to describe precisely what went wrong. It is typically placed after a decision or branching node, on the branch that represents the error case.

Configuration

Parameters

Parameter	Type	Required	Description
message	textarea	Yes	Error message that stops the workflow. Supports dynamic variables

Output

The node does not continue to a next node: it returns an error that stops the branch. The message is recorded in the trace:

{
  "error": {
    "message": "The lead has no valid email"
  }
}

The received data is preserved in the error output, but no downstream node runs on that branch.

Usage Examples

Stop if a required value is missing

{
  "label": "Invalid email",
  "message": "The lead has no valid email"
}

Placed on the “empty email” branch of a decision node, it halts the flow with a clear message.

Message with dynamic context

{
  "label": "Payment declined",
  "message": "Payment declined for order {{data.order_id}}: {{data.reason}}"
}

The message includes the order id and the reason taken from data, useful for diagnosing in the trace.

Notes

• It stops only the branch it runs on; other parallel branches of the workflow are not affected by this node itself
• The error is recorded in the logger and in the workflow execution trace
• The message field supports dynamic and cross-node variables: {{data.field}}, {{@NodeName.field}}
• Does not require credentials