AppsPricingBlogTry it
PagerDuty logo
Pipedrive logo

Connect PagerDuty to Pipedrive

Use 2 documented PagerDuty triggers to run 24 documented Pipedrive actions.

2 source triggers
24 target actions
Reverse direction supported

Why Connect PagerDuty & Pipedrive?

Start with a PagerDuty event

Choose from 2 documented triggers, including New On-Call Rotation, New or Updated Incident.

Run a Pipedrive action

Send the event into one of 24 documented actions, such as Add Activity, Add Deal, Add Labels.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

PagerDuty logo

PagerDuty

Triggers (2)

New On-Call Rotation

Emit new event each time a new user rotates onto an on-call rotation

polling
New or Updated Incident

Emit new event each time an incident is created or updated

polling

Actions (24)

Acknowledge Incident

**Deprecated** — use **Update Incident** instead. Acknowledge an incident. See the documentation

Add Note to Incident

Add a text note to an incident. Notes are visible in the incident timeline and useful for documenting investigation steps, resolution details, or handoff notes. Use **List Incidents** or **Get Incident** to find the incident ID. See the documentation

Create Incident

Trigger a new incident on a PagerDuty service. Use **List Services** to find a service ID and **List Escalation Policies** to find a policy ID. Use **List Priorities** to find priority IDs. Set incidentKey to a stable value derived from the alert source (e.g. a hash of title + service ID) to prevent duplicate incidents on retry — PagerDuty deduplicates open incidents with the same key on the same service. See the documentation

Create Schedule Override

Override a schedule layer to assign a specific user for a time window. Use **List Schedules** to find a schedule ID and **List Users** to find the user ID. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. Always include the UTC offset — do not assume UTC; using the wrong offset will place the override in the wrong time slot. See the documentation

Create Service

Create a new PagerDuty service. A service represents a system or application that generates incidents. Use **List Escalation Policies** to find a valid escalation policy ID (required). Set autoResolveTimeout to 0 to disable auto-resolve. Set acknowledgementTimeout to 0 to disable re-triggering after acknowledgment. See the documentation

Find Oncall User

Find the user on call for a specific schedule. See the documentation

Get Event Orchestration for Service

Get the active event orchestration routing rules configured for a service. Event orchestration routes incoming events to the right responders based on conditions. Use **List Services** to discover service IDs. See the documentation

Get Incident

Get full details for a single incident by ID, including its current status, urgency, assignments, and html_url. Use **List Incidents** to find the incident ID. See the documentation

Get Service Analytics

Get incident volume and MTTR (mean time to resolve) metrics for one or more services over a time range. Use **List Services** to discover service IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. See the documentation

List Escalation Policies

List escalation policies in the PagerDuty account. Supports both exact name match (name) and substring search (query), plus team filtering. Use policy IDs with **Create Incident**, **Create Service**, and **Update Escalation Policy**. See the documentation

List Escalation Policy ID Options

Retrieves available options for the Escalation Policy ID field.

List Incident Change Events

List change events (deployments, config changes) correlated to an incident. Change events show what changed in your systems around the time the incident was triggered. Use **List Incidents** or **Get Incident** to find the incident ID. See the documentation

List Incident Workflows

List available incident automation workflows. Use workflow IDs with **Start Incident Workflow** to run automation on an active incident. Requires Business+ plan — accounts without this plan will receive empty results or a 402 error. See the documentation

List Incidents

List and filter incidents by status, urgency, service, or team. Default statuses are triggered and acknowledged (open incidents). Use **List Services** to discover service IDs and **List Teams** for team IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. See the documentation

List Log Entries

List log entries (the audit trail of actions taken on an incident or across the account). When incidentId is provided, scopes results to that incident's log entries. Otherwise returns account-wide log entries. Use **List Incidents** or **Get Incident** to find incident IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. Set isOverview: true to get only the most recent action per incident. See the documentation

List On-Call Schedule ID Options

Retrieves available options for the On-Call Schedule ID field.

List On-Calls

List on-call entries — who is on call right now or during a given time window. Filterable by schedule IDs or escalation policy IDs. Use **List Schedules** to discover schedule IDs and **List Escalation Policies** to discover policy IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. Set earliest: true to get one on-call entry per unique (schedule, escalation policy, escalation level) combination. See the documentation

List Priorities

List the priority levels configured for this PagerDuty account. Returns priority IDs and names (e.g. P1, P2, critical) useful for **Create Incident** and **Update Incident**. See the documentation

List Schedules

List on-call schedules in the PagerDuty account, optionally filtered by name. Returns schedule IDs and names useful for **List On-Calls** and **Create Schedule Override**. See the documentation

List Service ID Options

Retrieves available options for the Service ID field.

List Services

List services, optionally filtered by team or searched by name. Returns service IDs, names, status, and html_url. Use **List Teams** to discover team IDs for filtering. See the documentation

List Status Page Posts

List posts on a PagerDuty status page. Use **List Status Pages** to discover status page IDs. Set activeOnly: true to filter to currently active posts (client-side filter). Requires Business+ plan — accounts without this plan will receive empty results or a 402 error. See the documentation

List Status Pages

List configured PagerDuty status pages. Use status page IDs with **List Status Page Posts** to retrieve posts on a specific page. Requires Business+ plan — accounts without this plan will receive empty results or a 402 error. See the documentation

List Teams

List teams in the PagerDuty account, optionally filtered by name. Returns team IDs and names useful for filtering incidents, users, and services. See the documentation

Pipedrive logo

Pipedrive

Triggers (6)

Deal Updated (Instant)

Emit new event when a deal is updated.

webhook
Lead Updated (Instant)

Emit new event when a lead is updated.

webhook
New Deal (Instant)

Emit new event when a new deal is created.

webhook
New Event (Instant)

Emit new event when a new webhook event is received. See the documentation

webhook
New Person (Instant)

Emit new event when a new person is created.

webhook
Person Updated (Instant)

Emit new event when a person is updated.

webhook

Actions (24)

Add Activity

Adds a new activity. Includes more_activities_scheduled_in_context property in response's additional_data which indicates whether there are more undone activities scheduled with the same deal, person or organization (depending on the supplied data). See the Pipedrive API docs for Activities here. For info on adding an activity in Pipedrive

Add Deal

Adds a new deal. See the Pipedrive API docs for Deals here

Add Labels

Adds labels to a lead, person, deal, or organization in Pipedrive. See the documentation

Add Lead

Create a new lead in Pipedrive. See the documentation

Add Note

Adds a new note. For info on adding an note in Pipedrive

Add Organization

Adds a new organization. See the Pipedrive API docs for Organizations here

Add Person

Adds a new person. See the Pipedrive API docs for People here

Get All Leads

Get all leads from Pipedrive. See the documentation

Get Deal

Get a deal by its ID. See the documentation

Get Lead by ID

Get a lead by its ID. See the documentation

Get person details

Get details of a person by their ID. See the documentation

List Deals

List deals in your Pipedrive account. See the documentation

List Lead Label IDs Options

Retrieves available options for the Lead Label IDs field.

List Organization Label IDs Options

Retrieves available options for the Organization Label IDs field.

List Person Label IDs Options

Retrieves available options for the Person Label IDs field.

List User ID Options

Retrieves available options for the User ID field.

Merge Deals

Merge two deals in Pipedrive. See the documentation

Merge Persons

Merge two persons in Pipedrive. See the documentation

Remove Duplicate Notes

Remove duplicate notes from an object in Pipedrive. See the documentation for getting notes and deleting notes

Remove Labels

Removes one or more specific labels from a lead, person, deal, or organization in Pipedrive, leaving all other labels intact. See the documentation

Search Leads

Search for leads by name or email. See the documentation

Search Notes

Search for notes in Pipedrive. See the documentation

Search persons

Searches all Persons by name, email, phone, notes and/or custom fields. This endpoint is a wrapper of /v1/itemSearch with a narrower OAuth scope. Found Persons can be filtered by Organization ID. See the Pipedrive API docs here

Update Deal

Updates the properties of a deal. See the Pipedrive API docs for Deals here

Integration Features

2 documented PagerDuty triggers
24 documented Pipedrive actions
Configurable field mapping
Conditional workflow steps
Execution monitoring
A supported Pipedrive to PagerDuty direction

Capability Examples

PagerDuty trigger → Pipedrive action

Catalog example
PagerDutyPagerDuty

New On-Call Rotation

PipedrivePipedrive

Add Activity

Pipedrive trigger → PagerDuty action

Reverse direction
PipedrivePipedrive

Deal Updated (Instant)

PagerDutyPagerDuty

Acknowledge Incident

How It Works

1

Connect Apps

Authenticate your PagerDuty and Pipedrive accounts

2

Choose a Trigger

Select a documented PagerDuty event

3

Choose an Action

Select the documented Pipedrive operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Trigger-driven Workflows

Start the supported direction from one of 2 documented PagerDuty triggers.

Automated Actions

Run one of 24 documented Pipedrive actions after the selected trigger fires.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Select a documented trigger, choose a target action, and map the fields required by the workflow.

Field Mapping

Map the fields exposed by the selected trigger and action, then review the required provider inputs.

Execution Review

Test the workflow and review provider responses before relying on it in production.

Pipedrive logoPagerDuty logo

Reverse Integration Available

Also connect Pipedrive to PagerDuty for bidirectional automation

View Integration
PagerDuty logo

All PagerDuty Integrations

Explore all available PagerDuty connections

View All Integrations
Pipedrive logo

All Pipedrive Integrations

Explore all available Pipedrive connections

View All Integrations

Ready to Connect PagerDuty & Pipedrive?

Build this supported workflow in Mazaal AI and test it with your own provider accounts.

Get Started Free