Build it
What do you want PagerDuty and Pushover to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with PagerDuty and Pushover
Triggers and actions 2 triggers · 35 actions
Trigger
List Maintenance WindowsGets a list of maintenance windows (GET /maintenance_windows).
Trigger
New IncidentsPolls for new incidents in PagerDuty (GET /incidents, newest first).
Action
Add RespondersRequest additional responders (a user or escalation policy) to help with an incident.
Action
Add Team MemberAdd a user to a team with a given role.
Action
Create IncidentCreates an incident in PagerDuty (POST /incidents).
Action
Create Note on IncidentCreates a note on a given incident.
Action
Delete or End a Maintenance WindowDeletes a maintenance window that hasn't started yet, or ends one that is ongoing.
Action
Get Escalation PolicyRetrieve a single escalation policy by its ID.
Action
Get IncidentRetrieve a single PagerDuty incident by id.
Action
Get ScheduleRetrieve a single on-call schedule by its ID.
Action
Get ServiceRetrieve a single PagerDuty service by id.
Action
Get TeamRetrieve a single team by its ID.
Action
Get User InformationGets a user's information based on provided ID.
Action
List Escalation PoliciesList PagerDuty escalation policies (GET /escalation_policies).
Action
List Incident NotesList all notes attached to an incident.
Action
List IncidentsList PagerDuty incidents with filters (statuses, service_ids, urgencies, date range) (GET /incidents).
Action
List On-CallsList current on-call entries — who is on call now, by escalation policy/schedule/user/time window (GET /oncalls).
Action
List Schedule OverridesList overrides on a schedule within a required since/until time window.
Action
List SchedulesList PagerDuty on-call schedules (GET /schedules).
Action
List ServicesList PagerDuty services (GET /services).
Action
List TeamsList all teams in the account.
Action
List UsersList PagerDuty users (GET /users).
Action
Manage IncidentsBulk acknowledge or resolve multiple incidents in a single call.
Action
Snooze IncidentSnooze a triggered/acknowledged incident for a number of seconds so it won't re-alert until the snooze expires.
Action
Two-way sync add a maintenance windowCreates a maintenance window for use with two-way sync triggers (POST /maintenance_windows). Does not update. Use only with two-way sync triggers.
Action
Two-way sync add or update an incidentCreates or updates an incident for use with two-way sync triggers (POST /incidents; incident_key dedups). Use only with two-way sync triggers.
Action
Update IncidentUpdates an incident in PagerDuty. Set status to acknowledged or resolved to manage the incident.
Action
Update Maintenance WindowUpdates a maintenance window.
Action
Add GroupCreate a new Pushover delivery group. POST https://api.pushover.net/1/groups.json with token + name.
Action
Cancel Emergency Retry by ReceiptStop the ongoing retries of an emergency-priority notification by its receipt before it is acknowledged.
Action
Cancel Emergency Retry by TagStop the ongoing retries of all emergency-priority notifications sharing a given tag before they are acknowledged.
Action
Check ReceiptCheck the acknowledgement status of an emergency-priority (priority 2) notification by its receipt.
Action
Get GroupRetrieve a delivery group's info + member users. GET https://api.pushover.net/1/groups/{group_key}.json?token=...
Action
List SoundsRetrieve the list of notification sounds available to Pushover devices.
Action
Send NotificationSend a push notification to your Pushover devices with optional title, priority, sound, URL, and attachment.
Action
Update GroupRename a delivery group. POST https://api.pushover.net/1/groups/{group_key}/rename.json with token + name.
Action
Validate UserVerify that a Pushover user or group key is valid and has at least one active device.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.