Resources · Make integration

PagerDuty Make integrationAutomate PagerDuty with Make.

Can an alert from another tool reach PagerDuty without anyone copying it by hand? The PagerDuty Make integration gives you 6 modules: 1 trigger, 4 actions and 1 search. This guide shows how to connect your account and build a first scenario that sends events to PagerDuty.

Try the PagerDuty integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PagerDuty Make integration do for your team?

The PagerDuty Make integration links your PagerDuty account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. Once connected, Make can send events to PagerDuty, read and update incidents, and look up who is on call.

Alerts from other tools, routed to PagerDuty. A support ticket flagged urgent or a failed payment in another app can start the scenario, and Create an Event passes it to PagerDuty under the incident key you pick. No more pasting alerts into a chat and hoping someone sees them.

Incidents kept in sync with the rest of your stack. Get an Incident pulls the full details of one incident so you can copy them into a ticket or a report, and Update an Incident writes changes back when work moves forward elsewhere.

The right person, named in the message. List On-Call Users finds who is on call for a schedule, so a notification can mention that person instead of a whole channel.

What to know before you start: the only trigger, Watch Incidents, is marked deprecated in Make, and the official doc gives no limit or troubleshooting tip for this app. Make an API Call covers anything the listed modules skip. PagerDuty also has an n8n node, described on the PagerDuty n8n integration page, and the n8n vs Make comparison sets the two tools side by side. New to Make? The Make training starts from zero.

Connect

How do you connect PagerDuty to Make?

  1. 01

    Add a PagerDuty module

    Log in to Make, open a scenario and add any PagerDuty module. Click Create a connection. A connection is your PagerDuty account linked to Make once, then reused by every PagerDuty module you add later.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name helps when you have several PagerDuty accounts, one for production and one for tests for example. Anything readable works.

  3. 03

    Paste your credentials

    You need an active PagerDuty account and an API key. Enter the credentials copied from PagerDuty, or follow the on-screen instructions. For OAuth, register an app under App Registration in PagerDuty and copy its Client ID and Client secret.

First scenario

Build your first scenario with PagerDuty

GoalWhen an urgent alert shows up in another app, Make sends an event to PagerDuty with Create an Event.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Pick the app where your alerts start: a helpdesk, a form, a monitoring tool. Its trigger opens the flow.

  2. 02

    Set the starting trigger

    Configure that first module so it only catches what deserves a page: urgent tickets, failed checks. Each item it catches becomes a bundle, one record passed on to the next module.

  3. 03

    Add Create an Event

    Click the + on the right, search for PagerDuty and choose Create an Event. Connect your account, then map the alert text from the first module into the event fields.

  4. 04

    Test with Run once

    Click Run once and trigger a real alert in the source app. Open the bubble above each module to read the bundles it received, then check that the event reached PagerDuty.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Switch the scenario on.

Triggers

What starts a PagerDuty scenario?

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

PagerDuty1Watch Incidents DEPRECATED

Watch Incidents DEPRECATED

Instant trigger

In Make“Triggers when new incidents are created, or when existing incidents change state.”

Watch Incidents starts a scenario when a new incident is created in PagerDuty or when an existing one changes state. Make lists it as deprecated, so treat it as a module to keep an eye on rather than one to build around.

How it fires
instant, PagerDuty calls Make through a webhook as soon as the incident appears or moves.
When to use it
an existing scenario already depends on it, such as posting each new incident into a team channel.
Watch out
on this module, click Create a webhook before Create a connection, and keep in mind that the deprecated label is a warning sign for any new build.
Modules

What else can Make do in PagerDuty?

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

PagerDuty1

Create an Event

Action

In Make“Creates a new event for the specified incident key.”

Create an Event sends a new event into PagerDuty, attached to the incident key you provide. It is the bridge that lets an alert born in another app land where your on-call team already looks.

When to use it
a payment tool reports a failure, or a support ticket gets tagged critical, and someone has to know now.
Watch out
reuse the same incident key for alerts about the same problem, since the key is what ties the event to its incident.
PagerDuty2

Get an Incident

Action

In Make“Shows detailed information about an incident.”

Get an Incident returns the detailed record of a single incident. Pick it when you already know which incident you care about and need its details in the next module, not a list of everything open.

When to use it
a post-incident review doc needs the facts of one incident copied in without retyping.
Watch out
it reads one incident only; tell it which incident you mean, usually by mapping it from an earlier module.
PagerDuty3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the PagerDuty API with the connection you already set up. Think of it as the spare key: when none of the other five modules does the job, this one can.

When to use it
you need a PagerDuty feature the listed modules skip, such as data the incident modules do not return.
Watch out
you write the request yourself, so keep the PagerDuty API reference open while you build it.
PagerDuty4

Update an Incident

Action

In Make“Updates incident information.”

Update an Incident changes the information on an incident that already exists. It keeps PagerDuty honest when the real work happens in another tool, like a ticket that gets resolved in your helpdesk.

When to use it
an engineer closes the matching task elsewhere and PagerDuty should reflect that without a second manual update.
Watch out
the change is written straight to the live incident, so run it once on a test incident before switching the scenario on.
PagerDuty5

List On-Call Users

Search

In Make“Finds the user on call for a specific schedule.”

List On-Call Users tells you who is on call for a given PagerDuty schedule. As a search module, it can return zero, one or several people, each as a separate bundle.

When to use it
a message about an outage should name the person on duty instead of pinging an entire channel.
Watch out
if two people share the shift, the next module runs twice, once per bundle, and each run costs an operation on your plan.
Need help

Need help automating PagerDuty with Make?

A person reads every message.

FAQ

Questions people ask about PagerDuty and Make

01Is the PagerDuty Make integration free to use?
Yes. PagerDuty is a standard app in Make, so it works on the Free plan. That plan has real limits though: 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the minimum interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one operation being one module handling one bundle. Your PagerDuty subscription is separate and set by PagerDuty.
02What does it take to connect PagerDuty to Make?
You need an active PagerDuty account and an API key from it. In Make, add a PagerDuty module, click Create a connection, give it a name if you like, and paste the credentials. If you go the OAuth route, register an app in PagerDuty under Integrations, then App Registration, select OAuth 2.0 and copy the Client ID and Client secret it shows. For the instant Watch Incidents module, click Create a webhook before creating the connection.
03Does the PagerDuty trigger in Make react in real time?
Yes, as far as the trigger type goes. Watch Incidents is an instant trigger: PagerDuty calls Make through a webhook as soon as an incident is created or changes state, with no polling interval. The catch is that Make marks this module as deprecated, so it is a poor base for a new scenario. For flows that start elsewhere, open the scenario on another app's trigger and use Create an Event or Update an Incident to act in PagerDuty.
04What if a PagerDuty module is missing in Make?
Use Make an API Call. It calls any endpoint of the PagerDuty API with the connection you already created, so the scenario is not limited to the five listed actions and searches. You build the request yourself, which means reading the PagerDuty API reference for the endpoint you want. The Make documentation for this app lists no specific limits or troubleshooting notes, so test each new call with Run once on data you can safely change.
05Make or n8n for PagerDuty automation?
It depends on the tool your team already works in. PagerDuty has an n8n node as well as this Make app, and both can talk to your PagerDuty account. On the Make side you get 6 modules: one instant trigger that is now deprecated, four actions including Make an API Call, and one search for on-call users. Compare that list with the n8n node's operations for the exact task you have in mind before you commit to one tool.
Same platform

Other docs you might need on this stack.

Browse all integrations