PagerDuty

PagerDuty + Konnectify

PagerDuty Integration with Konnectify

Connect PagerDuty to Konnectify to automate incident management, service updates, on-call schedules, escalations, notes, and support workflows across your DevOps and support stack.

Incidents Services Tasks Responders Workflows Event Orchestrations Schedules Overrides Vendors Users 30 Triggers 36 Actions

ON THIS PAGE

→ What is PagerDuty? → API & authentication → How to connect → Triggers (30) → Actions (36) → Popular automations → FAQ

What is PagerDuty?

PagerDuty is an incident management platform that helps teams detect, triage, escalate, and resolve operational issues with reliable notifications, automatic escalations, and on-call scheduling.

With Konnectify, you can connect PagerDuty to support desks, collaboration tools, monitoring systems, CRMs, databases, and internal apps so incident activity automatically triggers the right follow-up actions across your organization.

New to PagerDuty?

Create a PagerDuty account to manage on-call response and incident operations.

Visit PagerDuty →

New to Konnectify?

Build automated workflows between PagerDuty and the rest of your business apps.

What you can automate

• Create and update PagerDuty incidents from external events

• Trigger workflows when incidents are acknowledged, resolved, escalated, or reopened

• Sync service creation, updates, deletions, and custom field changes

• Add, update, list, and delete incident notes automatically

• Manage schedules, schedule overrides, users, and vendors

• Build automation around event orchestrations, responders, tasks, and incident workflows

API & Authentication

Authentication method: API Key authentication

This integration uses a PagerDuty REST API key. When you create a PagerDuty connection in Konnectify, enter the API key in the API Key field. Konnectify uses the key to securely call PagerDuty APIs for the workflows you configure.

In PagerDuty, REST API keys are typically created by an account owner or administrator from the integrations or API access settings. Use a key with permissions appropriate for the objects your workflows need to read or update.

API capabilities used by this connector

Incident lifecycle operations: create, update, merge, snooze, retrieve, and list incidents.
Incident collaboration: create, update, list, and delete notes; create status updates; manage business service impact.
Incident intelligence: retrieve outlier, past, and related incident data.
Service and custom field event handling through PagerDuty webhooks.
Event orchestration management: create, update, get, list, and delete event orchestrations.
Schedule and override management, plus user and vendor lookup operations.

Important: PagerDuty API access, webhook availability, incident custom fields, event orchestrations, and related incident intelligence may depend on your PagerDuty plan, add-ons, role permissions, and API rate limits.

For endpoint details, refer to the official PagerDuty API documentation.

How to connect PagerDuty to Konnectify

Prerequisites

An active PagerDuty account with permission to create or use a REST API key.
A Konnectify account with access to create workflows and app connections.
Required PagerDuty object IDs such as incident IDs, service IDs, schedule IDs, override IDs, user IDs, or orchestration IDs for the actions you plan to use.
For note, snooze, and status update actions, a valid PagerDuty user email for the required From header.

Add PagerDuty to a Workflow

Open Konnectify and create a new workflow.
Choose PagerDuty as the trigger app or action app.
Select the specific trigger or action that matches your automation goal.

Authorize via API Key authentication

Click Connect or Add new connection.
Paste your PagerDuty REST API key into the API Key field.
Save the connection and allow Konnectify to validate it.

Configure the Trigger or Action

Map required fields such as incident ID, service ID, schedule ID, user ID, summary, status, urgency, or time range.
Use data from previous steps to dynamically populate PagerDuty fields.
For webhook triggers, ensure the workflow is enabled so Konnectify can receive PagerDuty events.

Tip: Some PagerDuty actions require exact object IDs and valid ISO date/time values. Confirm mapped IDs and time zones before testing schedule or override workflows.

Test the Workflow

Run a test from Konnectify.
Review the sample payload or action response.
Verify the result in PagerDuty before activating the workflow.

Activate the Workflow

Turn on the workflow after a successful test.
Monitor execution history in Konnectify for successful runs and any API errors.
Adjust field mappings or filters as your incident process evolves.

Triggers 30

PagerDuty includes 30 webhook triggers in Konnectify. Each trigger fires from a PagerDuty event and processes one event at a time.

Incidents 13 triggers

Incident Acknowledged

Fires whenever an incident is acknowledged by a user in PagerDuty.

Incident Resolved

Fires whenever an active incident is resolved in PagerDuty.

Incident Delegated

Fires whenever an incident is delegated to another user in PagerDuty.

Incident Escalated

Fires whenever an incident is escalated in PagerDuty.

Incident Reassigned

Fires whenever an incident is reassigned in PagerDuty.

Incident Reopened

Fires whenever a previously resolved incident is reopened in PagerDuty.

Incident Priority Updated

Fires whenever an incident's priority level is changed in PagerDuty.

Incident Type Changed

Fires whenever an incident's type is changed in PagerDuty.

Incident Service Updated

Fires whenever an incident is moved to a different service in PagerDuty.

Incident Unacknowledged

Fires whenever an incident's status changes back to unacknowledged in PagerDuty.

Incident Triggered

Fires whenever a new incident is triggered in PagerDuty.

Incident Conference Bridge Updated

Fires whenever conference bridge details are added or updated on an incident in PagerDuty.

Incident Annotated

Fires whenever a user adds a note (annotation) to an incident in PagerDuty.

Services4 triggers

Service Created

Fires whenever a new service is created in PagerDuty.

Service Updated

Fires whenever an existing service is updated in PagerDuty.

Service Deleted

Fires whenever a service is deleted from PagerDuty.

Service Custom Field Values Updated

Fires whenever custom field values associated with a service are updated in PagerDuty.

Incident Tasks3 triggers

Incident Task Completed

Fires whenever a task associated with an incident is marked as completed in PagerDuty.

Incident Task Created

Fires whenever a new task is created and associated with an incident in PagerDuty.

Incident Task Updated

Fires whenever details of a task associated with an incident are updated in PagerDuty.

Incident Responders2 triggers

Incident Responder Added

Fires whenever a responder is added to an incident in PagerDuty.

Incident Responder Replied

Fires whenever a responder replies to an incident request in PagerDuty.

Incident Automation Actions3 triggers

Incident Action Invocation Created

Fires whenever an automation action invocation is created for an incident in PagerDuty.

Incident Action Invocation Terminated

Fires whenever an automation action invocation for an incident is terminated in PagerDuty.

Incident Action Invocation Updated

Fires whenever an automation action invocation for an incident is updated in PagerDuty.

Incident Workflows2 triggers

Incident Workflow Started

Fires whenever an incident workflow instance is started in PagerDuty.

Incident Workflow Completed

Fires whenever an incident workflow instance completes its execution in PagerDuty.

Incident Fields, Roles & Status Updates3 triggers

Incident Custom Field Values Updated

Fires whenever custom field values associated with an incident are updated in PagerDuty.

Incident Role Assigned

Fires whenever a user is assigned a specific role (like Commander) on an incident in PagerDuty.

Incident Status Update Published

Fires whenever a status update is published for an incident in PagerDuty.

Actions 36

Use PagerDuty actions to create, update, retrieve, and manage incidents, schedules, overrides, event orchestrations, users, vendors, and related operational data.

Incidents6 actions

Create Incident

Creates a new incident synchronously on a specified service. You can map priorities, escalation policies, and urgency.

Update Incident

Updates parameters of an existing incident, such as status, priority, urgency, or assigned service.

Get Incident by ID

Fetches detailed information about a PagerDuty incident using its unique ID.

List Incidents

Returns a paginated list of incidents based on specified filtering parameters.

Snooze Incident

Snoozes a PagerDuty incident for a given number of seconds. The user's email is required for the 'From' header.

Merge Incidents

Merges a list of source incidents into a target incident. After the merge, the target incident will contain the source incidents' alerts, and the source incidents will be resolved.

Incident Notes4 actions

Create a Note on an Incident

Creates a new note on the specified PagerDuty incident. The user's email is required for the 'From' header.

Update Incident Note

Modifies the content of an existing note on a PagerDuty incident. The user's email is required for the 'From' header.

List Incident Notes

Fetches a complete list of notes added to a specified PagerDuty incident.

Delete Incident Note

Deletes an existing note on a PagerDuty incident. The user's email is required for the 'From' header.

Incident Insights3 actions

Get Outlier Incident

Fetches outlier information associated with a given incident ID, determining if it represents a rare or frequent occurrence.

Get Past Incidents

Fetches past incidents that are similar or related to the given incident ID.

Get Related Incidents

Fetches incidents related to a given incident based on machine learning, service dependencies, or other relational metadata.

Incident Fields & Impact4 actions

Update Custom Field Values

Updates the custom field values of a specific incident based on its assigned incident type.

Create Status Update

Creates a new status update for an active PagerDuty incident. The user's email is required for the 'From' header.

List Impacted Business Services

Fetches a list of all business services that are currently impacted by the specified PagerDuty incident.

Change Incident Impact

Updates whether a specific business service is currently impacted by an active incident.

Event Orchestrations5 actions

Create Event Orchestration

Creates a new event orchestration, optionally assigning it to a specific team.

Update Event Orchestration

Modifies the details of a specific event orchestration in PagerDuty.

Get Event Orchestration

Fetches comprehensive details for a specific event orchestration in PagerDuty using its ID.

List Event Orchestrations

Returns a paginated list of event orchestrations.

Delete Event Orchestration

Deletes an existing event orchestration from PagerDuty.

Schedules5 actions

Create Schedule

Creates a new schedule in PagerDuty with a specified time zone and optional team associations.

Update Schedule

Updates an existing PagerDuty schedule. Only provide the fields you wish to change.

Get Schedule

Fetches comprehensive details for a specific PagerDuty schedule.

List Schedules

Returns a paginated list of schedules based on search queries and team filters.

Delete Schedule

Deletes an existing schedule from PagerDuty.

Schedule Overrides5 actions

Create Overrides

Create schedule overrides for a specific schedule. You can map a single override via the fields, or provide a stringified JSON array to create multiple overrides at once.

Update Override

Update the start time, end time, or the overriding user for a specific schedule override.

Get Override by ID

Fetches the full details of a specific schedule override by its ID.

List Overrides

Retrieves a list of schedule overrides within a specified time range.

Delete Override

Removes a specific schedule override from a PagerDuty schedule.

Vendors2 actions

List Vendors

Returns a paginated list of PagerDuty vendors, which represent integration partners.

Get Vendor by ID

Fetches the full details of a specific PagerDuty vendor (integration partner) by its ID.

Users2 actions

List Users

Returns a paginated list of users from your PagerDuty account.

Get User by ID

Fetches the full details of a specific PagerDuty user by their ID.

Popular automations

Here are common PagerDuty workflow ideas you can build with Konnectify.

Create follow-up documentation for new incidents

When a new PagerDuty incident is triggered, automatically add an initial note and fetch related incidents for context.

Incident Triggered→Create a Note on an Incident→Get Related Incidents

Escalation-aware incident updates

When an incident escalates, update the incident priority or urgency and publish a status update to keep stakeholders informed.

Incident Escalated→Update Incident→Create Status Update

Maintain on-call schedule overrides

Use data from HR, calendars, or service desks to create or update PagerDuty schedule overrides automatically.

Service Updated→List Schedules→Create Overrides

Reduce noise from related incidents

When an incident is reopened or duplicated, retrieve similar incidents and merge source incidents into a target incident.

Incident Reopened→Get Past Incidents→Merge Incidents

FAQ

How does PagerDuty authentication work in Konnectify?

PagerDuty connects to Konnectify using API Key authentication. Create or copy a PagerDuty REST API key from your PagerDuty account, then paste it into the API Key field when creating the connection in Konnectify.

Which PagerDuty plans are supported?

Konnectify can connect to PagerDuty accounts that allow REST API access and webhooks. Specific capabilities such as incident custom fields, event orchestrations, related incidents, and business service impact may require particular PagerDuty plans, roles, or add-ons.

How do PagerDuty triggers work?

All PagerDuty triggers in this connector are webhook-based. PagerDuty sends matching events to Konnectify, and Konnectify routes each event to the correct workflow trigger based on the PagerDuty event type, such as incident.triggered, incident.resolved, or service.updated.

How can I prevent duplicate incidents?

This connector does not include a dedicated upsert action. To reduce duplicates, add a lookup step such as List Incidents or Get Incident by ID before Create Incident, then use workflow conditions to create a new incident only when no matching active incident exists. For duplicate incident cleanup, use Merge Incidents.

How does Konnectify handle PagerDuty rate limits?

PagerDuty enforces API rate limits. If a workflow receives a rate-limit response, review the run history in Konnectify and adjust workflow frequency, filters, branching, or batching logic where appropriate. High-volume incident environments should avoid unnecessary list calls and use targeted IDs whenever possible.

Can I connect multiple PagerDuty accounts?

Yes. You can create separate PagerDuty connections in Konnectify using different API keys. Give each connection a clear name, such as Production PagerDuty or Staging PagerDuty, so workflow builders can select the correct account.

Why do some incident actions require a user email for the From header?

PagerDuty requires a valid user context for certain incident operations, including creating or updating notes, deleting notes, snoozing incidents, and creating status updates. Map the email address of a PagerDuty user who has permission to perform the operation.

Ready to automate your PagerDuty workflows?

Connect PagerDuty to Konnectify and automate incident response, service operations, schedules, and support handoffs.

Get started free →