Library / Monitoring, Ops & Incidents
Monitoring, Ops & Incidents
Collect Failed Execution Data for Workflow Errors
When another workflow fails, it extracts the webhook data and fetches the failed execution details from the n8n API.
What it does
# Errortrigger Workflow ## Overview Automated workflow: Errortrigger Workflow. This workflow processes data and performs automated tasks. ## Workflow Details - Total Nodes: 4 - Node Types: 4 - Error Handling: ✅ Implemented - Security: ✅ Hardened (no sensitive data) - Documentation: ✅ Complete ## Node Breakdown - Error Trigger: errorTrigger - Extract webhook data: code - Get execution data: n8n - Workflow Documentation: stickyNote ## Usage Instructions 1. Configure Credentials: Set up all required API keys and credentials 2. Update Variables: Replace any placeholder values with actual data 3. Test Workflow: Run in test mode to verify functionality 4. Deploy: Activate the workflow for production use ## Security Notes - All sensitive data has been removed or replaced with placeholders - Error handling is implemented for reliability - Follow security best practices when configuring credentials ## Troubleshooting - Check error logs if workflow fails - Verify all credentials are properly configured - Ensure all required services are accessible
The steps
- Error Trigger
- Extract webhook data
- Get execution data
- Error Handler
Similar automations
Monitoring, Ops & IncidentsSend grouped failed execution digests via Data Tables, email, and webhooks18 stepsMonitoring, Ops & IncidentsAccess Execution Data from an Error Workflow3 stepsMonitoring, Ops & IncidentsRetry Failed n8n Executions Every Hour9 stepsCode, Git & Developer ToolsRetry Failed n8n Executions Every Hour28 steps