# How to Monitor Make Uptime

> Make (formerly Integromat) is a visual automation platform that connects apps and services into multi-step scenarios without code.

*Source: https://monitoristic.com/monitor/make*

---

## Why Monitor Make?

Make is fully hosted, so you can't monitor their servers — but your automations depend on two things you CAN monitor: the webhook endpoints that trigger your scenarios, and the apps those scenarios connect to. When a trigger webhook stops responding or a connected service goes down, your scenarios fail, and Make won't always alert you in time.

## What to Monitor

- `hook.make.com/your-webhook-id` — Your Make custom webhook trigger endpoint
- `your-app.com/api/health` — An app endpoint your scenarios depend on
- `status.make.com` — Make's platform status for service-level incidents

## What You Should Actually Do

1. Monitor your Make custom webhook trigger URLs — if a trigger stops responding, the scenario silently stops running
2. Monitor the apps and endpoints your scenarios depend on — a connected service going down breaks the scenario partway
3. Check Make's system status page during incidents, but rely on your own monitors for trigger and dependency issues
4. Build a heartbeat: have a simple scenario hit a monitored endpoint on a schedule, so you can detect when Make stops executing
5. Keep a direct alert channel (not routed through Make) so a Make outage doesn't suppress your downtime notifications

## Make's Official Status Page

Make publishes real-time status at https://www.make.com/en/help/tools/system-status. Your own monitor complements it by catching connection-level issues, often before the status page updates.

## Takeaway

Make is hosted, so you can't watch their servers — but you can watch the two things that actually break your automations: the webhooks that trigger your scenarios and the apps they connect to. Most Make failures aren't Make going down; they're a trigger that stopped firing or a dependency that went offline. Monitoring those endpoints catches the silent failures that 'no executions today' would otherwise hide.

## Frequently Asked Questions

### Can I monitor Make scenarios for uptime?

You can't monitor Make's servers directly, but you can monitor what actually breaks your scenarios: the webhook trigger endpoints and the apps your scenarios connect to. You can also build a heartbeat scenario that pings a monitored endpoint on a schedule to detect when Make stops executing.

### Why did my Make scenario stop running without errors?

If a scenario shows no recent executions and no errors, the trigger likely stopped firing — the webhook isn't receiving data, or the source app changed. Monitoring the trigger webhook endpoint catches this, since a silent trigger failure produces no error in Make itself.

### How do I detect when a Make-connected app goes down?

Set up monitors on the apps and endpoints your scenarios depend on. When a connected service goes down, your monitor alerts you and pinpoints the failing dependency — so you know why the scenario broke instead of debugging blind.

### How is this different from Make's status page?

Make's status page reports platform-wide incidents. It won't tell you that your specific trigger webhook stopped firing or that a connected app went down. Those scenario-specific failures only show up through monitoring the endpoints your scenarios actually use.