# How to Connect Monitoristic to n8n, Make, and Zapier

> Route downtime alerts into your automation workflows. Learn how to connect Monitoristic webhooks to n8n, Make, and Zapier to trigger tickets, escalations, and automated responses when your site goes down.

*Source: https://monitoristic.com/blog/how-to-connect-monitoristic-to-n8n-make-zapier*

---

Monitoristic tells you the moment your site goes down — via [Telegram](/docs/telegram) or [webhooks](/docs/webhooks). But what if you want more than a notification? What if you want your downtime alert to *do something* — create a ticket, escalate to your on-call engineer, log the incident, or trigger an automated recovery?

That's where automation platforms come in. n8n, Make, and Zapier all accept incoming webhooks, which means you can pipe Monitoristic alerts into any workflow you can imagine.

This guide shows you how to connect Monitoristic to all three.

## How It Works

The mechanism is the same for every platform:

1. The automation tool gives you a **webhook URL** — a unique address that listens for incoming data.
2. You paste that URL into Monitoristic's webhook settings.
3. When a monitor goes down (or recovers), Monitoristic sends a JSON payload to that URL.
4. Your workflow receives the data and runs whatever steps you've built.

No code required on your end. You build the logic visually in the automation tool.

## The Monitoristic Webhook Payload

Before connecting anything, it helps to know what data you'll receive. When a monitor goes down or recovers, Monitoristic sends this JSON:

```json
{
  "event": "monitor.down",
  "monitor": {
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "name": "My Website",
    "url": "https://example.com"
  },
  "incident": {
    "id": "f9e8d7c6-b5a4-3210-fedc-ba9876543210",
    "title": "My Website is down"
  },
  "check": {
    "status_code": 500,
    "response_time": 1234,
    "error": null
  },
  "timestamp": "2026-05-02T12:00:00.000Z"
}
```

The `event` field is either `monitor.down` or `monitor.recovered`. You'll use these fields to build conditional logic — for example, "if event is monitor.down, create a ticket; if monitor.recovered, close it."

There's also a separate payload for [maintenance events](/docs/webhooks) (`maintenance.started`, `maintenance.completed`, etc.) if you want to automate around planned downtime.

## Connecting to n8n

[n8n](/monitor/n8n) is a powerful, often self-hosted automation tool that developers love for its flexibility.

**Steps:**

1. In n8n, create a new workflow and add a **Webhook** node as the trigger.
2. Set the HTTP method to **POST** and copy the **Production URL** n8n generates.
3. In Monitoristic, go to your notification settings, add a **Webhook** channel, and paste the n8n URL.
4. Back in n8n, add the nodes you want to run — an **IF** node to branch on `{{$json.event}}`, then actions like creating a ticket or posting to Slack.
5. Activate the workflow.

**Example n8n workflow:**

```
Webhook (trigger)
  → IF event == "monitor.down"
      → Jira: Create Issue (title from incident.title)
      → Slack: Post to #incidents
  → IF event == "monitor.recovered"
      → Jira: Transition Issue to Done
      → Slack: Post "Resolved" message
```

Because n8n is code-friendly, you can also drop in a **Function** node to transform the payload, enrich it with data from other APIs, or build complex routing logic.

## Connecting to Make

[Make](/monitor/make) (formerly Integromat) uses a visual scenario builder that's great for connecting many apps together.

**Steps:**

1. In Make, create a new scenario and add a **Webhooks → Custom webhook** module as the trigger.
2. Click **Add**, name the webhook, and copy the generated URL.
3. In Monitoristic, add a **Webhook** notification channel and paste the Make URL.
4. Trigger a test from Monitoristic (or wait for a real event) so Make can detect the data structure.
5. Add modules after the webhook — a **Router** to branch on the event type, then actions like creating records or sending messages.

**Example Make scenario:**

```
Custom webhook (trigger)
  → Router
      → Route 1 (event = monitor.down): Trello → Create Card + Email → Send
      → Route 2 (event = monitor.recovered): Trello → Archive Card
```

Make's strength is the breadth of app integrations — if you use a tool, Make probably connects to it.

## Connecting to Zapier

[Zapier](/monitor/zapier) is the most beginner-friendly of the three, with the largest catalog of app integrations.

**Steps:**

1. In Zapier, create a new Zap and choose **Webhooks by Zapier** as the trigger.
2. Select **Catch Hook** as the event and copy the custom webhook URL.
3. In Monitoristic, add a **Webhook** notification channel and paste the Zapier URL.
4. Send a test event so Zapier can parse the fields.
5. Add action steps — use a **Filter** to run only on `monitor.down`, then connect actions like Slack, Google Sheets, or PagerDuty.

**Example Zap:**

```
Catch Hook (trigger)
  → Filter: only continue if event = monitor.down
  → PagerDuty: Create Incident
  → Google Sheets: Add Row (log the downtime)
```

Zapier's filters and paths make it easy to build conditional logic without any technical setup.

## Real Workflow Ideas

Once your alerts flow into an automation tool, here's what you can build:

**Incident ticketing**
Downtime automatically creates a ticket in Jira, Linear, or Trello with the monitor name, URL, and status code pre-filled. Recovery closes it. Your incident log builds itself.

**Smart escalation**
Post to Slack immediately. If the monitor is still down after 10 minutes (use a delay step), escalate by sending an SMS or calling your on-call engineer via PagerDuty.

**Incident logging**
Every downtime and recovery event gets logged to a Google Sheet or database with timestamps. Over time, you build a complete incident history you can analyze for patterns — exactly the kind of data covered in [how to read an uptime report](/blog/how-to-read-an-uptime-report).

**Automated response**
For some failures, you can trigger a fix. A webhook can call your hosting provider's API to restart a service, clear a cache, or scale up resources — turning detection into automatic remediation.

**Multi-channel broadcast**
Fan out a single downtime alert to Slack, email, a status page update, and a team SMS — all from one Monitoristic webhook.

## A Note on Reliability

One important detail: if you're routing critical alerts through an automation platform, remember that platform is now part of your alert chain. If [n8n](/monitor/n8n), [Make](/monitor/make), or [Zapier](/monitor/zapier) has an outage, your automated alerts could be delayed or dropped.

For mission-critical alerts (like a checkout outage), it's wise to keep a **direct** notification channel too — a [Telegram alert](/docs/telegram) straight from Monitoristic that doesn't depend on any third party. Use the automation platform for the rich workflow (tickets, logging, escalation) and keep a direct channel as your reliable backstop.

This is also why it's worth [monitoring your automation tool itself](/monitor/n8n) — especially if you self-host n8n.

## Get Started

1. Pick your automation platform (n8n, Make, or Zapier)
2. Create a workflow with a webhook trigger and copy the URL
3. In Monitoristic, add a [webhook notification channel](/docs/webhooks) and paste the URL
4. Build your workflow steps
5. Test it, then let it run

From there, every downtime event becomes the start of an automated workflow — not just a notification you have to act on manually.

[Start monitoring with Monitoristic →](https://app.monitoristic.com/register)

For the full webhook reference, see the [webhook integration docs](/docs/webhooks).