Automations
Try / Catch Node
3 min readnode-try-catch
Wrap a set of nodes in error handling so failures route to a fallback path instead of stopping the automation.
Try / Catch Node
Wraps one or more downstream nodes. If any wrapped node throws an error, execution routes to the Error Handler branch instead of stopping the entire automation run.
When to use it
- Gracefully handle a failed webhook call — log the error and continue the flow.
- Prevent a transient Twilio error from blocking the rest of the automation.
---
Required fields
None — the node is configured by connecting nodes inside the Try block and connecting an error handler node to the Catch handle.
---
Variables available inside Catch branch
| Variable | Description |
|---|---|
{{variables.errorMessage}} | Human-readable error message from the failed node |
{{variables.errorNode}} | Name of the node that threw the error |
---
Step-by-step setup
- Add a Try/Catch node.
- Connect the nodes you want to protect inside the Try branch (e.g. a webhook call, a Twilio SMS).
- Connect a fallback node (e.g. Add Lead Note, Post to Slack) to the Catch handle.
- In the Catch branch, use
{{variables.errorMessage}}to log what went wrong.
---
Example Catch branch config (Add Lead Note)
json
{
"note": "Automation error in node {{variables.errorNode}}: {{variables.errorMessage}}"
}
---
Tips & gotchas
- Without Try/Catch, any node error stops the automation run and marks it as failed. With Try/Catch, you control what happens next.
- Use a Post to Slack node in the Catch branch to alert your team of critical failures in real time.
- Nested Try/Catch blocks are not supported — keep error handling at the top level of risky operations.