How to Monitor Your Make.com Workflows (And Know When They Fail)

Make.com scenarios can break silently — and you won't find out until a customer complains. Here's how to add instant failure alerts to any Make.com scenario using TaskPulse.

The problem — silent failures in Make.com

Make.com (formerly Integromat) is one of the most powerful automation platforms available. But like all automation tools, it has a fundamental limitation: it doesn't alert you when a scheduled scenario silently stops running.

Make.com sends error notifications for failed runs — but only if the scenario actually executed and encountered an error. If your scenario stops being triggered entirely (because of a broken webhook, a scheduler issue, or a plan limit), you get nothing.

The result is a "silent failure" — a workflow that appears active in your dashboard but has stopped doing anything useful. By the time you notice, days of data may be missing or processes may be stalled.

How TaskPulse monitors Make.com

TaskPulse uses a Dead Man's Switch pattern. Your Make.com scenario sends a small HTTP ping to TaskPulse at the end of every successful run. TaskPulse expects that ping on a schedule. If it doesn't arrive, you get an alert.

Two monitor types are available:

• Heartbeat monitor — for scheduled scenarios. Ping at the end of each run. Get alerted if the ping is missed.
• Signal monitor — for event tracking. Post a signal for each record processed, order created, or email sent. Track throughput over time.

Step-by-step: Setting up monitoring for Make.com

Step 1: Create a free TaskPulse account

Go to taskpulse.co/register and sign up. The Free plan includes 5 Heartbeat monitors — no credit card required.

Step 2: Create a Heartbeat monitor

In your TaskPulse dashboard, click New Monitor and choose Heartbeat. Name it after your Make scenario (e.g., "Make: order sync") and set the interval to match how often the scenario runs. Copy the monitor UUID.

Step 3: Add an HTTP module at the END of your Make.com scenario

In your Make.com scenario, add an HTTP > Make a request module as the last module. Configure it as follows:

URL: https://api.taskpulse.co/ping/YOUR-MONITOR-UUID
Method: POST

To send metadata with your ping (Smart Heartbeat — always free):

URL: https://api.taskpulse.co/ping/YOUR-MONITOR-UUID
Method: POST
Body type: Raw
Content type: application/json
Request content:
{
  "items_processed": {{length(1.items)}},
  "scenario": "{{scenario.name}}"
}

Step 4: Set expected interval + tolerance

Back in TaskPulse, set the interval to match your scenario's schedule and add a tolerance window to avoid false alarms from minor delays.

Step 5: Configure alerts

Set up your notification channels. Email is available on all plans. Slack and Discord are included on Pro ($9/mo). Custom Webhooks are available on Business ($29/mo).

Tracking business events with Signal monitors

Signal monitors let you track business throughput from your Make.com scenarios. For each business event — an order processed, a lead created, a report generated — send a signal event:

URL: https://api.taskpulse.co/signal/YOUR-MONITOR-UUID
Method: POST
Body type: Raw
Content type: application/json
Request content:
{
  "status": "success",
  "scenario": "{{scenario.name}}",
  "items_processed": {{length(1.items)}}
}

What happens when a Make.com scenario fails

1. Your Make.com scenario stops running (scheduler issue, API error, plan limit, etc.)
2. No ping arrives at TaskPulse within the expected interval + tolerance
3. Monitor status changes from healthy to failed
4. Alert sent via email, Telegram, Slack, or Discord
5. You investigate, fix the issue — next successful ping resets the monitor to healthy

Pricing

See the full pricing page for details.

• Free: 5 Heartbeat + 5 Signal monitors, 100 events/mo, email alerts
• Pro ($9/mo): 50 monitors, 50k events, Slack + Discord, 1-min intervals
• Business ($29/mo): 200 monitors, 1M events, Custom Webhooks, 10-sec intervals

Frequently asked questions