Feature Request: Error Nodes for Workflows

[Lapotor]

What's the idea?

Add a dedicated "Error Node" to the Workflow builder — a node you can place on any branch to explicitly halt a workflow and mark it as failed, rather than letting it run into an empty dead-end branch that gets marked as successful.

---

Why would this be useful?

Right now, if a workflow hits a condition that isn't met, the execution just runs into an empty branch — and still gets marked as successful. There's no way to communicate to the person who triggered it that something was actually wrong or incomplete. An Error Node would let workflow builders add intentional failure paths with a clear, human-readable explanation, making workflows much more self-sufficient and user-friendly.

---

What could it look like?

At its simplest, an Error Node just emits an error state — halting the workflow and marking the run as failed in the execution history. That alone would already be a big improvement over the current silent dead-end behavior.

From there, optional enhancements could include:

• A custom error message shown to the person who triggered the workflow (e.g. "The Close Date is missing on this deal — please fill it in and try again.")
• An optional notification to the executor, the record owner, or another team member
• Variable interpolation (like {{fieldName}}) to make messages more dynamic

---

Example

flowchart TD
    A([🔔 Trigger: Deal updated]) --> B{Condition\nRequired fields filled?}
    B -->|✅ Yes| C[Send follow-up email]
    C --> D([✅ Workflow successful])
    B -->|❌ No| E[🛑 Error Node]
    E --> F([❌ Workflow failed])

Loading

---

Similar concepts in other tools

n8n has a dedicated Stop and Error node that does exactly this — it lets you explicitly halt a workflow and throw a custom error message at any point, which then marks the execution as failed rather than successful. This is a great reference for the core behavior. Make has error handlers on modules and Zapier has built-in error paths as well, but the n8n concept maps most closely to what's described here.

---

_{I used Claude Sonnet 4.6 by Anthropic to help me structure and write this idea up.}

[BOHEUS]

CC: @thomtrp @Bonapara