Cronjob.de › Guides › n8n

Monitoring an n8n workflow: notice when it stops running

A workflow with a Schedule Trigger fetches orders every night, syncs contacts or sends a report. When it fails, someone often notices only when data is missing. An “HTTP Request” node at the end reports every successful run to Cronjob.de – if the check-in does not arrive, you get a message.

Why at all

Why you would not notice otherwise

n8n has error workflows: when an execution fails, a workflow with the Error Trigger starts and can notify you. That helps with failures inside a run.

It does not help when no run happens at all: the instance did not come back after an update, the server disk is full, the workflow was deactivated during a rework, or the schedule sits in the wrong time zone. Without an execution there is no error – and no message.

A heartbeat turns the logic around: we expect a check-in. If it does not come, that is exactly the message.

Ping address (example)
https://runcheck.de/a8k3m2x9q1
Schedule
as in the Schedule Trigger, such as hourly or daily
Applies to
n8n 1.x, Cloud und selbst betrieben
Sufficient Cronjob.de plan
One heartbeat is free; you see its status in your account. Email alerts come with Plus (€17.88 a year), Slack, Teams and Discord with Unlimited.

Setup

Set up in three steps

What is a heartbeat?

A regular sign of life: after every run your job calls its own address at Cronjob.de. If the call is overdue or the job reports a failure, we alert you. More about heartbeats

  1. Create a heartbeat

    In your account, create a new one under “Heartbeats”: the same rhythm as the Schedule Trigger, plus leeway for the workflow's run time. You receive a ping address of its own, such as https://runcheck.de/a8k3m2x9q1.

  2. Add an “HTTP Request” node at the end

    Add an “HTTP Request” after the last node: method GET, your ping address as URL, and under “Options” a timeout of 10000 milliseconds. In the node settings, set “On Error” to “Continue” – then the workflow never fails because of the check-in.

    Method:   GET
URL:      https://runcheck.de/a8k3m2x9q1
Options:  Timeout 10000
Settings: On Error → Continue

  3. Save and run once

    Save the workflow, keep it active and execute it once by hand. In your account, “Waiting for the first check-in …” turns green.

The ready-made lines for Linux, PHP, Python, Node.js, n8n, Make, Supabase and Vercel are on the page Cron job monitoring. Your own ping address appears in your account once you create the heartbeat, with the same lines ready to copy.

When something fails

What happens when a run fails

If the workflow does not start – instance down, workflow deactivated, schedule changed – or fails before the last node, the check-in is missing. After the leeway we alert you; the next check-in brings the all-clear. To hear about failures during a run right away, also call https://runcheck.de/a8k3m2x9q1/fail from your error workflow.

FAQ

Common questions about n8n

Does this work with n8n Cloud?
Yes. The node only calls an address; nothing else is needed, no firewall change on your server either.
Can I send along what the workflow did?
Yes, via POST: method POST instead of GET, with the number of processed records as the body, for example. Up to 10 KB then show up in the log.
What about Make or other automation tools?
Works the same way: an HTTP step at the end that calls the address via GET. In Make that is the HTTP › “Make a request” module, in Activepieces, Windmill or Node-RED the respective HTTP block.

Set up your heartbeat now

One heartbeat is free; you see its status in your account. Email alerts come with Plus (€17.88 a year), Slack, Teams and Discord with Unlimited. The first 14 days run on the Unlimited plan, no payment details needed.

Set up a heartbeat for free More about heartbeats

More monitoring guides

Official documentation of n8n

The details about n8n come from their own documentation, as of October 2026. Please check there whether anything has changed since. n8n is a trademark of its respective owner. This guide comes from Cronjob.de and has no business relationship with that provider.