PulseProbe

Automation monitoring guides

Webhook guide

Webhook Heartbeat Monitoring for Automations

Most automation tools can call a URL. That makes HTTP heartbeats a portable way to monitor completion without a platform-specific app.

Short answer

Webhook heartbeat monitoring uses an HTTP request as a completion signal. When the request stops arriving on the expected schedule, PulseProbe alerts you.

Last reviewed: June 10, 2026

How webhook heartbeats work

PulseProbe gives a probe a unique heartbeat URL. Your automation calls that URL after it completes successfully. PulseProbe records the timestamp and compares it with the expected interval.

GET vs POST

For heartbeat monitoring, the simplest request is usually best. A GET request can be enough when the tool supports it. POST is useful when the tool expects an action step, but PulseProbe does not need private workflow data to decide whether a check-in arrived.

Privacy and security cautions

  • Treat heartbeat URLs like bearer secrets.
  • Do not paste heartbeat URLs into public docs, screenshots, issue trackers, or chat rooms.
  • Do not send API keys, prompts, customer records, or private workflow payloads as metadata.
  • Rotate the heartbeat URL if it is exposed.

Step-by-step setup

  1. 1Create a PulseProbe probe.
  2. 2Copy the heartbeat URL.
  3. 3Add an HTTP request or webhook action at the final successful step.
  4. 4Send one test request.
  5. 5Confirm the check-in appears in PulseProbe.
  6. 6Test a missed state by stopping the automation in a safe window.

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

Is a webhook heartbeat a platform-specific app?

No. It is a standard HTTP request pattern that works in tools capable of calling external URLs.

Can someone fake a heartbeat?

Anyone with the heartbeat URL can send a check-in, so treat the URL as a secret and rotate it if exposed.

Should I include workflow output in the request?

No. The safest setup is to send only the check-in and keep sensitive data inside your automation platform.