As you can see in the screenshot, my workflow just stopped because of an error in the Send Email node.
I checked the Execution flow and there was no error message in the output that I could actually test with an IF node, the node just fails and stops everything.
I know I can set up error notifications via the workflow settings, but I’m looking for a way to branch the flow to another node specifically when this error happens. Any idea how I can catch this and keep the flow moving to a different branch?
In the send email node, go to the settings tab and change the on error option to continue working. This adds an error output to the node, allowing you to branch the flow and connect another node to handle the failure however you like.
@Orionpax
Hey! I’m learning n8n seriously and trying to understand how professionals sell workflows
to clients (exporting, VPS setup, ownership model).
Could you share how you usually approach this? How do you usually deliver an n8n workflow to a client using VPS while keeping credentials secure?
@shubh_works7, please create a new post with your question as this is non related to the original topic, already has a solution and will likely not receive new eyes to answer your question