When you need this
Error Trigger helps when a workflow runs and fails. If n8n is offline or the schedule was never published, no execution reaches the handler. An external deadline also detects the absence of execution.
How to connect
- 1
Create a monitor matching the Schedule Trigger schedule and timezone. Allow enough grace time for normal workflow duration.
- 2
Add HTTP Request after the last successful operation. Import the curl example below, replace the URL and set timeout to 5000 ms. Publish the main workflow.
- 3
Create a separate workflow: Error Trigger → HTTP Request posting to the /fail URL. Assign it in the main workflow’s Settings → Error workflow.
Ready-to-use example
Uses Schedule Trigger, HTTP Request and Error Trigger. This example tracks completion and missed runs; per-run duration is not measured without /start. Continue on delivery errors only in the monitoring node; business-node failures must remain failures.
curl --fail --max-time 5 -X POST 'https://ping.tickwatch.dev/YOUR_PING_KEY'curl --fail --max-time 5 -X POST '{{PING}}/fail'Check before going live
Schedule Trigger uses the workflow timezone, falling back to the instance timezone. Saving a draft does not publish the schedule.
Test Error Trigger with a real automatic execution that fails. A manual editor execution does not trigger this handler.
If a business node returns zero items, the next node may not run. Test empty results and branches; configure Always Output Data on the appropriate node where needed.
Common questions
Why use Tickwatch alongside an error workflow?
An error workflow reports execution failures. Tickwatch additionally expects scheduled results and detects a missing run or an offline installation.
Does this work with n8n Cloud and self-hosted n8n?
Yes, provided HTTP Request can reach the ping URL over HTTPS. Keep the key in workflow settings and remove it from public exports.