Skip to content
Data warehouse ⇄ Developer tools

MotherDuck to PagerDuty integration — real-time, two-way sync

Keep MotherDuck and PagerDuty in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

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
Why teams connect MotherDuck and PagerDuty

Close the gap between analytics and operations: MotherDuck holds the record while PagerDuty runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.

MotherDuck is the central store where teams keep Schemas, Tables, Views, Database Shares for reporting and analysis; PagerDuty runs the operational side of engineering work — tracking issues, moving messages and events, watching systems, and managing users and access. The two overlap wherever the same operational data matters to both: the Notes and Log Entries, Incidents, Services, Users produced in PagerDuty are exactly what analysts want to measure in MotherDuck, and the curated rows in MotherDuck are what should drive the next action in PagerDuty. When that overlap is bridged by nightly ETL or hand-written scripts, dashboards lag a day behind reality and the tools that should react to warehouse signals never see them.

Stacksync syncs Schemas, Tables, Views, Database Shares in MotherDuck with Notes and Log Entries, Incidents, Services, Users in PagerDuty field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync matches records on a stable external key, keeps every copy consistent, and resolves conflicts by rules you set — so analytics and operations work from the same current data instead of two drifting copies.

Common use cases

  • 01 Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
  • 02 Sync modeled MotherDuck tables outward to operational tools for activation
  • 03 Provision and deactivate Users and Team memberships two-way from an HRIS or identity provider so the on-call roster matches the current org.
  • 04 Write Schedules and Escalation Policies from a workforce tool or source-of-truth spreadsheet so rotations and overrides stay consistent across teams.

Common sync patterns

No batch jobs to babysit

New and changed records move field by field the moment they change, replacing scheduled ETL and one-off scripts that fail quietly and leave stale rows behind.

One shared record, kept consistent

Where both systems track the same entity, a change on either side propagates to the other, ending the manual reconciliation between the operational copy and the warehouse copy.

Keep user and access records aligned

Where PagerDuty manages users, directory, or access data, those records stay current in MotherDuck — and can be provisioned back from it — so ownership and permissions match across both.

What you can sync between MotherDuck and PagerDuty

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

MotherDuck objects PagerDuty objects How this pairing syncs
Schemas Namespaces within a database used to organize synced tables. Escalation Policies Ordered rules routing incidents to users and schedules; read and written two-way to codify paging logic from a source of truth. Schemas is specific to MotherDuck and Escalation Policies to PagerDuty — each maps to any object or custom field on the other side.
Tables The main landing target for synced records and source for analysis. 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. Tables is specific to MotherDuck and On-Calls to PagerDuty — each maps to any object or custom field on the other side.
Views Modeled projections used as outbound sync sources. 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. Views is specific to MotherDuck and Notes and Log Entries to PagerDuty — each maps to any object or custom field on the other side.
Database Shares Read-only copies of a database shared with other users or teams. 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. Database Shares is specific to MotherDuck and Incidents to PagerDuty — each maps to any object or custom field on the other side.
Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. 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. Attached Local DuckDB Databases is specific to MotherDuck and Services to PagerDuty — each maps to any object or custom field on the other side.
Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. 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. Databases is specific to MotherDuck and Users to PagerDuty — each maps to any object or custom field on the other side.

How changes propagate between MotherDuck and PagerDuty

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

MotherDuck PagerDuty Interval-based propagation

DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

DeliveryEach detected change is written to PagerDuty through its API, with automatic retries and rate-limit backoff.

PagerDuty MotherDuck Sub-second propagation

DetectionPagerDuty notifies Stacksync of record changes through webhook events. V3 webhook subscriptions push incident.* and service.* events (triggered, acknowledged, escalated, resolved, created, updated).

DeliveryEach detected change is applied to MotherDuck as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
  • PagerDuty: 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.
What ships with MotherDuck ⇄ PagerDuty

Connect MotherDuck and PagerDuty for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in MotherDuck or PagerDuty instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever MotherDuck or 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 MotherDuck or PagerDuty record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between MotherDuck and PagerDuty.

How the MotherDuck and PagerDuty connectors work

MotherDuck

Integration surface
SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
Authentication
Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck setup guide

PagerDuty

Integration surface
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
Capabilities
read · write · webhooks
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.
PagerDuty setup guide
How it works

How to connect MotherDuck to PagerDuty — three steps, no code

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 MotherDuck and PagerDuty with each platform's 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
    MotherDuck connected
    PagerDuty connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the MotherDuck and PagerDuty objects to sync — Stacksync auto-detects both schemas, 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 · MotherDuck ⇄ 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
    MotherDuck PagerDuty
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

MotherDuck and PagerDuty integration FAQ

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

Related integrations

Every pair below is a real-time, two-way sync. Search all 328 integrations available for MotherDuck and PagerDuty.

Popular · 8 of 328
All MotherDuck integrations All PagerDuty integrations Browse all integrations
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