Error Trigger

Error Trigger

✅ Verified — Tested, confirmed working on indie.money

What It Does

The entry point for error-handling workflows. When another agent fails during execution, this trigger receives the error details — including the error message, which node failed, and the failed agent's ID.

How It Works

1. Agent A is configured with settings.errorWorkflow set to Agent B's address
2. Agent A runs and encounters an error (e.g., a Stop and Error node, or an API failure)
3. The platform detects the failure and automatically calls Agent B
4. Agent B's Error Trigger receives the error payload
5. Your workflow processes the error (send notification, log it, retry, etc.)

Error Payload

The Error Trigger receives this data structure:

Setting Up an Error Workflow

1. Create a new agent with an Error Trigger as the starting node
2. Add processing nodes (e.g., send a Slack message, log to a spreadsheet)
3. Publish and activate the error-handling agent
4. In your main agent's workflow JSON, set settings.errorWorkflow to the error handler's contract address
5. Publish and activate the main agent

Compatibility

Tips

• Error workflows run with their own budget — ensure the error handler agent is funded
• 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.