PulseProbe

Automation monitoring guides

Setup guide

How to Monitor a Make.com Scenario with PulseProbe

This setup guide focuses on placing a final heartbeat check in a Make.com scenario.

Short answer

Create a probe, add an HTTP request near the end of the Make scenario, and confirm PulseProbe receives a heartbeat after successful completion.

Last reviewed: June 10, 2026PulseProbe is not an official Make.com integration or partner. It receives a standard outbound HTTP check-in.

What you need

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

Step-by-step setup

  1. 1Create a PulseProbe probe for the scenario.
  2. 2Copy the heartbeat URL.
  3. 3Add an HTTP module or request step near the final successful path.
  4. 4Call the heartbeat URL only after important modules complete.
  5. 5Run the scenario once and confirm PulseProbe records a check-in.
  6. 6Set the expected interval and grace window around the scenario schedule.

Common mistakes

  • Putting the heartbeat before modules that can still fail.
  • Ignoring retries or incomplete executions when choosing a grace window.
  • Using one probe for unrelated scenarios.
  • Sending sensitive scenario data with the heartbeat.

How to test missed and recovered states

  1. 1Run one successful scenario execution.
  2. 2Confirm PulseProbe records the check-in.
  3. 3Safely disable or stop the scenario.
  4. 4Wait for the missed alert.
  5. 5Re-enable the scenario 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 Make scenarios call a heartbeat URL?

Yes, when the scenario can make an outbound HTTP request on its successful path.

Does this replace Make error handling?

No. Use Make error handling for module errors and PulseProbe for missed expected check-ins.

Where should the heartbeat go?

Near the end of the successful scenario path, after the work that matters.