Skip to content
PagerDuty logo

PagerDuty integration

Incident management workflows for PagerDuty REST API v2.

Actions
6
Triggers
3
Auth
API key
License
MIT, open source
Updated
September 2026

About the PagerDuty integration

Add the PagerDuty piece to a flow, connect your account once, and the rest of the builder can read from it and write to it. Because the piece is open source you can run it on our cloud or self-host it, and combine PagerDuty with 770+ other apps in the same flow.

Triggers

Start a flow the moment something happens in PagerDuty

Each trigger below can start a flow on its own, either instantly or on a schedule.

  • New Incident

    Triggers when a new incident is created

    1 field

  • Incident Resolved

    Triggers when an incident is resolved.

    1 field

  • Incident Acknowledged

    Triggers when an incident is acknowledged.

    1 field

Actions

Everything Activepieces can do in PagerDuty

Drop any of these into a flow and fill in the fields. No code is required.

  • Create Incident

    Create a new PagerDuty incident using the REST API.

    10 fields

  • List Incidents

    List PagerDuty incidents with optional filters and pagination.

    6 fields

  • Get Incident

    Retrieve a PagerDuty incident by ID.

    1 field

  • Acknowledge Incident

    Acknowledge an existing PagerDuty incident.

    2 fields

  • Resolve Incident

    Resolve an existing PagerDuty incident.

    3 fields

  • Custom API Call

    Make a custom API call to PagerDuty REST API v2. Authorization, Accept, and Content-Type headers are injected automatically. For write endpoints that require a From header, add it manually in the headers field.

    10 fields

Use PagerDuty in a flow

Connect PagerDuty once and every trigger and action above is yours to drop into the builder, alongside 770+ other apps. Free to start, on our cloud or your own servers.

PagerDuty, answered.

Yes. Activepieces is open source and free to start, and the PagerDuty piece is included on every plan, from the free cloud tier to any self-hosted deployment.

Add the PagerDuty piece to a flow, then authenticate with API key. Once connected, its 3 triggers and 6 actions are available anywhere in the builder.

"New Incident" can start a flow that runs "Create Incident", and you can chain PagerDuty together with any of 770+ other apps and AI steps in between.

Yes. Activepieces is fully self-hostable, so you can run the PagerDuty piece on your own infrastructure with your connections and your data staying in your environment.

Yes. Every piece you connect can be exposed over one Activepieces MCP server, so Claude, Cursor, Windsurf or any MCP client can call PagerDuty actions as tools.