Skip to content
Database ⇄ Developer tools

InterSystems IRIS to PagerDuty integration — real-time, two-way sync

Keep InterSystems IRIS 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 InterSystems IRIS and PagerDuty

Keep InterSystems IRIS and PagerDuty in step: the rows in your database and the Incidents, Services, Users, Teams your engineering tools track stay consistent in real time, in both directions.

InterSystems IRIS is where your application's durable data lives; PagerDuty is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.

Stacksync syncs Tables, Views, Schemas, Persistent Classes in InterSystems IRIS with Incidents, Services, Users, Teams in PagerDuty field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set, so the database and the tooling around it never drift apart.

Common use cases

  • 01 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
  • 02 Consolidate IRIS data with other databases in an analytics warehouse for cross-system reporting
  • 03 Write Schedules and Escalation Policies from a workforce tool or source-of-truth spreadsheet so rotations and overrides stay consistent across teams.
  • 04 Mirror Services and their integration keys with a CMDB or service catalog so ownership and tier metadata stay aligned in both directions.

Common sync patterns

Land tool activity as queryable rows

Records and events from PagerDuty arrive in InterSystems IRIS as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.

One integration pattern instead of per-tool API code

Read and write the synced tables in InterSystems IRIS and Stacksync keeps PagerDuty current, replacing the auth, webhooks, rate limits, and retry logic you would otherwise maintain for each tool.

React to changes on either side in near real time

Updates in PagerDuty arrive as row changes in InterSystems IRIS, and writes to InterSystems IRIS propagate to PagerDuty within seconds, so triggers, jobs, and alerts fire without polling.

What you can sync between InterSystems IRIS 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.

InterSystems IRIS objects PagerDuty objects How this pairing syncs
Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. Schedules On-call rotations built from layers and overrides; read and written so calendar or workforce tools can drive who is on call. Globals is specific to InterSystems IRIS and Schedules to PagerDuty — each maps to any object or custom field on the other side.
Namespaces Namespaces partition databases and determine the connection context for integrations. Escalation Policies Ordered rules routing incidents to users and schedules; read and written two-way to codify paging logic from a source of truth. Namespaces is specific to InterSystems IRIS and Escalation Policies to PagerDuty — each maps to any object or custom field on the other side.
Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. 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. Stored Procedures is specific to InterSystems IRIS and On-Calls to PagerDuty — each maps to any object or custom field on the other side.
Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. 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. Tables is specific to InterSystems IRIS and Notes and Log Entries to PagerDuty — each maps to any object or custom field on the other side.
Views SQL views expose curated slices of data for outbound replication. 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. Views is specific to InterSystems IRIS and Incidents to PagerDuty — each maps to any object or custom field on the other side.
Schemas Schema organization scopes which tables a sync connection can see. 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. Schemas is specific to InterSystems IRIS and Services to PagerDuty — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS 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.

InterSystems IRIS PagerDuty Interval-based propagation

DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).

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

PagerDuty InterSystems IRIS 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 InterSystems IRIS as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • InterSystems IRIS: Constrained by database resources rather than published 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 InterSystems IRIS ⇄ PagerDuty

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the InterSystems IRIS and PagerDuty connectors work

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate limits

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 InterSystems IRIS 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 InterSystems IRIS 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
    InterSystems IRIS connected
    PagerDuty connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the InterSystems IRIS 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 · InterSystems IRIS ⇄ 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
    InterSystems IRIS PagerDuty
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

InterSystems IRIS 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 346 integrations available for InterSystems IRIS and PagerDuty.

Popular · 7 of 346
All InterSystems IRIS 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