Skip to content
Database ⇄ Analytics

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

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

Give Pendo the users, events, and records that live in InterSystems IRIS in real time, and sync the cohorts and scores Pendo computes back into InterSystems IRIS where your applications read them.

A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Pendo is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from InterSystems IRIS into Pendo usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.

Stacksync syncs Tables, Views, Schemas, Persistent Classes in InterSystems IRIS with Features / Pages / Guides (metadata), Visitors, Accounts, Feature Events in Pendo in real time and in both directions. Operational rows flow into Pendo as they change, so dashboards read current data with no pipeline to maintain, and the segments, cohorts, or scores Pendo computes flow back into InterSystems IRIS, where the applications and services that read from it get them at normal query latency. Field-level mapping, schema and type translation, and conflict resolution are handled for you.

Common use cases

  • 01 Pull NPS scores and poll responses into a database so voice-of-customer sits next to revenue, renewal, and churn signals for analysis.
  • 02 Push warehouse-computed Account attributes (plan, ARR, renewal date, health score, CSM owner) onto Pendo Accounts via the Metadata API so segments and guide targeting stay current.
  • 03 Keep reference data consistent between an IRIS-based clinical or financial application and downstream SaaS tools
  • 04 Write enriched or corrected records from SaaS apps back into IRIS tables for on-platform processing

Common sync patterns

Where Pendo builds cohorts or scores: results your services can read

Segments, cohorts, or scores computed in Pendo sync back into InterSystems IRIS, where the services that read from the database act on them at query speed without calling the analytics API.

Analytics on live operational data, minus the pipeline

The users, events, orders, and records stored in InterSystems IRIS land in Pendo as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.

One version of each user or account

A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.

What you can sync between InterSystems IRIS and Pendo

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 Pendo objects How this pairing syncs
Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Page Events Page-view events for tagged pages; read-only via the Aggregation API, used for adoption and path analysis in a warehouse. Tables is specific to InterSystems IRIS and Page Events to Pendo — each maps to any object or custom field on the other side.
Views SQL views expose curated slices of data for outbound replication. Guide Events Guide seen/advanced/dismissed and step events for in-app walkthroughs; read-only through the Aggregation API to measure onboarding flow adoption. Views is specific to InterSystems IRIS and Guide Events to Pendo — each maps to any object or custom field on the other side.
Schemas Schema organization scopes which tables a sync connection can see. Poll / NPS Responses Survey answers and NPS scores captured in-app (pollEvents / npsEvents); read-only via the Aggregation API as voice-of-customer data. Schemas is specific to InterSystems IRIS and Poll / NPS Responses to Pendo — each maps to any object or custom field on the other side.
Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Features / Pages / Guides (metadata) Definitions of tagged UI elements listed through the entity endpoints; read-only reference used to label and join the event streams. Persistent Classes is specific to InterSystems IRIS and Features / Pages / Guides (metadata) to Pendo — each maps to any object or custom field on the other side.
Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. Visitors End-user records with agent-collected and custom fields; queried through the Aggregation API and enriched with custom fields written back via the Metadata API. Globals is specific to InterSystems IRIS and Visitors to Pendo — each maps to any object or custom field on the other side.
Namespaces Namespaces partition databases and determine the connection context for integrations. Accounts Company/workspace records that roll visitors up to an account dimension; readable via Aggregation and a write target for custom fields (plan, ARR, health) via the Metadata API. Namespaces is specific to InterSystems IRIS and Accounts to Pendo — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS and Pendo

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 Pendo 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 Pendo through its API, with automatic retries and rate-limit backoff.

Pendo InterSystems IRIS Interval-based propagation

DetectionStacksync polls Pendo for changes on an incremental schedule, reading only records changed since the previous pass. Polling - reads query the Aggregation API over event-time windows.

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.
  • Pendo: Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
What ships with InterSystems IRIS ⇄ Pendo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your InterSystems IRIS ⇄ Pendo 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 Pendo.

How the InterSystems IRIS and Pendo 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

Pendo

Integration surface
Pendo Engage API (REST) on app.pendo.io (US) / app.eu.pendo.io (EU), base path /api/v1/ - Aggregation API for reads and the Metadata API for writes
Authentication
Integration key sent in the x-pendo-integration-key header, generated in Subscription Settings; keys are scoped read-only or read/write, so writes require a read/write key
Change detection
Polling - reads query the Aggregation API over event-time windows; no change-data-capture feed and no data-change webhooks. Writes go through the Metadata API on demand.
Capabilities
read · write
Rate limits
Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
How it works

How to connect InterSystems IRIS to Pendo — 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 Pendo 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
    Pendo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

InterSystems IRIS and Pendo 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 439 integrations available for InterSystems IRIS and Pendo.

Popular · 7 of 439
All InterSystems IRIS integrations All Pendo 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