Resources · Make integration

Pagerly - Rotations , Oncalls and Incidents Make integrationAutomate Pagerly - Rotations , Oncalls and Incidents with Make.

Who is on call right now, and can the rest of your stack know it too? The Pagerly - Rotations , Oncalls and Incidents Make integration gives you 3 modules: one trigger and two actions. This guide is for ops and support leads, and it walks you from connection to a first working scenario.

Try the Pagerly - Rotations , Oncalls and Incidents integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pagerly - Rotations , Oncalls and Incidents Make integration do?

It links your Pagerly account to Make so a scenario, the automation you build in Make, can notice a change in an on-call rotation and look up who holds the shift. Each brick of that scenario is a module, and Pagerly offers three of them, all usable without writing code.

Keep a shared channel aware of the handover. Watch Oncall / Rotation Change spots the switch, then Get the Rotation / Oncall User returns the person now on duty, ready to be posted wherever your team reads alerts.

Answer the question "who do I call?" from another tool. A form, a ticket or a sheet in another app can start the scenario, and Get the Rotation / Oncall User fills in the current responder without anyone opening Pagerly.

Reach what the listed modules skip. Make an API Call talks to the Pagerly API with the same connection, which is the route for incidents or anything else the two named modules do not cover.

Be aware of one limit before you start: Make itself flags the Pagerly documentation as limited, because there is not enough public information about the app. Module fields and outputs are therefore something you discover in the editor with a test run. If that feels thin, the Make troubleshooting guide helps you read failed runs, and the Make training covers mapping from scratch.

Weighing another tool? The n8n vs Make comparison lays out how the two platforms differ in general.

Connect

How do you connect Pagerly to Make?

  1. 01

    Open the connection window

    Add any Pagerly module to your scenario and click Create a connection. The connection is your Pagerly account linked to Make once, then reused by all three modules, so you only do this step a single time.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when several teams share the workspace. Then authorize Make on the Pagerly page that opens, or paste the key Pagerly gives you, depending on what the window asks for.

  3. 03

    Save and check the list

    Click Save. Back in the module, the connection now appears in the dropdown, and Make can show the objects it is able to read from your account while you fill the fields.

First scenario

Your first scenario: hear about every rotation change

GoalWhen an on-call rotation changes in Pagerly, Make fetches the person now on duty.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Add the trigger

    Search for Pagerly, pick Watch Oncall / Rotation Change and choose your connection. Fill its fields; Make lists what it can read from Pagerly once the account is linked.

  3. 03

    Fetch the on-call person

    Click the + on the right of the trigger, add Get the Rotation / Oncall User, and fill its fields with data mapped from the trigger's bundle.

  4. 04

    Test with Run once

    Click Run once, then open each module's bubble to read the bundles it received. A bundle is one item passed along, here one rotation change.

  5. 05

    Schedule and switch on

    Open the clock on the first module; a new scenario checks every 15 minutes by default. Adjust it if your plan allows, then switch the scenario on.

Triggers

What starts a Pagerly scenario

1 module starts a scenario when something happens in Pagerly - Rotations , Oncalls and Incidents. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Pagerly - Rotations , Oncalls and Incidents as soon as it happens.

Pagerly - Rotations , Oncalls and Incidents1Watch Oncall / Rotation Change

Watch Oncall / Rotation Change

triggerIn the docs only

This trigger gives you a starting point each time an on-call rotation changes hands in Pagerly, so the rest of the scenario can react to the handover. Make lists it as a trigger; its scheduled nature is inferred from its name, not confirmed by the documentation.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default and never under 15 minutes on the Free plan.
When to use it
when a shift handover should be announced or recorded somewhere other than Pagerly.
Watch out
a scheduled check can pick up a change a few minutes after it happens, so run it once first and read the bundle to see what a change looks like.
Modules

What the Pagerly modules do

Pagerly - Rotations , Oncalls and Incidents gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Pagerly - Rotations , Oncalls and Incidents1

Get the Rotation / Oncall User

ActionIn the docs only

Returns the person currently on duty for a rotation, as a bundle you can map into any later module of the scenario.

When to use it
right after the trigger, or when a ticket or form from another app needs the name of the current responder.
Watch out
the documentation does not list its outputs, so click Run once and inspect the bundle before mapping anything downstream.
Pagerly - Rotations , Oncalls and Incidents2

Make an API Call

ActionIn the docs only

Opens the whole Pagerly API to your scenario, with the connection you already set up, for any request the two named modules leave out.

When to use it
incident data or any other endpoint you need that neither the trigger nor Get the Rotation / Oncall User reaches.
Watch out
you need the Pagerly API reference to build the request, since Make gives no details on it for this app.
Need help

Need help automating Pagerly - Rotations , Oncalls and Incidents with Make?

A person reads every message.

FAQ

Questions about Pagerly and Make

01Is the Pagerly - Rotations , Oncalls and Incidents Make integration free?
Yes, Pagerly is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one per module run on one bundle, against your monthly credits. The Pagerly subscription itself is a separate matter handled with Pagerly.
02What do you need to connect Pagerly to Make?
A Pagerly account and the right to authorize an outside tool on it. The Make documentation gives no Pagerly-specific prerequisite and no dedicated steps, so the generic flow applies: add a Pagerly module, click Create a connection, name it if you want, authorize Make on the Pagerly page or paste the key Pagerly provides, then click Save. The same connection serves all 3 modules afterwards. If something in the authorization window is unclear, the person who manages Pagerly for your team is the best one to ask, since public documentation on the app is limited.
03Does the Pagerly trigger react in real time?
No, not as far as the listing shows. Watch Oncall / Rotation Change is treated as a scheduled trigger, a type inferred from its name because the documentation does not describe it. A scheduled trigger means Make asks Pagerly for changes on the scenario's schedule, every 15 minutes by default, down to 1 minute on paid plans. It carries the clock badge in the editor, not the lightning badge of an instant trigger. For a handover announcement this delay is usually acceptable; for paging someone during an incident, keep Pagerly itself as the alerting channel.
04What if a Pagerly module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Pagerly API with the connection you already created, so incidents or other objects outside the trigger and Get the Rotation / Oncall User stay within reach. The catch is that Make publishes limited documentation for this app, which means you will lean on the Pagerly API reference to know which request to send. Build the call, click Run once and read the returned bundle before mapping it into the next module. Keep the request small at first, so a failed run is easy to understand.
05Make or n8n for Pagerly?
It depends on the platform your team already runs its automations on. On the Make side, the facts are clear: 3 modules, one trigger, a lookup of the current on-call person and an open door to the whole API through Make an API Call, all on the Free plan. The same app often has an n8n node as well, but availability and depth there are worth checking on your own before choosing. Pick the tool where your other scenarios already live, so the Pagerly data joins the rest of your flows without a second platform to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations