PagerDuty integration

What it does

The PagerDuty integration lets you orchestrate incidents, services, and on-call signal inside any workflow you build for your clients. Connect a PagerDuty account once, then trigger new incidents from upstream events, react to live incident lifecycle changes (triggered, acknowledged, resolved), and post operational notes back to incidents without writing any code.

Connect a PagerDuty account

1. In TaskJuice, open Settings → Connections and choose Add connection → PagerDuty.
2. Sign in with the PagerDuty account you (or your client) want TaskJuice to act on behalf of.
3. Review the requested scopes and approve access. The connection appears in your workspace immediately.

Scopes requested: incidents.read, incidents.write, services.read, users.read, schedules.read, teams.read. You can audit or revoke the grant any time at https://app.pagerduty.com under Integrations → App Registrations or in your user profile's connected applications section.

Triggers

• pagerduty/incident-triggered. Fires when a PagerDuty incident transitions to triggered.
• pagerduty/incident-acknowledged. Fires when a responder acknowledges an incident.
• pagerduty/incident-resolved. Fires when an incident is resolved.

Every trigger verifies the inbound POST with HMAC-SHA256 over the raw request body using the secret generated for the PagerDuty Webhook v3 subscription. The signature arrives base64-encoded in the X-PagerDuty-Signature header with a v1= prefix; multiple signatures may be present during secret rotation. Configure each subscription in PagerDuty under Integrations → Generic Webhooks (v3) and point it at the trigger's incoming webhook URL.

Actions

• pagerduty/create-incident. Trigger a new incident on a service with a title, urgency, and details body.
• pagerduty/get-incident. Look up an incident by ID.
• pagerduty/update-incident. Acknowledge, resolve, retitle, or change the urgency of an incident.
• pagerduty/create-incident-note. Post a note onto an incident timeline.
• pagerduty/list-incidents. List incidents filtered by status, service, urgency, or time range, paginated by offset and limit.
• pagerduty/list-services. List the services available on the connected account, paginated by offset and limit.

Known limitations

• Every write action requires a From header carrying the email of a valid PagerDuty user; TaskJuice surfaces this as a required input on each action and validates it server-side before dispatch.
• Rate limits follow PagerDuty's published per-token caps documented at https://developer.pagerduty.com/docs/rest-api-v2/rate-limiting/. TaskJuice retries on 429 responses honoring the Retry-After header where PagerDuty returns one.
• Webhook subscription validation (the one-time POST PagerDuty sends to confirm the URL) must be enabled in the PagerDuty Generic Webhooks UI; once verified, all runtime deliveries are authenticated by the HMAC recipe.
• Pagination uses PagerDuty's offset and limit parameters; the maximum limit per request is 100. The runtime advances until the response sets more: false.