Skip to content
One platform. From customer conversation to completed work.Take a closer look
All connections
Alerting & Incidents · CONNECTION

PagerDuty + NodeHub

Trigger incidents and on-call rotations.

Explore 10 workflow actions for PagerDuty, including account permissions and operation limits.

7 read actions3 write actions
WORKFLOW ACTIONS

What you can configure.

Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.

Add incident note

Write

Add a note to an incident as an account user.

Permissions and limits

Account permissions

  • incidents.write

Operation limits

  • A lost answer remains uncertain and is never resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Create incident

Write

Create an incident on an explicit PagerDuty service using an account user's identity.

Permissions and limits

Account permissions

  • incidents.write

Operation limits

  • PagerDuty can notify on-call responders. The selected service must support API-created incidents. incidentKey rejects a matching open incident rather than replaying its receipt. Writes are not retried automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Get incident

Read

Read a PagerDuty incident, including its current status, service and assignments.

Permissions and limits

Account permissions

  • incidents.read

Get log entry

Read

Read one log entry, optionally with its incident, service, channel and teams.

Permissions and limits

Account permissions

  • incidents.read

Get user

Read

Read one user, optionally with contact methods, notification rules and teams.

Permissions and limits

Account permissions

  • users.read

List incident notes

Read

Read every note on an incident.

Permissions and limits

Account permissions

  • incidents.read

List incidents

Read

Read PagerDuty incidents with status, service and date filters, retaining the provider's pagination metadata.

Permissions and limits

Account permissions

  • incidents.read

Operation limits

  • Returns one page with PagerDuty's actual limit, offset, more and optional total. Continue with offset plus limit while more is true. This connector caps offset at 9900; use date filters to narrow larger incident searches.
  • PagerDuty defaults the incident date window to one month and limits date ranges to six months.

Pagination: offset. Check the result for additional pages; a single action may not return every record.

List log entries

Read

Read one page of the account's log entries, optionally within a date range or for teams.

Permissions and limits

Account permissions

  • incidents.read

Operation limits

  • Returns one page with PagerDuty's limit, offset and more. Continue with offset plus limit while more is true, up to offset 9900.

Pagination: offset. Check the result for additional pages; a single action may not return every record.

List services

Read

Read accessible PagerDuty services and their provider pagination metadata.

Permissions and limits

Account permissions

  • services.read

Operation limits

  • Returns one page with PagerDuty's actual limit, offset, more and optional total. Continue with offset plus limit while more is true. This connector caps offset at 9900; use date filters to narrow larger incident searches.

Pagination: offset. Check the result for additional pages; a single action may not return every record.

Update incident

Write

Acknowledge, resolve or reopen an incident, or change its title or urgency.

Permissions and limits

Account permissions

  • incidents.write

Operation limits

  • Reopening can notify responders. NodeHub does not automatically repeat a write after a lost or malformed receipt.

A repeated request may repeat the external action. Review the previous result before retrying a write.

SETUP

Start with a controlled test.

01Connect the intended account

Use the account and permissions required for your process. Review the connection check before configuring a workflow action.

02Review inputs and access

Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.

03Confirm the result

Inspect step outputs and confirm the result in PagerDuty. A saved workflow is not a completed provider action.

Follow the workflow quickstart
EXPLORE YOUR STACK

More in Alerting & Incidents.

PagerDuty integration | NodeHub