Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

PagerDuty

Incident management workflows for PagerDuty REST API v2.

CategoryDeveloper Tools
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect PagerDuty with Flows360

Incident management workflows for PagerDuty REST API v2.

Use the PagerDuty connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 3 triggers.

Available actions

  • Create Incident
  • List Incidents
  • Get Incident
  • Acknowledge Incident
  • Resolve Incident
  • Custom API Call

Available triggers

  • New Incident
  • Incident Resolved
  • Incident Acknowledged

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: PagerDuty
  • Package: @activepieces/piece-pagerduty@0.2.0
  • Exact artifact digest: sha256:bc36e1097c60005ee36207aefacb8e909ad1b2e02dc7882ff0f4c51aa5f1a9a8
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Incident (create_incident), Create a new PagerDuty incident using the REST API. Classification: read.
  • List Incidents (list_incidents), List PagerDuty incidents with optional filters and pagination. Classification: read.
  • Get Incident (get_incident), Retrieve a PagerDuty incident by ID. Classification: read.
  • Acknowledge Incident (acknowledge_incident), Acknowledge an existing PagerDuty incident. Classification: read.
  • Resolve Incident (resolve_incident), Resolve an existing PagerDuty incident. Classification: read.
  • Custom API Call (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. Classification: read.

Trigger contracts

  • New Incident, webhook.
  • Incident Resolved, webhook.
  • Incident Acknowledged, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects9
Supported actions6
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • PagerDuty API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Incident Yes No Create a new PagerDuty incident using the REST API.
List Incidents Yes No List PagerDuty incidents with optional filters and pagination.
Get Incident Yes No Retrieve a PagerDuty incident by ID.
Acknowledge Incident Yes No Acknowledge an existing PagerDuty incident.
Resolve Incident Yes No Resolve an existing PagerDuty incident.
Custom API Call Yes No 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.
New Incident Yes No webhook trigger declared by the pinned package.
Incident Resolved Yes No webhook trigger declared by the pinned package.
Incident Acknowledged Yes No webhook trigger declared by the pinned package.

Supported actions

Create Incident · Read

Create a new PagerDuty incident using the REST API.

create_incident · Risk: low · Retry: safe

Inputs

  • fromEmail · string · Required, PagerDuty REST write operations require the email address of a valid PagerDuty user on the account.
  • serviceId · string · Required, The PagerDuty service to associate with the incident.
  • title · string · Required, Incident title / summary.
  • urgency · string · Required, The urgency for the incident.
  • details · string · Optional, Additional incident body text.
  • incidentKey · string · Optional, A string that identifies the incident. Duplicate requests with the same key and open incident on the same service will be rejected (de-duplication).
  • assigneeIds · array · Optional, Comma-separated list of PagerDuty user IDs to assign the incident to. Cannot be used together with Escalation Policy ID.
  • priorityId · string · Optional, The ID of the priority to assign to this incident.
  • conferenceNumber · string · Optional, Phone number of the conference bridge.
  • conferenceUrl · string · Optional, URL for the conference bridge.
List Incidents · Read

List PagerDuty incidents with optional filters and pagination.

list_incidents · Risk: low · Retry: safe

Inputs

  • statuses · array · Optional, Optional incident status filters.
  • urgency · string · Optional, Optional urgency filter.
  • since · string · Optional, Optional start of the search window.
  • until · string · Optional, Optional end of the search window.
  • limit · number · Optional, Maximum number of incidents to return (1u2013100).
  • offset · number · Optional, Pagination offset (number of records to skip).
Get Incident · Read

Retrieve a PagerDuty incident by ID.

get_incident · Risk: low · Retry: safe

Inputs

  • incidentId · string · Required, The PagerDuty incident ID, for example PABC123.
Acknowledge Incident · Read

Acknowledge an existing PagerDuty incident.

acknowledge_incident · Risk: low · Retry: safe

Inputs

  • incidentId · string · Required, The PagerDuty incident ID, for example PABC123.
  • fromEmail · string · Required, PagerDuty REST write operations require the email address of a valid PagerDuty user on the account.
Resolve Incident · Read

Resolve an existing PagerDuty incident.

resolve_incident · Risk: low · Retry: safe

Inputs

  • incidentId · string · Required, The PagerDuty incident ID, for example PABC123.
  • fromEmail · string · Required, PagerDuty REST write operations require the email address of a valid PagerDuty user on the account.
  • resolution · string · Optional, Optional resolution note. PagerDuty adds this to the resolve log entry.
Custom API Call · Read

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.

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Incident · Webhook

Triggers when a new incident is created

Inputs

  • instruction · string
Incident Resolved · Webhook

Triggers when an incident is resolved.

Inputs

  • instruction · string
Incident Acknowledged · Webhook

Triggers when an incident is acknowledged.

Inputs

  • instruction · string

Setup

Setup

  1. Add the PagerDuty connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-pagerduty@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 3 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required PagerDuty connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-pagerduty@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com