Is Make Down? How to Tell and What to Do

Is Make Down? How to Tell and What to Do

Make (formerly Integromat) is the automation backbone for thousands of businesses — connecting CRMs, support tools, eCommerce platforms, and internal databases through visual workflow scenarios. When Make goes down, those scenarios stop executing silently. Webhook triggers miss events, scheduled scenarios skip runs, and data that was supposed to flow between apps simply disappears into a gap.

Statusfield brings reported Make incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.

---

Common Signs of a Make Outage

---

How to Confirm It's Make, Not Your Scenario

1. Check your scenario run history

In the Make dashboard, look at the run history for your most active scenarios. If multiple unrelated scenarios all stopped executing at the same time, the issue is with Make's infrastructure — not a misconfiguration in your scenario logic.

2. Send a test webhook

If you have a webhook-triggered scenario, send a test event manually (using a tool like Postman or curl). If Make's webhook URL doesn't respond or shows a connection error, the ingestion layer is down.

3. Manually trigger a simple scenario

Pick a minimal test scenario with one or two modules and trigger it manually. If it fails immediately with a generic execution error, the core execution engine is degraded — not something specific to your complex workflows.

4. Check connection status for a core module

Open any module in your scenario editor and check its connection status. If connections that were working yesterday are now showing as invalid or timing out, it's likely Make's integration layer — not your OAuth tokens.

---

Use vendor reports as investigation context

Statusfield brings reported Make incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.

A reported incident can help you decide where to investigate and what to tell your team. An operational status does not prove that your account, region or complete workflow is working. Review the affected components and timestamps alongside your own logs and checks.

What to Do During a Make Outage

Immediate (first 5 minutes)

1. Identify the failure mode — check whether scheduled scenarios, webhook-triggered scenarios, or both are affected. Schedulers and webhook ingestion are separate systems.
2. Check your run history — note the exact time runs stopped. This is the timestamp you'll need to identify which data is in the gap.
3. Enable error handlers on critical scenarios — if you haven't already, add error-handler routes to your most important scenarios so that when Make recovers, you can see exactly which operations failed.
4. Identify fallback processes — for critical workflows (like order processing or lead routing), determine if there's a manual fallback you can run while Make is down.

Communication (first 15 minutes)

• Alert any teams that depend on Make-driven automations (sales ops, support ops, finance) so they can run manual processes if needed.
• If Make triggers customer-facing actions (order confirmations, onboarding emails, support ticket routing), notify the relevant customer-facing teams.
• Hold off on campaigns that rely on Make automations to execute follow-up sequences — queuing more events during an outage creates a larger backlog to reconcile.

Recovery

• After Make recovers, check for missed scheduled runs — Make may have skipped runs during the outage window rather than executing them retroactively.
• Replay any webhooks that were lost during the outage. For services that support webhook replay (Stripe, GitHub, etc.), use their dashboards to re-send events from the outage window.
• Audit your operations count to identify the gap in executions, and manually process any business-critical data that didn't flow through during the outage.
• Re-test your most critical scenarios end-to-end before trusting them fully — outages can occasionally leave integration connections in a broken state even after the platform recovers.

---

Make Components and What Each Outage Looks Like

A webhook ingestion failure is the most dangerous outage type for Make — events are silently dropped rather than queued, which means data loss rather than just delay. Execution engine failures are more visible (failed runs appear in history) but still require manual reconciliation.

---

Bring Make updates to your team

Follow reported Make status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.

Start your monitoring trial — view plans. Eligible first-time customers can start a free trial. Continued monitoring requires a paid plan.

---

FAQ

Is Make down right now?

This article is a troubleshooting guide, not a live outage verdict. Check the Statusfield catalog and the official vendor status page for the latest reported status, affected components and observation times. Compare those reports with what your own application is experiencing.

How can I get alerts about Make incidents?

Follow reported Make status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.

Does an operational Make status mean my application is working?

No. A vendor status page describes reported service conditions. Your account, integration, network or application can still fail. Check your own public HTTPS endpoint and use logs or workflow tests to investigate the customer experience.

Browse the service catalog and plans and alert destinations.