Can NoClick open and route Pagerduty incidents on its own?

Yes. The Pagerduty node creates incidents, adds responders, and subscribes stakeholders to status updates. Wire it to any trigger, so an error spike, a failed check, or an inbound alert from another node can page the right person without anyone touching Pagerduty.

How do I connect Pagerduty to NoClick?

The node authenticates with a Pagerduty REST API token, which you generate in your Pagerduty account and paste into the node's credential field. Once it is saved, every operation runs against your account, so incidents and services show up under your own team.

Can a workflow start when a Pagerduty incident happens?

Yes. The On Incident Event trigger starts a workflow whenever an incident fires, so you can react in real time by tagging it, adding responders, or fanning the details out to a chat or email node. The incident payload is available to every downstream step.

Can it set up escalation policies and services, or only incidents?

Both. Beyond creating incidents, the node creates escalation policies, business services, event orchestrations, and incident workflows, and it can associate service dependencies and attach an escalation policy to a service. A single run can stand up the on-call structure a new service needs, not just page against an existing one.

Can it manage on-call teams and responders?

Yes. The node adds team members, creates contact methods, and adds responders to a live incident. You can automate onboarding by adding a new engineer to a team and creating their contact method so they are reachable when they go on call.

PagerDuty Integration

PagerDuty incident management automation

248 operations availableDeveloper Tools

Pagerduty is the on-call and incident response platform engineering teams use to route alerts to whoever is holding the pager. The NoClick Pagerduty node calls the Pagerduty REST API, so a single workflow can create incidents, add responders, subscribe stakeholders to status updates, and tag incidents for reporting. It also builds the structure behind on-call: escalation policies, business services, event orchestrations, incident workflows, and service dependencies. Drop it on the canvas to open and route incidents automatically instead of by hand.

What you can automate with PagerDuty

Pick one to start building it.

PagerDuty Operations

Triggers1

Incidents7

Incident Details20

Services5

Schedules & On-Call11

Escalation Policies5

Users & Teams26

Maintenance Windows5

Events API1

Webhooks8

Reference8

Service Dependencies4

Service Integrations3

Service Event Rules5

Extensions8

Event Orchestrations18

Event Rulesets (Legacy)10

Response Plays6

Automation Actions8

Automation Runners5

Incident Workflows6

Workflow Triggers7

Business Services13

Status Dashboards4

Status Pages15

Analytics6

Audit1

Change Events3

Custom Fields10

Templates6

Tags6

Vendors2

Add-ons5

Templates using PagerDuty

Incident Scribe Agent

Posts a structured incident update to Slack within seconds of a page, with impact, owner and a next update time, and mirrors it into the incident timeline without ever touching the incident itself. In the first ten minutes of an incident the responder is debugging and everyone else is asking what is happening, and one of those two jobs always loses. This agent takes the second one: it reads the incident, its alerts and the closest past incident, posts one structured update to your comms channel, then writes the same thing back to the incident timeline. It never acknowledges, resolves or reassigns anything, so the responder keeps the incident and loses the audience. ## What people use it for - **The first update in seconds** - The comms channel gets what broke, who has it and when the next update lands before the responder has finished reading the alert. Nobody has to be appointed scribe at the start of a call. - **Stop the side channel questions** - A stated next update time is what stops six people asking for status at once. Stakeholders wait for the clock instead of messaging whoever is in the middle of fixing it. - **Past incidents surface themselves** - The closest previous incident on the same service, and how it ended, is pulled into the update. A repeat page arrives with its own history attached instead of being rediscovered at the postmortem. - **A timeline the postmortem can use** - Every update is written back to the incident as a note with its time, so what PagerDuty records and what the channel was told stay the same story, minute by minute. ## Before you fork **What do I need to connect before this works?** A PagerDuty credential that can read incidents and alerts and add notes, plus the Slack channel your incidents are communicated in. Your runbook notes and the cadence and tone you want go in as variables. It does not need permission to acknowledge or resolve anything, and it is safer if you never give it any. **What does it cost to run?** One run per incident event you forward, so cost follows your paging volume. Point the trigger at the services that need public communication rather than every service, and a normal week is a handful of runs. Noisy services are better filtered at PagerDuty than handled here. **Could it say something wrong while an incident is live?** It writes only from the incident, the alerts, the past incidents and your runbook notes. Impact the data does not confirm is written as not yet confirmed rather than estimated, and it states no cause, ETA or customer count it cannot see. It has no ability to acknowledge, resolve, reassign or escalate, so the worst case is an update thinner than you wanted, which the responder can correct in the same channel.

5804 nodes

Frequently asked questions

Use PagerDuty as an AI agent tool

Wire PagerDuty into a coding agent and let it use these operations as tools.

Ready to build with PagerDuty?

Start building workflows in minutes with our visual builder. No code required.

Book Demo

Browse all integrations

PagerDuty Integration

What you can automate with PagerDuty

PagerDuty Operations

Triggers1

Duty Incident Trigger

Incidents7

Duty List Incidents

Duty Get Incident

Duty Create Incident

Duty Update Incident

Duty Manage Incidents

Duty Snooze Incident

Duty Merge Incidents

Incident Details20

Duty List Notes

Duty Create Note

Duty Create Status Update

Duty List Alerts

Duty List Log Entries

Duty Add Responders

Duty Get Alert

Duty Update Alert

Duty Manage Alerts

Duty Get Incident Custom Fields

Duty Update Incident Custom Fields

Duty List Related Change Events

Duty Get Past Incidents

Duty Get Related Incidents

Duty Get Outlier Incident

Duty List Status Update Subscribers

Duty Add Status Update Subscribers

Duty Remove Status Update Subscriber

Duty List Global Log Entries

Duty Get Log Entry

Services5

Duty List Services

Duty Get Service

Duty Create Service

Duty Update Service

Duty Delete Service

Schedules & On-Call11

Duty List Schedules

Duty Get Schedule

Duty List On Calls

Duty Create Schedule

Duty Update Schedule

Duty Delete Schedule

Duty Preview Schedule

Duty List Users On Schedule

Duty List Overrides

Duty Create Override

Duty Delete Override

Escalation Policies5

Duty List Escalation Policies

Duty Create Escalation Policy

Duty Get Escalation Policy

Duty Update Escalation Policy

Duty Delete Escalation Policy

Users & Teams26

Duty List Users

Duty Get User

Duty Create User

Duty Get Current User

Duty List Teams

Duty Update User

Duty Delete User

Duty List Contact Methods

Duty Create Contact Method

Duty Get Contact Method

Duty Update Contact Method

Duty Delete Contact Method

Duty List Notification Rules

Duty Create Notification Rule

Duty Get Notification Rule

Duty Update Notification Rule

Duty Delete Notification Rule

Duty Get Team

Duty Create Team

Duty Update Team

Duty Delete Team