Resources · Make integration

ilert Make integrationAutomate ilert with Make.

Can Make take routine incident work off your on-call team? The ilert Make integration gives you 10 modules, including 2 triggers and 7 actions. This guide shows what each one does, how to link your API key, and how to build a first scenario step by step.

Try the ilert integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ilert Make integration do for your team?

The ilert Make integration links your ilert account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick, such as a trigger that watches incidents or an action that accepts, assigns or resolves one.

Route every new incident to the right person. Watch New Incidents picks up the incident, Get a User On-Call asks a schedule who is on duty, and Assign an Accident hands the incident to that user. Nobody has to open ilert to dispatch it.

Turn an outside signal into an incident. A form, a monitoring tool or a spreadsheet row can feed Create an Incident, which posts an alert event to ilert and opens a new incident.

Close the loop once the fix ships. When your ticketing tool marks a problem as done, Resolve an Incident closes the matching ilert incident, and List Incidents helps you find it first.

What the integration does not do: it only covers the 10 modules listed below. Anything else in the ilert API goes through Make an API Call. The same app often has an n8n node too, and our n8n vs Make comparison lays out the differences. New to the tool? The Make training starts from zero, and the Make pricing page explains plans and operations.

Connect

How do you connect ilert to Make?

  1. 01

    Create an API key in ilert

    In ilert, open Profile, then API Keys, and click the button that creates a new key. Copy the key shown on screen right away; you need an active ilert account for this step.

  2. 02

    Add an ilert module in Make

    In your scenario, add any ilert module and click Create a connection. A connection is your ilert account linked to Make once, then reused by every ilert module. You can type a label in Connection name if you like.

  3. 03

    Paste the key and save

    Paste the API key you copied from ilert, or follow the instructions Make shows on screen, then save. Make now lists what it can read from your account when you fill the module fields.

First scenario

Your first scenario with ilert

GoalWhen a new incident appears in ilert, Make finds who is on call and assigns the incident to that person.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. Search for ilert and pick Watch New Incidents.

  2. 02

    Link your account

    Click Create a connection and paste the ilert API key. Once the connection exists, Make can read your incidents and fill the lists in each field.

  3. 03

    Ask who is on call

    Click the + on the right of the trigger and add Get a User On-Call. Pick the schedule your team uses; the module returns the person on duty for it.

  4. 04

    Assign the incident

    Add Assign an Accident, map the incident from the trigger and the user returned by the previous module. Each bundle, one item passed between modules, carries that data.

  5. 05

    Test with Run once

    Click Run once and create a test incident in ilert. Open the bubbles above each module to read the bundles it received and check the assignment.

  6. 06

    Schedule and switch on

    Open the clock on the first module; a new scenario runs every 15 minutes by default, and the Free plan does not go below that. Then switch the scenario on.

Triggers

What starts an ilert scenario

2 modules start a scenario when something happens in ilert. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by ilert as soon as it happens.

ilert1Watch Connection Incidents

Watch Connection Incidents

Instant trigger

In Make“Triggers depending on the connection settings you added.”

This trigger starts your scenario as soon as ilert reports incident activity that matches the settings of your connection, so the response begins without waiting for a check.

How it fires
instant, ilert calls Make through a webhook as soon as it happens, which is what the lightning badge on the module means.
When to use it
pick it when a delay between the incident and your automation would hurt, for example posting an alert to a team channel.
Watch out
click Create a webhook before Create a connection, and check your connection settings, since they decide what fires.
ilert2Watch New Incidents

Watch New Incidents

Scheduled trigger

In Make“Watches for new incidents.”

Every new incident in ilert becomes a bundle that the rest of your scenario can use without you copying anything by hand.

How it fires
scheduled, Make checks ilert on the scenario's schedule, shown by the clock badge; that is every 15 minutes by default, and never less than 15 minutes on the Free plan.
When to use it
choose it when a short wait is fine, such as logging incidents to a sheet or starting a review.
Watch out
each check counts operations, so a tight schedule uses your plan faster.
Modules

Everything the ilert modules can do

ilert gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

ilert1

Accept an Incident

Action

In Make“Accepts a specified incident.”

Marks a chosen incident as accepted, so ilert shows that someone owns it.

When to use it
when a responder confirms from another tool, such as a chat button or a form, and you want ilert to reflect it.
Watch out
it needs the incident to act on, so map it from a trigger or from Get an Incident.
ilert2

Assign an Accident

Action

In Make“Assigns a specified accident by user ID, escalation policy ID, or schedule ID.”

Hands an incident to a specific user, an escalation policy or a schedule, which saves a responder from reassigning it by hand in ilert.

When to use it
after Get a User On-Call, to route the incident to whoever is on duty right now.
Watch out
the module name says accident, but it works on ilert incidents; it targets by user ID, escalation policy ID or schedule ID.
ilert3

Create an Incident

Action

In Make“Posts new event with ALERT type (creates a new incident).”

Sends an alert event to ilert, which opens a new incident there without anyone logging in to ilert.

When to use it
when a problem is spotted outside ilert, for instance a failed payment in your shop or a monitoring email, and your on-call team must hear about it.
Watch out
put a filter before it, or every bundle that reaches it opens another incident.
ilert4

Get an Incident

Action

In Make“Returns a specified incident.”

Fetches the full details of one incident you already know, so later modules can work from all of its data.

When to use it
in the middle of a scenario, before writing a report or a message that needs more than the incident reference.
Watch out
it reads a single incident; to find several, use List Incidents instead.
ilert5

Get a User On-Call

Action

In Make“Returns a user on-call for the specified schedule.”

Tells you who is on call for a given schedule, which lets the scenario reach the right person without anyone looking at the rota.

When to use it
before Assign an Accident, or before sending a direct message to the person on duty through your chat tool.
Watch out
pick the right schedule in the module; each schedule has its own person on call.
ilert6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the ilert API with the connection you already set up, which covers the jobs the other nine modules leave out.

When to use it
when you need an ilert feature that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the ilert API documentation open and test it with Run once first.
ilert7

Resolve an Incident

Action

In Make“Resolves a specified incident.”

Closes a chosen incident in ilert, so the status your team sees matches the actual state of the problem.

When to use it
when the fix is confirmed elsewhere, for example a ticket moved to done or a health check back to normal.
Watch out
make sure the scenario targets the right incident, since resolving the wrong one hides a live problem.
ilert8

List Incidents

Search

In Make“Lists incidents or searches for them by specified criteria.”

Searches your ilert incidents with the criteria you set and returns each match as its own bundle, ready for the next module.

When to use it
to find the incident to resolve or to build a summary of open incidents for your manager.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle, which counts operations.
Need help

Need help automating ilert with Make?

A person reads every message.

FAQ

Common questions about ilert and Make

01Is the ilert Make integration free?
Yes, on the Make side. ilert is a standard app, so its 10 modules work on the Make Free plan. That plan allows 2 active scenarios, runs scheduled scenarios no more often than every 15 minutes, and caps each run at 5 minutes and files at 5 MB, with 512 MB of data transfer. Paid plans, Core, Pro, Teams and Enterprise, go down to a 1 minute interval and count usage in credits each month. You still need an active ilert account with its own subscription.
02What do you need to connect ilert to Make?
You need an active ilert account and an API key. In ilert, go to Profile, then API Keys, create a new key and copy it. In Make, add any ilert module, click Create a connection, give it a name if you want, and paste the key. The connection is then reused by every ilert module in your scenarios. If your first module is the instant trigger, click Create a webhook before creating the connection.
03Does the ilert trigger in Make react in real time?
It depends on which trigger you pick. Watch Connection Incidents is instant: ilert calls Make through a webhook as soon as something happens, so the scenario starts right away. Watch New Incidents is scheduled: Make checks ilert on the scenario's schedule, every 15 minutes by default, and never more often than that on the Free plan. Paid plans can go down to 1 minute. Choose the instant trigger when speed matters, the scheduled one for logging.
04What if an ilert module is missing in Make?
Use Make an API Call. It sends any request the ilert API accepts, with the connection you already created, so you are not limited to the 10 modules listed on this page. Build the request with the ilert API documentation next to you and test it with Run once before switching the scenario on. The Make documentation for ilert also warns that part of its content is AI-generated, so check important details with ilert directly.
05Should you use Make or n8n for ilert?
It depends on the rest of your stack. On Make, ilert comes with 10 ready modules, including an instant trigger, and Make an API Call covers the rest of the API. The same app often has a node in n8n as well, so the best choice is usually the tool where your other automations already run. Compare the two on the modules you actually need, and look at how each one handles connections, schedules and testing before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations