Skip to content
Developer tools

Connect PagerDuty to any app with two-way sync.

Two-way sync PagerDuty across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes
Setup guide: how Stacksync connects to PagerDuty

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Object catalog

What Stacksync syncs in PagerDuty.

These objects sync between PagerDuty and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where PagerDuty exposes them.

Incidents
Core records with status of triggered, acknowledged, or resolved plus urgency and assignments; created, updated, and resolved two-way, with V3 webhooks firing on each transition.
Services
Technical services that group incidents and hold integration keys; read and written two-way, with service.created, service.updated, and service.deleted webhook events.
Users
Responders with contact methods and notification rules; provisioned and updated two-way to keep the on-call roster aligned with an HRIS or identity provider.
Teams
Groupings of users, services, and escalation policies; synced two-way so membership mirrors org structure from an IdP or HRIS.
Schedules
On-call rotations built from layers and overrides; read and written so calendar or workforce tools can drive who is on call.
Escalation Policies
Ordered rules routing incidents to users and schedules; read and written two-way to codify paging logic from a source of truth.
On-Calls
Computed view of who is on call now, derived from schedules and escalation policies; read-only, ideal for pushing current responders into other systems.
Notes and Log Entries
Notes are writable to append context to an incident; log entries are a read-only record of every action taken on that incident.
API surface

How Stacksync connects to PagerDuty.

The connector runs on PagerDuty's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
REST API v2 (plus Events API v2 for inbound alerts)
Authentication
REST API token via the Authorization: Token header (account-level for full access or user-level scoped to the user's permissions), or OAuth 2.0 (Authorization Code / PKCE); the Events API v2 uses a per-service routing (integration) key
Change detection
V3 webhook subscriptions push incident.* and service.* events (triggered, acknowledged, escalated, resolved, created, updated); list endpoints also support polling with updated_at and since/until windows
Rate limits
REST API allows 960 requests per minute per token and returns HTTP 429 when exceeded; the Events API is rate-limited separately per integration key.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
PagerDuty connector documentation
What ships with PagerDuty

Connect PagerDuty for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every connection.

Real-time

Two-way sync

Changes in PagerDuty instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever PagerDuty data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single PagerDuty record.

Observability

Monitoring

Track your PagerDuty sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the PagerDuty connector.

PagerDuty is the system of engagement for incident response and on-call management, owned by SRE, DevOps, and ITOps teams. It holds the operational graph — Services, Escalation Policies, Schedules, Teams, and Users — plus the live Incident record and its timeline. Because it decides who gets paged and tracks every acknowledgment and resolution, it is both the routing brain for production alerts and the system of record for on-call coverage and incident history that reliability and IT leaders report on.

  • SRE / on-call engineers
  • DevOps / platform engineering
  • IT operations (ITOps)
  • Incident management / ITSM owners
  • PagerDuty admins

  1. Provision and deactivate Users and Team memberships two-way from an HRIS or identity provider so the on-call roster matches the current org.

  2. Stream Incidents into a Postgres or Snowflake warehouse in real time via V3 webhooks to report MTTA, MTTR, and per-team on-call load.

  3. Write Schedules and Escalation Policies from a workforce tool or source-of-truth spreadsheet so rotations and overrides stay consistent across teams.

  4. Mirror Services and their integration keys with a CMDB or service catalog so ownership and tier metadata stay aligned in both directions.

  5. Push current On-Calls into Slack, a status page, or an internal directory so everyone sees who is responsible right now.

  6. Provision Users and Team membership two-way between an HRIS or Okta and PagerDuty so joiners, movers, and leavers automatically gain or lose on-call access and contact methods without manual admin work.

All PagerDuty integrations

Pick the system you need to keep in sync with PagerDuty. Each page covers the sync setup, field mapping, and common workflows for that pair.

Database · 50

Data warehouse · 28

Business productivity · 37

How it works

Set up PagerDuty in minutes, without APIs.

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate PagerDuty with its native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    PagerDuty connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the PagerDuty objects to sync — Stacksync auto-detects the schema, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · PagerDuty
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    PagerDuty database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

PagerDuty connector FAQ

What can I sync with the PagerDuty connector?

PagerDuty's core objects — Incidents, Services, Users, Teams and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to PagerDuty?

Via REST API v2 (plus Events API v2 for inbound alerts), authenticated with REST API token via the Authorization: Token header (account-level for full access or user-level scoped to the user's permissions), or OAuth 2.0 (Authorization Code / PKCE); the Events API v2 uses a per-service routing (integration) key. Changes are detected as follows — v3 webhook subscriptions push incident.* and service.* events (triggered, acknowledged, escalated, resolved, created, updated); list endpoints also support polling with updated_at and since/until windows. Stacksync manages rate limits, retries, and schema changes automatically.

Is the PagerDuty connector two-way?

Yes. Changes made in PagerDuty propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a PagerDuty integration take to set up?

Most PagerDuty integrations go live in minutes: authenticate PagerDuty and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is PagerDuty data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. PagerDuty data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own