Pagerly Zapier integrationAutomate Pagerly with Zapier.
The Pagerly Zapier integration gives you 1 trigger, 0 actions and 1 search. It is small but sharp: a rotation change in Pagerly starts your Zap right away, and the search tells any Zap who is on call right now, so the rest of your tools can follow.
Verified Trustpilot reviews · AI, automation & growth agency
What the Pagerly Zapier integration actually does
It links Pagerly, where your team sets up rotations and on-call duty (simple, round robin or more complex), to Zapier, the tool that chains apps without code. You build a Zap (one starting event, then the steps after it) and Pagerly either starts it or answers a question inside it.
Three results teams build first. A handover message: New Rotation Change starts a Zap that posts in the support channel who takes over, so nobody pings the person who just went off duty. An on-call lookup for alerts: when a monitoring tool raises an incident, Find User(s) on Rotation finds the person currently on call so the next step can reach them. A duty log: each rotation change adds a row to a sheet, which gives managers a plain record of who covered what.
What Zapier does not do here. Pagerly has no actions on Zapier: a Zap cannot create a rotation, swap a shift or put someone on call. It can react to a change and read who is on rotation, nothing more. Every step that writes or sends lives in another app. And a Zap never goes back in time: rotation changes made before you switch it on are not replayed.
If you are still weighing the platform, the Zapier review covers it as a whole, and n8n vs Zapier puts it next to n8n.
Zapier words in one minute
Eight words come back on every line of this page. Here they are once, in ordinary language.
- Zap
- The automation you build on Zapier: one starting event, then one or more steps that run each time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Pagerly has one: a rotation change.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something. With Pagerly, it sits in another app.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Instant vs polling
- An instant trigger is reported by the app itself, with no wait. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it otherwise.
- Search step
- A step that looks up something that already exists in an app, such as who is on call, so later steps can use it.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A search, a filter or a second action makes one, and it needs a paid plan.
What it really costs to run
Pagerly is not a premium app on Zapier, so it works from the free plan. The meter that matters is the task count, and the shape of the Zap.
- Premium appNo, free plan works
- Trigger0 tasks
- Successful action1 task each
- Search in a ZapMulti-step, paid plan
The trigger never costs a task. Each action that succeeds counts as one, and a failed one is not counted. The free plan gives you 100 tasks a month but only builds two-step Zaps: one trigger, one action. That matters here, because the search is a step of its own: a Zap that uses Find User(s) on Rotation is multi-step and needs a paid plan. The interval grid below is for polling triggers; New Rotation Change is instant, so it does not apply.
Connect Pagerly to Zapier in 3 steps
- 01
Open your Apps page
In Zapier, go to the Apps page of your account. That is where every connection lives: your account of an app, linked once, then reused by every Zap that needs it.
- 02
Add the connection
Click + Add connection, type Pagerly in the dialog, pick it, then click Add connection. You need a Pagerly account, plus access to the teams whose rotations you want to follow.
- 03
Sign in and grant access
Sign in to Pagerly in the tab that opens and let Zapier access the account. From then on, any Zap can pick this connection from a list instead of asking you to log in again.
Your first Zap: announce the new on-call person to the team
GoalWhen a Pagerly rotation changes, find who is now on call and post their name in the support channel.
- 01
Build: pick the trigger
Create a Zap, choose Pagerly, then New Rotation Change, and select your connection. In Team Name, enter the team to watch, or all for every team.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items from your account, so you map the next steps on a real rotation change rather than an empty example.
- 03
Add the on-call search
Add Find User(s) on Rotation and give it the Team Name. This search makes the Zap multi-step, so it needs a paid plan. Keep the same team as the trigger.
- 04
Add the message
Add the channel message step and map the name the search found into the text, so the team reads who to call without opening Pagerly.
- 05
Test, then publish
Test each step once and read what came back. When it looks right, click Publish to switch the Zap on. From then on, each rotation change starts it right away.
The Pagerly trigger
1 event starts a Zap when something happens in Pagerly, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Rotation Change
Instant triggerIn Zapier“Triggers when a rotation is changed.”
Starts your Zap whenever a rotation changes in Pagerly, for one team or for all of them. It is the moment duty passes from one person to the next, which is exactly when the rest of your tools need to know.
The Pagerly search
1 search step looks for data that already exists in Pagerly, so a later step can use it.
Searches sit at the bottom of the event list, under the SEARCH heading of Action event. They fetch what already exists in Pagerly and hand it to the next steps. Adding one makes the Zap multi-step. Three settings decide what happens when the answer is not the expected one.
Find User(s) on Rotation
SearchIn Zapier“Get current user(s) / oncall(s) in your rotation.”
Returns the person or people currently on call in a given team's rotation. Any Zap can ask it, whatever started that Zap.
The three settings every search exposes
- Successful if no search results are found?Left as is, a search that finds nobody stops the Zap and skips the steps that needed a name. Switched on, the Zap goes on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. The Pagerly search does not offer it, so you will not see it.
- If multiple search results are found?Keep the first match, which is the default, stop the Zap, or hand every match on at once.
When it breaks
Zapier attaches no help article to Pagerly, so the known traps are the ones every Zap shares. Around on-call duty, they show up in specific ways.
Read these before you publish; an on-call Zap that fails quietly is worse than none. If one is already misbehaving, the Zapier troubleshooting guide walks through the usual causes.
Past rotation changes are never replayed
A Zap only reacts to what happens after you switch it on. Handovers that happened before stay out of it, and rebuilding that history is a separate job.A Zap that feeds its own trigger
A Zap that writes into the very place its own trigger watches sets itself off again and again. Pagerly has no action, but watch chains across your tools.A burst of changes can be held back
If a trigger suddenly sends a huge batch, for instance after a bulk import or a migration of rotations, Zapier's flood protection can hold the runs back.The search needs its own Team Name
Team Name is required on the trigger and again on the search. Filling it once does not carry over: set it on each step, and keep the same team on both.
Need help automating Pagerly with Zapier?
A person reads every message.
