Skip to content
Communications ⇄ Database

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

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

Turn the messages, calls, and events Aircall handles into live rows in InterSystems IRIS, and write back to trigger new outbound communication, with both sides in sync in seconds.

Engineers reach communications tools like Aircall through APIs, which means auth tokens, webhooks, delivery callbacks, and rate limits, all maintained forever and all shaped differently for every tool. The data those tools produce, who was contacted, what was sent, and what came back, would be simple to use if it lived in InterSystems IRIS next to everything else.

Stacksync mirrors Contacts, Calls, Users, Numbers from Aircall into Stored Procedures, Tables, Views, Schemas in InterSystems IRIS and keeps both sides in sync in real time. Communication activity lands in the database as ordinary rows you can query and join, and rows your code writes, such as a queued outbound message or an updated contact, flow back into Aircall so the tool and the database never disagree.

There is no webhook endpoint to host, no rate limit to babysit, and no nightly export that leaves your services reading yesterday's activity.

Common use cases

  • 01 Log every Call with its recording URL, tags, comments, and metadata into Postgres or a warehouse for talk-time and call-outcome reporting beside CRM pipeline data.
  • 02 Provision and deprovision Users and Team membership from an HR system or IdP so the agent roster, seats, and routing groups 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

Communication history as database rows

Every message, call, or event Aircall records becomes rows in InterSystems IRIS, ready to query, join with your own data, and report on without touching the vendor API.

Trigger outbound communication from the database

Write a row to a synced table in InterSystems IRIS and Stacksync propagates it into Aircall, so your code sends the message, places the call, or schedules the meeting without integration glue.

One contact list across both

Recipients and contacts stay consistent between Aircall and InterSystems IRIS, so a phone number or email corrected on either side is current the next time either system uses it.

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

Aircall objects InterSystems IRIS objects How this pairing syncs
Contacts Shared and personal phone-book contacts with full CRUD plus search by phone number or email; the primary two-way object synced with CRM contacts for click-to-dial. Namespaces Namespaces partition databases and determine the connection context for integrations. Contacts is specific to Aircall and Namespaces to InterSystems IRIS — each maps to any object or custom field on the other side.
Calls Inbound and outbound call records with recording URL, duration, tags, comments, and metadata; the record itself is read-only, but you can add tags, comments, insight cards, transfer, archive, and control recording. Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Calls is specific to Aircall and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side.
Users Agent seats with name, email, and availability; full CRUD to provision or deprovision seats and map Aircall agents to CRM, HR, or directory identities. Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Users is specific to Aircall and Tables to InterSystems IRIS — each maps to any object or custom field on the other side.
Numbers Provisioned phone numbers with settings, open hours, and IVR config; read and update to keep routing and business-hours data aligned across systems. Views SQL views expose curated slices of data for outbound replication. Numbers is specific to Aircall and Views to InterSystems IRIS — each maps to any object or custom field on the other side.
Tags Call tags with name and color; full CRUD, applied to calls for disposition and outcome reporting in the CRM or warehouse. Schemas Schema organization scopes which tables a sync connection can see. Tags is specific to Aircall and Schemas to InterSystems IRIS — each maps to any object or custom field on the other side.
Teams Groups of users for routing and reporting; create and delete teams and add or remove members to mirror org structure from an HR system or IdP. Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Teams is specific to Aircall and Persistent Classes to InterSystems IRIS — each maps to any object or custom field on the other side.

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

Aircall InterSystems IRIS Sub-second propagation

DetectionAircall notifies Stacksync of record changes through webhook events. Webhooks (POST /v1/webhooks) for call, contact, user, message, and number events.

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

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

Rate-limit considerations

  • Aircall: 60 requests per minute per company by default (120/min for Advanced Messaging customers); responses carry X-AircallApi-Limit, X-AircallApi-Remaining, and X-AircallApi-Reset headers.
  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with Aircall ⇄ InterSystems IRIS

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Aircall and InterSystems IRIS connectors work

Aircall

Integration surface
REST API (Aircall Public API v1, https://api.aircall.io/v1)
Authentication
HTTP Basic auth (base64 api_id:api_token) for single-account integrations, or OAuth 2.0 authorization_code flow for multi-tenant Technology Partner apps
Change detection
Webhooks (POST /v1/webhooks) for call, contact, user, message, and number events; historical pulls via list endpoints paged with from/to timestamps and order
Capabilities
read · write · webhooks
Rate limits
60 requests per minute per company by default (120/min for Advanced Messaging customers); responses carry X-AircallApi-Limit, X-AircallApi-Remaining, and X-AircallApi-Reset headers
Aircall 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 Aircall 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 Aircall 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
    Aircall connected
    InterSystems IRIS connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Aircall 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 371 integrations available for Aircall and InterSystems IRIS.

Popular · 7 of 371
All Aircall 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