Error Trigger
Trigger node for error-handling branches that receive error data when the agent's own run fails.
Written By Philippe
Last updated About 4 hours ago
Error Trigger
β Verified β Tested, confirmed working on indie.money
What It Does
The entry point for an in-workflow error-handling branch. When the agent's own run fails during execution, this trigger's branch receives the error details β including the error message, which node failed, and the execution ID.
How It Works
- Add an Error Trigger node to your agent's own workflow
- The agent runs and encounters an error (e.g., a Stop and Error node, or an API failure)
- The platform detects the failure and runs the Error Trigger's branch within the same execution
- The Error Trigger branch receives the error payload
- Your agent processes the error (send notification, log it, retry, etc.)
Error Payload
The Error Trigger receives this data structure:
Setting Up an Error Workflow
- Add an Error Trigger node to your agent's workflow
- Add processing nodes off the Error Trigger (e.g., send a Slack message, log to a spreadsheet)
- Publish and activate the agent
Compatibility
Tips
- The error branch runs within the same execution as the agent that failed β no separate budget; its cost is inherited into the parent run
- Error workflows do not trigger their own error workflows, preventing infinite loops
- Use the error payload fields in expressions to build informative notifications
- Combine with the HTTP Request node to send error alerts to external services
Status
This integration is fully tested and verified on indie.money.