Zapier guide

How to Get Alerted When a Zapier Zap Stops Running

Zapier history and error tools help investigate runs that happened. A heartbeat monitor adds an outside signal for the case where an expected completion never arrives.

Short answer

If you need to know when a Zap silently stops running, add a heartbeat URL to the final successful step. If the heartbeat does not arrive within the expected window, PulseProbe marks the workflow as missed and sends an alert.

Last reviewed: June 10, 2026PulseProbe is not an official Zapier integration or partner. It works with Zapier workflows that can send HTTP requests through supported webhook actions.

Why Zaps can appear to fail silently

A Zap can be turned off, delayed by trigger behavior, blocked by an app connection problem, or fail before the final business action finishes. Zapier's history is useful once you know where to look, but a client or operator may not notice a missing run immediately.

Heartbeat monitoring is built around the question: did the automation finish when we expected it to finish?

Zapier task errors are not the same as missed-run monitoring

Zapier run history helps troubleshoot Zap workflows that have run. A missed-run monitor watches for the lack of an expected completion signal.

Use both when the automation matters: Zapier's own tools for execution details, and PulseProbe for an external alert when the final check-in never arrives.

Step-by-step setup

1Create a PulseProbe probe named after the Zap or client workflow.
2Set the expected interval to how often the Zap should complete, with a grace window for normal delays.
3Copy the heartbeat URL when PulseProbe shows it after probe creation.
4Add a Webhooks by Zapier action after the critical Zap actions.
5Configure the webhook action to request the PulseProbe heartbeat URL. Use a simple GET or request style that fits the Zapier webhook action available in your account.
6Test the Zap and confirm the PulseProbe probe shows a recent check-in.

Common mistakes

Putting the heartbeat before the important app action, which can make a failed Zap look healthy.
Using one probe for several unrelated Zaps.
Setting a one-hour Zap to alert after exactly one hour with no grace time.
Assuming Zapier task history alone will alert you when an expected scheduled completion never happens.

How to test missed and recovered states

1Run the Zap once and verify a fresh check-in in PulseProbe.
2Temporarily turn off or pause the Zap only if it is safe to do so.
3Wait for the expected interval and grace period to pass.
4Confirm PulseProbe marks the probe as missed and sends the configured alert.
5Turn the Zap back on and confirm the next successful run records recovery.

When built-in Zapier errors are enough

Use Zapier tools when

Use heartbeat monitoring when

You need task-level run details.

You need an outside alert for a missing completion.

A Zap ran and produced a visible error.

A scheduled or expected Zap does not appear to finish.

You are debugging field mappings or app responses.

A client-facing business process must not go silent.

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

How do I know if my Zapier Zap stopped running?

For expected runs, place a heartbeat request at the final successful action and alert if the check-in does not arrive on schedule.

Does PulseProbe replace Zapier task history?

No. Zapier history is still where you inspect what happened inside Zapier. PulseProbe adds missed-check-in monitoring from outside the Zap.

Should I send Zap data to PulseProbe?

No. Use the heartbeat URL as a completion signal and avoid sending customer data, secrets, or private payloads.