PulseProbe

Heartbeat monitoring for automation builders.

Heartbeat monitoring for critical automations

Your automations should not fail silently.

PulseProbe monitors Make, n8n, Zapier, and AI workflows. Add a heartbeat URL to any automation and get alerted when it misses a check-in.

Start monitoring freeSee setup examples

Missed leads. Broken reports. Failed syncs. Silent AI agents. PulseProbe watches for automations that were supposed to run but didn't.

Monitoring strip

Workflow / heartbeat / incident flow

Active probe
1

Workflow run

Complete

2

Pulse received

On time

3

Expected window

08:45-09:00

4

Missed pulse

Detected

5

Alert sent / Recovery pending

Open

Heartbeat URL

One-time URL generated for this probe

Drop the heartbeat URL into the final successful step of the workflow so each run confirms it finished on time.

Missed pulse incident

Nightly sync missed its expected pulse.

Incident opened after the workflow stopped checking in for one full cycle. The recovery state closes when the next pulse arrives.

Recent pulses

Expected every 15 min

Pulse received

08:31

Zapier lead routing closed successfully.

Pulse received

08:46

Make client report completed and checked in.

Missed pulse

09:02

Nightly sync exceeded the expected window.

How it works

Three steps from workflow to pulse monitoring.

Step 1Define

Create a probe

Choose how often your automation should check in.

Step 2Connect

Add the heartbeat URL

Paste the PulseProbe URL into Make, n8n, Zapier, cron, or any workflow that can make an HTTP request.

Step 3Detect

Get alerted when it stops

If the automation misses its expected check-in, PulseProbe marks it unhealthy and alerts you.

Setup examples

Add a final check-in to the tools you already use.

PulseProbe works with automations that can make an HTTP request. These examples show where to place the final heartbeat check-in in common workflow tools.

n8n workflow monitoring

View guide

Add an HTTP Request node near the end of a workflow so successful runs check in.

Make.com scenario monitoring

View guide

Place an HTTP module after the important scenario steps and monitor its schedule.

Zapier Zap monitoring

View guide

Use Webhooks by Zapier after the critical actions to confirm the Zap completed.

AI agent heartbeat monitoring

View guide

Have a scheduled agent check in only after its expected work finishes successfully.

Google Apps Script monitoring

Guide coming soon

Call the heartbeat URL after a scheduled script completes its important work.

Cron/cURL monitoring

View guide

Send a simple HTTP request at the end of a cron job or scheduled shell command.

Problem

Automation failures often look healthy right up until they do not.

PulseProbe watches the last successful pulse so automation builders and small agencies can catch workflow silence before clients, reports, or downstream jobs start failing.

1

A workflow can finish cleanly and still miss its next check-in.

2

A silent failure often looks healthy until the pulse window expires.

3

Recovery gets harder the longer the workflow goes quiet.

Use cases

Built for the workflows automation builders cannot afford to lose track of.

PulseProbe fits the places where a missed pulse matters: client routing, nightly syncs, operational reports, and automation pipelines with real business consequences.

Lead routingWatch
Client reportingWatch
AI agentsWatch
Nightly syncsWatch
Webhook pipelinesWatch

Plans

Simple plans for early workflow monitoring.

Plan

Free

For users validating workflow monitoring before rolling it out more broadly.

Early access

Plan

Starter

For growing workspaces that need dependable pulse tracking and straightforward recovery signals.

Early access