Resources · Make integration

Opsgenie Make integrationAutomate Opsgenie with Make.

Can Make open an Opsgenie alert for you when something breaks elsewhere? Yes. The Opsgenie Make integration gives you 6 action modules, from Create Alert to Make an API Call. This page shows on-call and ops teams how to connect the account and build a first alert flow.

Try the Opsgenie integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Opsgenie Make integration do for you?

The Opsgenie Make integration lets a Make scenario, the automation you build as a chain of bricks called modules, act on your Opsgenie alerts. It can open an alert, add a note or tags, read one back, or delete it. Opsgenie never starts the scenario itself: another app or Make's schedule does.

A failed payment becomes an alert. When a module from your billing or monitoring app reports an error, Create Alert opens the alert in Opsgenie so the person on call sees it without anyone copying details by hand.

Context lands on the alert. Add Note to Alert writes what the other app knows (the customer, the error text) on the alert, and Add Tags to Alert labels it so your Opsgenie filters sort it correctly.

Cleanup after a false alarm. Get an Alert reads an alert back so a later module can check it, and Delete Alert removes one that should never have been created.

What Make does not give you here: a trigger. No module watches Opsgenie for new or closed alerts, and Make's own documentation for this app is marked as limited. For anything outside the five alert modules, Make an API Call reuses the same connection. The same app may also exist in n8n; the n8n vs Make comparison helps you pick, and the Make pricing page explains what each run costs in operations. If you would rather hand the build over, see the Make agency page.

Connect

How do you connect Opsgenie to Make?

  1. 01

    Add an Opsgenie module

    In a new scenario, click the +, search for Opsgenie and pick any of its modules, Create Alert for instance. Then click Create a connection. A connection is your Opsgenie account linked to Make once, then reused by every Opsgenie module.

  2. 02

    Name the connection

    Give it a name you will recognize later, such as the team or environment it belongs to. This step is optional, but it saves guesswork the day you run two Opsgenie accounts side by side in the same Make organization.

  3. 03

    Authorize and save

    Follow what the window asks: either approve Make on the Opsgenie page that opens, or paste the key Opsgenie gives you. Click Save. From there the module fields fill with what Make can read from your account.

First scenario

Your first scenario: open an Opsgenie alert and explain it

GoalWhen another app reports a problem, Make opens an alert in Opsgenie and adds a note with the details.

  1. 01

    Start the scenario from the source app

    From the Scenarios page, create a new scenario and click the +. Pick the module of the app that spots the problem, since Opsgenie has no trigger of its own to start with.

  2. 02

    Add Create Alert

    Click the + on the right of that first module, search for Opsgenie and choose Create Alert. Connect your account, then map the error details from the previous module into the alert fields.

  3. 03

    Attach the context with a note

    Add Add Note to Alert after it. Point it at the alert Create Alert just produced by mapping data from that module, and write the note from what the source app sent: the customer, the error, a link.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles, the items each module received and passed on. Check in Opsgenie that the alert and its note look right.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) if the source app is polled, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the Opsgenie modules do

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

Opsgenie1

Add Note to Alert

Action

In Make“Adds note to alert at OpsGenie”

This module writes a note on an existing Opsgenie alert, so the responder opens it and already finds the context another app collected.

When to use it
right after Create Alert, or later in the flow when a second system reports what happened next, such as a retry that failed again.
Watch out
the note needs an alert to land on, so map the alert from an earlier module instead of typing it.
Opsgenie2

Add Tags to Alert

Action

In Make“Adds tags to alert at OpsGenie”

Tags turn a vague alert into one your team can filter: this module adds labels to an alert that already exists in Opsgenie.

When to use it
when the source app tells you which product, customer tier or region is affected, and you want that visible without reading the whole alert.
Watch out
a filter only catches a tag spelled the same way every time, so agree on the spelling with your team before the scenario starts writing them.
Opsgenie3

Create Alert

Action

In Make“Creates an alert at OpsGenie”

With Create Alert, a problem detected anywhere in your scenario becomes a proper Opsgenie alert that reaches whoever is on call.

When to use it
as the main action of most Opsgenie scenarios, placed after the module of the app that notices the failure, a form entry or an error row.
Watch out
every bundle that reaches this module opens one alert, so filter upstream or a busy source app will flood your on-call rotation.
Opsgenie4

Delete Alert

Action

In Make“Deletes an alert from OpsGenie”

Delete Alert removes an alert from Opsgenie entirely, which keeps the list clean when a scenario opened one by mistake.

When to use it
in a cleanup path, once another module has confirmed the alert was a test or a false alarm.
Watch out
treat a deletion as final: Make has no undo button for it. Run it on a test alert with Run once before letting it touch real incidents.
Opsgenie5

Get an Alert

Action

In Make“Gets an alert from OpsGenie”

Get an Alert reads one Opsgenie alert back into the scenario, so the next modules can use what it contains instead of guessing.

When to use it
before deciding what to do with an alert, for example to check its details before adding tags or passing them to a chat or ticket app.
Watch out
it fetches a single alert you point it to; it does not search Opsgenie for alerts matching a condition.
Opsgenie6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call”

Make an API Call covers whatever the five alert modules leave out: it calls any endpoint of the Opsgenie API with the connection you already set up.

When to use it
when you need an Opsgenie action that has no dedicated module in Make, and you are comfortable reading the Opsgenie API reference.
Watch out
you write the request yourself, so test it with Run once and read the response bundle before relying on it.
Need help

Need help automating Opsgenie with Make?

A person reads every message.

FAQ

Opsgenie and Make: common questions

01Is the Opsgenie Make integration free?
Yes, Opsgenie is a standard app in Make, available from the Free plan. The Free plan limits you to 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Every module run counts as an operation, and your plan gives you a monthly amount of credits. Opsgenie's own subscription is a separate matter this page does not cover.
02What do you need to connect Opsgenie to Make?
An Opsgenie account and a Make account. Make's documentation lists no specific prerequisite for this app and is marked as limited. The connection follows Make's usual path: add an Opsgenie module, click Create a connection, optionally name it, then either authorize Make on the Opsgenie page or paste the key Opsgenie gives you, and click Save. If the window asks for access you lack, the person who manages your Opsgenie account is the one to ask.
03Can an Opsgenie event start a Make scenario?
No, not with the listed modules: Opsgenie has no trigger in Make, only 6 actions. The scenario starts from something else. Either a module of another app opens the flow, for instance the tool that detects the failure, or you use the schedule on the first module, every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. Opsgenie then receives the result through Create Alert or the other actions.
04What if the Opsgenie module you need is missing?
Use Make an API Call. It reaches any endpoint of the Opsgenie API with the same connection as the other modules, so you are not limited to creating, reading, tagging, annotating and deleting alerts. You write the request yourself, which means reading the Opsgenie API reference. Keep in mind that Make's documentation for this app is limited, so test each call with Run once. If that path feels too heavy, another tool in your stack may already cover the step.
05Should you use Make or n8n for Opsgenie?
It depends on what you need to build. In Make, Opsgenie offers 6 action modules and no trigger, which suits flows where another app detects the problem and Opsgenie receives the alert. Make an API Call fills the gaps with the same connection. Apps like Opsgenie often have an n8n node too, so check whether it exists and which operations it lists, then compare the two against your own scenario rather than on reputation. The n8n vs Make comparison linked above sets out the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations