PagerDuty n8n integrationAutomate PagerDuty with n8n.
Every alert that reaches a human should already carry its context. The PagerDuty n8n integration puts 9 operations across 4 resources inside a workflow: incidents, notes, log entries and users. PagerDuty has no trigger node in n8n, so the workflow starts elsewhere. Built for on-call teams.
Verified Trustpilot reviews · AI, automation & growth agency
What does the PagerDuty n8n integration actually cover?
The PagerDuty node ships with n8n and talks to the PagerDuty REST API on your behalf. It exposes 9 operations grouped into 4 resources: Incident, Incident Note, Log Entry and User. That means a workflow can open an incident, read it back, list incidents, update its status, attach notes, pull log entries and look up a user, all with the same credential you set up once.
One thing to get straight first: there is no PagerDuty trigger node in n8n. Nothing in PagerDuty starts a workflow by itself. The workflow starts with a Schedule Trigger on a fixed interval, with an n8n Webhook (a URL n8n exposes so another service can call it), or with the trigger of another tool, and PagerDuty sits downstream as the action.
Three shapes come up again and again. The first is incident creation from a check you already run: a scheduled workflow queries an endpoint or a database, sees a failure, and calls incident.create on the right service. The second is enrichment. An incident exists, so the workflow reads it, pulls the last log entries, resolves the assignee with user.get and posts a digest to Slack or Telegram before anyone opens a laptop. The third is reporting: incident.getAll with a date range, dropped into Google Sheets for the weekly on-call review.
Closing the loop matters as much as opening it. When the monitoring side reports the service healthy again, incident.update sets the status to resolved and writes what happened into the Resolution field, so the incident carries its own conclusion.
Where the node stops, HTTP Request continues. Any endpoint of the PagerDuty REST API is reachable from the HTTP Request node, reusing the same PagerDuty credential through predefined authentication, so you stay on one set of keys. Two boundaries are worth knowing up front: a listing only returns everything if Return All is on, since n8n otherwise stops at Limit, and the Since and Until date range of a search is capped at 6 months.
If on-call is the first automation your team builds, the n8n review covers what the platform is good at, and the n8n training goes through building workflows like these step by step.
How do you connect PagerDuty to n8n?
- 01
Create the credential once in n8n
In n8n, open the Credentials menu and add a PagerDuty credential. A credential is a stored set of keys: you create it once and every workflow picks it from the node's dropdown. The node supports two authentication methods, API token and OAuth2. A token is the shortest path for a workflow that runs unattended; OAuth2 fits when access should be tied to an app you registered.
- 02
Generate a general access API token
For the token method, you need a general access API Token from PagerDuty. Open Integrations, then Developer Tools, then API Access Keys, then Create New API Key. Copy the key that PagerDuty shows you and paste it into the API Token field of the n8n credential. That key is what the node sends on every call to the REST API.
- 03
Or register an app for OAuth2
For OAuth2, register a new PagerDuty app. In the Category dropdown pick Infrastructure Automation, and in the Functionality section select OAuth 2.0. Save, then edit the app configuration: under OAuth 2.0 select Add, copy the OAuth Callback URL from n8n into the Redirect URL field, paste the Client ID and Client Secret into n8n, and choose Read/Write in the Set Permission Scopes list.
What can the PagerDuty node do?
The PagerDuty node exposes 9 operations across 4 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
| Resource | Create | Get | Get Many | Update |
|---|---|---|---|---|
| Incident | ✓ | ✓ | ✓ | ✓ |
| Incident Note | ✓ | ✓ | ||
| Log Entry | ✓ | ✓ | ||
| User | ✓ |
Incident
4 operationsCreate an incident
incident.createWhat you see in n8n
Notes & use cases
Opens a new incident in PagerDuty from whatever the workflow just detected, and returns the created incident for later nodes.
Key parameters
- Title: a succinct description of the nature, symptoms or cause, often built from the alert payload with
{{ $json.message }}. - Service Name or ID: the service the incident is created on, chosen from the list or set by expression.
- Email: a valid user of the account making the request, in the
name@email.comformat. - Incident Key: in Additional Fields, the de-duplication key. A later request on the same service with the same key is rejected while a matching incident stays open.
Get an incident
incident.getWhat you see in n8n
Notes & use cases
Pulls a single incident back from PagerDuty, which is how a workflow checks the current state of a page before doing anything else with it.
Key parameters
- Incident ID: the unique identifier of the incident, not its title. It usually comes from an earlier node as
{{ $json.id }}.
Get many incidents
incident.getAllWhat you see in n8n
Notes & use cases
Lists incidents from the account, with an Options collection of 12 filters to narrow the set down to what a report needs.
Key parameters
- Return All: on, n8n walks the API pages and brings back every matching incident; off, Limit caps how many come back.
- Statuses: keeps only the
triggered,acknowledgedorresolvedones. - Since and Until: the start and end of the search window, limited to 6 months.
- Include: adds details such as assignees or services to each record.
Update an incident
incident.updateWhat you see in n8n
Notes & use cases
Changes an incident that already exists. Status, title, urgency, priority and escalation all live here, in an Update Fields collection of 7 entries.
Key parameters
- Incident ID: which incident gets changed.
- Email: the address of a valid account user, required on this operation as well.
- Status:
acknowledgedorresolved. - Resolution: the resolution text, which only carries meaning when the status is set to resolved.
- Escalation Level: escalates the incident to that level of its escalation policy.
Incident Note
2 operationsCreate an incident note
incidentNote.createWhat you see in n8n
Notes & use cases
Attaches a note to an incident. This is how an automation leaves context for whoever picks up the page at three in the morning.
Key parameters
- Incident ID: the incident the note is filed against.
- Content: the note text itself, where a workflow drops the failing log lines or the runbook link it just fetched.
- Email: again a valid user of the account making the request.
Get many incident notes
incidentNote.getAllWhat you see in n8n
Notes & use cases
Reads back the notes already filed on one incident, in bulk rather than one by one.
Key parameters
- Incident ID: notes belong to a single incident, so this one is required.
- Return All: every note on the incident; switched off, Limit decides how many come back.
Log Entry
2 operationsGet a log entry
logEntry.getWhat you see in n8n
Notes & use cases
Fetches one log entry. A log entry is PagerDuty's record of a single thing that happened to an incident, such as a trigger, an acknowledgement or a notification.
Key parameters
- Log Entry ID: the unique identifier of that entry, normally taken from a previous listing as
{{ $json.id }}.
Get many log entries
logEntry.getAllWhat you see in n8n
Notes & use cases
Returns log entries across the account over a period. It is the closest thing to an activity feed the node exposes, with an Options collection of 5 filters.
Key parameters
- Return All: every entry across pages, or Limit for a sample.
- Is Overview: on, only the most important changes to the incident come back, which keeps a timeline readable.
- Since and Until: the search window, again capped at 6 months.
- Timezone Name or ID: dates come back in UTC unless this is set.
User
1 operationGet a user
user.getWhat you see in n8n
Notes & use cases
Looks up one user of the PagerDuty account and returns their profile, so a workflow can name the person behind an identifier.
Key parameters
- User ID: the unique identifier of the user, normally read from an incident rather than typed by hand.
Need help automating PagerDuty with n8n?
A person reads every message.
