PagerDuty incident management automation
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.
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.
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.
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.
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.
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.