PulseProbe

Automation monitoring guides

Setup guide

How to Monitor an n8n Workflow with PulseProbe

This setup guide focuses on placing a final HTTP Request heartbeat in an n8n workflow.

Short answer

Create a probe, add an HTTP Request node near the end of the workflow, and confirm PulseProbe receives a heartbeat after successful completion.

Last reviewed: June 10, 2026PulseProbe is not an official n8n integration or partner. It uses a standard outbound HTTP request from n8n.

What you need

  • A PulseProbe account with permission to create a probe.
  • Access to edit and test the n8n workflow.
  • A realistic workflow schedule or expected cadence.
  • Email alerts configured in PulseProbe.

Step-by-step setup

  1. 1Create a PulseProbe probe for the workflow.
  2. 2Copy the heartbeat URL.
  3. 3Add an HTTP Request node near the end of the success path.
  4. 4Use the heartbeat URL as the request URL. A simple GET request is enough for PulseProbe.
  5. 5Run the workflow manually and confirm a recent check-in.
  6. 6Set the expected interval and grace window around the workflow schedule.

Common mistakes

  • Putting the HTTP Request node too early.
  • Forgetting to save and publish scheduled workflows.
  • Using one probe across workflows with different schedules.
  • Using workflow heartbeat monitoring as a replacement for host monitoring.

How to test missed and recovered states

  1. 1Run one successful workflow execution.
  2. 2Confirm PulseProbe records the check-in.
  3. 3Safely disable or pause the workflow.
  4. 4Wait for the missed alert.
  5. 5Re-enable the workflow and confirm recovery.

When not to use PulseProbe

  • Do not use heartbeat monitoring as the only control for safety-critical, medical, emergency, financial trading, or regulated systems.
  • Do not send secrets, customer records, prompt text, API keys, or private payloads to the heartbeat URL.
  • Heartbeat monitoring proves a check-in arrived. It does not inspect the quality of the workflow output.

FAQ

Can n8n call a heartbeat URL?

Yes. The HTTP Request node can make outbound HTTP requests, which fits the heartbeat pattern.

Is this the same as an n8n Error Workflow?

No. Error Workflows handle execution failures; heartbeats monitor expected final check-ins.

Does PulseProbe monitor my n8n host?

No. It monitors workflow completion. Monitor the host separately if you self-host.