# Capture error on any node WITHOUT a "Stop and Error" node

**URL:** <https://community.n8n.io/t/capture-error-on-any-node-without-a-stop-and-error-node/47715>\
**Category:** Feature Requests\
**Created:** [June 3, 2024, 10:44am UTC](https://community.n8n.io/t/capture-error-on-any-node-without-a-stop-and-error-node/47715 "2024-06-03T10:44:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![scottyb](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@scottyb](https://community.n8n.io/u/scottyb)\
**Post date:** [June 3, 2024, 10:44am UTC](https://community.n8n.io/t/capture-error-on-any-node-without-a-stop-and-error-node/47715/1 "2024-06-03T10:44:40Z")

</div>

Is it possible to trigger an error workflow when there is an error anywhere in a workflow?

At the moment, it only seems possible to trigger an error workflow when using the “Stop and Error” node.

With complex workflows, where there are dozens of nodes, adding a “Stop and Error” for every external API, code function and so on just isn’t practical.

It would be great if there was an option to simply trigger an error workflow from ANY error in a workflow WITHOUT having to using a Stop and Error node.

Basically, a good old fashioned “try / catch” approach for a workflow.

---

<div class="post-metadata">

**Author:** ![octionic](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/octionic/32/42872_2.png) [@octionic](https://community.n8n.io/u/octionic)\
**Post date:** [June 3, 2024, 3:12pm UTC](https://community.n8n.io/t/capture-error-on-any-node-without-a-stop-and-error-node/47715/2 "2024-06-03T15:12:40Z")

</div>

You can define a second output of a node which you can use to handle the error.

 ![Screenshot 2024-06-03 at 5.08.06 PM](https://europe1.discourse-cdn.com/n8n/original/3X/5/f/5fb6dcd86f90cec5d880064eecbb7f8e6ffc9c40.png)
