Resources · Make integration

Statuspage Make integrationAutomate Statuspage with Make.

Every Statuspage incident update can move on to your other tools without anyone copying it. The Statuspage Make integration gives you 3 modules: one trigger, one search and one open API call. This guide is for ops and support teams, from the API key to a first scenario that runs.

Try the Statuspage integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Statuspage Make integration do for you?

The Statuspage Make integration links your Statuspage account to Make, a visual tool where you chain apps into a scenario (the automation you build, one brick at a time). Make spots new incident updates, lists them, and hands them to any other app you add after it, with no code to write.

A support team that hears about incidents first. Put Watch Incident Updates at the start of a scenario and each new update becomes a bundle, one item passed to the next module. Map its text into the chat or ticketing app your agents already watch, and they answer customers with the same wording as your status page.

A clean incident log. List Incident Updates returns the updates of your account as several bundles in one run. Send them to a spreadsheet or a database module and you keep a written trail for your post-mortems. If you need a table first, the Airtable Make integration page shows that side.

Anything the listed modules leave out. Make an API Call reaches any endpoint of the Statuspage API with the connection you already set up, so you are not stuck with the two ready-made modules.

Know the limits before you start: Make offers no ready-made module here to create or edit an incident, and the Statuspage documentation gives no figures on quotas. The same app often has an n8n node too; the n8n vs Make comparison helps you pick, and the Make review covers the editor itself.

Connect

How do you connect Statuspage to Make?

  1. 01

    Copy your API key

    Log in to Statuspage, click your Profile Icon, then open API Info. Copy the API Key shown there and paste it somewhere safe, because Make will ask for it in a moment.

  2. 02

    Add a Statuspage module in Make

    In your Make account, place any Statuspage module in a scenario and click Add next to the Connection field. A connection is your Statuspage account linked to Make once, then reused by every Statuspage module.

  3. 03

    Paste the key and save

    Give it a label in Connection name if you like, which helps when you manage several pages. Paste the key into the API Key field and click Save. Make can now read your incident updates.

First scenario

Your first scenario with Statuspage

GoalWhen an incident is updated in Statuspage, Make picks it up and pulls the list of incident updates so the full thread is ready for your next module.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. This first brick decides when everything starts.

  2. 02

    Pick the trigger

    Search for Statuspage, choose Watch Incident Updates and select the connection you made earlier, or click Add to create it now with your API Key.

  3. 03

    Add the search

    Click the + on the right of the trigger, pick List Incident Updates and reuse the same connection. Fill its fields and map data from the trigger where Make offers it.

  4. 04

    Test with Run once

    Update an incident on your status page, then click Run once. Read the bundles each module received and check that the right incident came through.

  5. 05

    Set the schedule and switch it on

    Open the clock on the first module: a new scenario checks every 15 minutes by default. Keep that or pick another interval your plan allows, then switch the scenario on.

Triggers

The trigger that starts a Statuspage scenario

1 module starts a scenario when something happens in Statuspage. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Statuspage as soon as it happens.

Statuspage1Watch Incident Updates

Watch Incident Updates

Scheduled trigger

In Make“Triggers when an incident is updated.”

Watch Incident Updates hands your scenario every new update posted on a Statuspage incident, so the next modules can pass it on without anyone rewriting it. Each update arrives as its own bundle, with its text ready to map.

How it fires
it is a scheduled trigger, so Make checks Statuspage on the scenario's schedule (the clock badge on the module) and picks up the new updates at each check.
When to use it
when your support desk should get the status message at the next check, instead of refreshing the public page during an outage.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, while paid plans go down to 1 minute.
Modules

What the other Statuspage modules do

Statuspage gives you 2 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Incidents

1 module
Statuspage1

List Incident Updates

Search

In Make“Lists all incident updates.”

List Incident Updates gives you the incident updates of your account in one pass, each one as a separate bundle, which is handy to build a history or a report.

When to use it
after an outage, when you want the whole thread written down in a sheet for the post-mortem.
Watch out
a search can return zero, one or many bundles, and every bundle the next module processes counts as an operation on your plan.

Other

1 module
Statuspage2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the Statuspage API from your scenario, reusing the connection you already created with your API Key.

When to use it
when the task you have in mind goes beyond reading incident updates, since those are the only ready-made modules.
Watch out
you describe the request yourself, so test it with Run once and read the returned bundle before switching the scenario on.
Need help

Need help automating Statuspage with Make?

A person reads every message.

FAQ

Questions about the Statuspage Make integration

01Is the Statuspage Make integration free?
Yes, Statuspage is a standard app in Make, so it works on the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits per month. Your Statuspage subscription is a separate matter that this page does not cover.
02What do you need to connect Statuspage to Make?
You need a Statuspage account, a Make account and the API Key found under Profile Icon then API Info in Statuspage. The documentation lists no other prerequisite. In Make, you add a Statuspage module, click Add next to the Connection field, optionally type a Connection name, paste the key into the API Key field and click Save. That single connection then serves the trigger, the search and the API call module, so you only go through these steps once per account.
03Does the Statuspage trigger in Make react instantly?
No. Watch Incident Updates is a scheduled trigger, marked with a clock badge in the editor. Make asks Statuspage for new updates each time the scenario's schedule comes around, every 15 minutes by default on a new scenario. The Free plan cannot go below 15 minutes between two checks, and paid plans can go as low as 1 minute. So a paid plan with a tighter schedule is the only way to shorten the wait between an update and your scenario.
04What if the Statuspage module you need is missing in Make?
Use Make an API Call. The app only ships a trigger for incident updates and a search that lists them, so creating or editing an incident has no ready-made module. With Make an API Call, you can reach any endpoint of the Statuspage API from the same scenario, reusing the connection built on your API Key. The Statuspage documentation for Make gives no figures on limits, so test each request with Run once before you let the scenario run on its own.
05Should you use Make or n8n for Statuspage?
It depends on where the rest of your automations live. Make gives Statuspage 3 modules, a scheduled trigger for incident updates, a search and an API call, all built in a visual editor with a first scenario you can test with Run once. The same app often has an n8n node as well, so check what that tool offers for Statuspage before you decide. The honest criteria are the modules you actually need and the tool your team already uses every day.
Same platform

Other docs you might need on this stack.

Browse all integrations