Monitor n8n Cron Workflows with QuietPulse Heartbeat Alerts

n8n cron workflows are useful for scheduled automation, but a healthy n8n instance does not prove that a specific workflow completed its work.

If a Schedule Trigger node does not fire, a workflow is not published, a timezone is wrong, or an HTTP step fails halfway through the workflow, the rest of your system can stay quiet. QuietPulse gives each scheduled workflow a heartbeat URL, and n8n calls that URL only after the workflow reaches its success point.

This guide shows how to monitor n8n Schedule Trigger workflows with QuietPulse, where to place the HTTP Request node, how to think about cron expressions, and how to route missed-workflow alerts through email, Telegram, or webhooks.

Why combine n8n and QuietPulse?

n8n is a workflow automation tool. QuietPulse monitors expected heartbeats from scheduled work. Together they create:

• Automated completion monitoring - no separate shell script required
• Workflow-level visibility - monitor the scheduled workflow, not just the n8n server
• Integration routing - send alerts into email, Telegram, Slack, Discord, incident tools, or another n8n workflow
• A clear success signal - QuietPulse expects a ping only after the meaningful work succeeds

How it works

1. QuietPulse provides a unique heartbeat URL for the workflow.
2. n8n runs the workflow from a Schedule Trigger node.
3. Your workflow does the real scheduled work: sync data, generate a report, call an API, run a cleanup, or update a database.
4. An HTTP Request node calls the QuietPulse URL after the important work succeeds.
5. If that ping does not arrive on time, QuietPulse sends an alert through email, Telegram, or webhooks.

That last detail matters. The heartbeat should represent successful completion, not just workflow start.

Step 1: Create a heartbeat endpoint in QuietPulse

1. Log in to the QuietPulse dashboard.
2. Create a monitor for the n8n workflow.
3. Set the expected interval to match the workflow schedule.
4. Add a grace period for normal execution delay.
5. Enable email alerts, Telegram alerts, webhooks, or the combination that fits your workflow.
6. Copy the monitor ping URL.

You now have a unique endpoint like:

https://quietpulse.xyz/ping/abc123def456...

Step 2: Add the ping to the n8n workflow

In your n8n workflow:

1. Drag an HTTP Request node near the end of the successful path.
2. Configure:
   • Method: GET
   • URL: paste the QuietPulse ping URL
   • Authentication: None
3. Connect this node after the business-critical steps, not directly after the trigger.

For example:

Schedule Trigger -> Fetch records -> Update CRM -> Send report -> HTTP Request to QuietPulse

If Fetch records, Update CRM, or Send report fails, the QuietPulse HTTP Request should not run. QuietPulse will then alert when the expected heartbeat is late.

Step 3: Schedule the workflow

Use n8n's Schedule Trigger node to run at your desired schedule. In older tutorials this is sometimes called a cron node, but current n8n documentation names it Schedule Trigger.

Common schedules can be configured with minutes, hours, days, weeks, or months. For custom cron expressions, choose the custom cron interval.

*/5 * * * *    # Every 5 minutes
0 2 * * *      # Daily at 02:00
*/15 * * * *   # Every 15 minutes

n8n can also use a six-field cron expression where the first field represents seconds:

0 */5 * * * *  # Every 5 minutes, with seconds explicitly set to 0

Before relying on the schedule, check three things:

• The workflow is saved and published.
• The workflow timezone or instance timezone matches your expectation.
• The QuietPulse interval and grace period are slightly wider than normal n8n execution delay.

For timing and grace-period patterns, read the Cron Job Monitoring Guide.

Step 4: Handle missed workflow alerts

QuietPulse can notify humans directly, or trigger another workflow when a heartbeat is missed.

Option 1: Webhooks

The cleanest automation path is a QuietPulse webhook:

1. In n8n, create a workflow with a Webhook trigger.
2. In QuietPulse, configure that webhook URL as a notification channel.
3. When the monitored n8n workflow is missed, QuietPulse sends a signed JSON payload to the webhook.
4. The alert workflow can create a ticket, send a Slack message, call PagerDuty, or run any other recovery path.

Option 2: Telegram to n8n

If you prefer the Telegram path:

1. Connect the QuietPulse Telegram bot to a Telegram group.
2. In n8n, add a Telegram Trigger node listening to that group.
3. When QuietPulse sends an alert, n8n catches it and runs the alert workflow.

For most production setups, direct webhooks are easier to reason about. Telegram is useful when a human-readable chat alert is the primary workflow.

Complete example: Backup monitoring

Workflow structure

With webhooks:

Schedule Trigger (0 2 * * *) -> Run backup -> Verify backup -> HTTP Request to QuietPulse

If the heartbeat is missed:

QuietPulse -> Webhook -> n8n Webhook Trigger -> Slack / ticket / recovery action

With Telegram:

Schedule Trigger (0 2 * * *) -> Run backup -> Verify backup -> HTTP Request to QuietPulse

If the heartbeat is missed:

QuietPulse -> Telegram group -> n8n Telegram Trigger -> Action

What happens

• 02:00: n8n starts the scheduled workflow.
• 02:00-02:05: the backup runs and verifies its output.
• 02:05: the final HTTP Request node pings QuietPulse.
• Later: if the next expected ping does not arrive, QuietPulse sends an alert.

This catches failures where n8n is online but the scheduled workflow did not complete.

Best practices

Do

• Use separate endpoints for different workflows.
• Put the QuietPulse HTTP Request at the end of the successful path.
• Publish the n8n workflow before expecting scheduled runs.
• Check timezone settings when local business time matters.
• Use direct QuietPulse webhooks for machine-to-machine alert routing.
• Keep email or Telegram enabled for owner-visible missed workflow alerts.

Do not

• Share your ping URL publicly because it contains a secret token.
• Use the same endpoint for multiple unrelated jobs.
• Ping QuietPulse at workflow start if later steps can still fail.
• Set intervals too tight for normal n8n execution delay.
• Assume n8n being online means every scheduled workflow completed.

Troubleshooting

Supported n8n patterns

FAQ

What is the n8n cron node called now?

In current n8n documentation, scheduled workflow runs are handled by the Schedule Trigger node. Older articles may call this a cron node or Cron Trigger, but the current node name is Schedule Trigger.

How do I monitor an n8n Schedule Trigger workflow?

Create a QuietPulse monitor, copy its ping URL, and add an n8n HTTP Request node at the end of the successful workflow path. If the scheduled workflow does not complete and send the heartbeat on time, QuietPulse alerts you.

Should the QuietPulse ping run at the start or end of the n8n workflow?

Place the ping at the end, after the important work succeeds. A start ping can hide later failures, partial updates, failed API calls, or reports that never finish.

Why does n8n use six fields in some cron expressions?

n8n's custom cron interval can include a seconds field before the usual minute, hour, day, month, and weekday fields. A five-field cron expression still works for normal schedules, but an explicit six-field expression lets you control seconds.

Why did my n8n scheduled workflow run at the wrong time?

Check the workflow timezone first, then the n8n instance timezone. If the workflow timezone is not set, n8n falls back to the instance timezone.

Are n8n execution logs enough for monitoring scheduled workflows?

Logs help explain a failed execution after you know something went wrong. They do not reliably alert you when a workflow never started, was unpublished, or did not reach its success point. A completion heartbeat makes that missing success visible.

Next steps

• Ensure email alerts, Telegram alerts, webhooks, or a combination are configured in each QuietPulse monitor.
• Add grace periods to avoid deployment false positives.
• Prefer an n8n Webhook trigger for direct QuietPulse alert integration.
• Monitor job status directly in the QuietPulse dashboard.
• Read the Cron Job Monitoring Guide for heartbeat timing and grace-period patterns.
• Compare QuietPulse vs Healthchecks.io if you are choosing a heartbeat monitoring tool.
• Create a free QuietPulse monitor when you are ready to test this with a real n8n workflow.