Skip to content
AI ⇄ Database

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

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

Sync the records in InterSystems IRIS into Autopilot and land its embeddings, classifications, and generated fields back on the same rows, in real time and without a pipeline to maintain.

AI systems do not hold customers or invoices the way business apps do. What they hold is derived from your data: the vectors and metadata in a vector store, or the classifications, extracted fields, and generated text a model produces over records it was given. InterSystems IRIS is where those source records actually live. The bridge between the two is the row itself, since an item in Autopilot and the record in InterSystems IRIS it describes are two halves of the same thing, and they drift the moment one is updated without the other.

Stacksync syncs Namespaces, Stored Procedures, Tables, Views in InterSystems IRIS with Smart Segments, Journeys (Triggers), Activities, Contacts in Autopilot in real time. Rows created or changed in InterSystems IRIS flow into Autopilot so inference and embedding run on current data, and the scores, labels, and generated fields Autopilot produces flow back onto the matching rows in InterSystems IRIS, mapped field by field. A change on either side appears on the other within seconds, with no extraction job or webhook plumbing to keep alive.

Because matching is by a stable identifier, every row in InterSystems IRIS stays tied to its AI-side counterpart in Autopilot. Retrieval, enrichment, and generated content always resolve back to the record they came from, so there are no orphaned vectors and no labels describing a version of a row that no longer exists.

Common use cases

  • 01 Upsert Contacts from a CRM or product database into Autopilot so new signups and profile changes flow into email and SMS journeys without manual CSV imports.
  • 02 Add contacts to a Journey from a database event or CRM stage change to start automated onboarding or nurture sequences.
  • 03 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
  • 04 Consolidate IRIS data with other databases in an analytics warehouse for cross-system reporting

Common sync patterns

Run the AI on current data

Rows created or changed in InterSystems IRIS flow into Autopilot as they happen, so embeddings, classifications, and prompts run on the latest records instead of a nightly snapshot.

Write results back onto the record

Scores, labels, extracted fields, or generated text produced in Autopilot land on the matching row in InterSystems IRIS, next to the source data your applications already query.

Keep derived data fresh as sources change

When a row in InterSystems IRIS is updated or removed, its counterpart in Autopilot is updated or removed too, so nothing in Autopilot describes a record that has since changed or gone.

What you can sync between Autopilot and InterSystems IRIS

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.

Autopilot objects InterSystems IRIS objects How this pairing syncs
Custom Fields User-defined contact properties (string, number, date, boolean); discovered so field keys map cleanly to destination columns. Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Custom Fields is specific to Autopilot and Persistent Classes to InterSystems IRIS — each maps to any object or custom field on the other side.
Smart Segments Rule-based dynamic audiences; membership is computed by Autopilot, so it is read-only over the API. Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. Smart Segments is specific to Autopilot and Globals to InterSystems IRIS — each maps to any object or custom field on the other side.
Journeys (Triggers) Automation journeys; a contact can be added to a journey via its trigger endpoint to start automated email or SMS sequences. Namespaces Namespaces partition databases and determine the connection context for integrations. Journeys (Triggers) is specific to Autopilot and Namespaces to InterSystems IRIS — each maps to any object or custom field on the other side.
Activities Per-contact activity and event history (opens, clicks, journey steps); read-only feed used for engagement reporting. Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Activities is specific to Autopilot and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side.
Contacts Core people records (email, name, custom fields, list and segment membership); upserted two-way as the primary sync object. Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Contacts is specific to Autopilot and Tables to InterSystems IRIS — each maps to any object or custom field on the other side.
Lists Static contact lists; membership is readable per list and writable by adding or removing contacts. Views SQL views expose curated slices of data for outbound replication. Lists is specific to Autopilot and Views to InterSystems IRIS — each maps to any object or custom field on the other side.

How changes propagate between Autopilot and InterSystems IRIS

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.

Autopilot InterSystems IRIS Interval-based propagation

DetectionStacksync polls Autopilot for changes on an incremental schedule, reading only records changed since the previous pass. No CDC.

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

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

Rate-limit considerations

  • Autopilot: The REST API is capped at 100 requests/minute per account; exceeding it returns HTTP 429. Enterprise plans can request a higher limit. Contact writes accept an array for bulk upsert, and list and segment reads paginate via a bookmark cursor.
  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with Autopilot ⇄ InterSystems IRIS

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Autopilot and InterSystems IRIS connectors work

Autopilot

Integration surface
REST API (Autopilot v1); Autopilot rebranded to Ortto in 2021 and the newer Ortto API co-exists with the legacy Autopilot endpoints
Authentication
Per-account API key sent in the autopilotapikey request header (generated in account settings); requests use Content-Type application/json against https://api2.autopilothq.com/v1/
Change detection
No CDC; incremental sync polls the /contacts endpoint with bookmark cursor pagination and updated timestamps. Journey webhook actions can push specific contact events, but there is no general change-subscription webhook, so polling is the reliable path.
Capabilities
read · write
Rate limits
The REST API is capped at 100 requests/minute per account; exceeding it returns HTTP 429. Enterprise plans can request a higher limit. Contact writes accept an array for bulk upsert, and list and segment reads paginate via a bookmark cursor.
Autopilot setup guide

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
How it works

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

    Choose tables

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

Autopilot and InterSystems IRIS 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 440 integrations available for Autopilot and InterSystems IRIS.

Popular · 7 of 440
All Autopilot integrations All InterSystems IRIS 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