Two-way sync
Changes in Gong or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Keep Gong 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.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in InterSystems IRIS, where it can be queried and joined like everything else.
Stacksync mirrors Interaction Stats (Activity), Trackers & Scorecards, CRM Objects, Library from Gong into Schemas, Persistent Classes, Globals, Namespaces in InterSystems IRIS with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Gong with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Signup, usage, or lifecycle changes written to InterSystems IRIS sync onto the matching records in Gong, giving go-to-market teams live product context.
Back-office apps read and write the synced tables; Stacksync handles the Gong API, limits, and retries.
Field and stage updates in Gong arrive as row changes in InterSystems IRIS, ready to drive jobs and notifications.
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.
| Gong objects | InterSystems IRIS objects | How this pairing syncs | |
|---|---|---|---|
| Calls Retrieved via POST /v2/calls/extensive with participants, topics, trackers, scorecards, and media URLs, filtered by fromDateTime/toDateTime; external recordings are also imported via POST /v2/calls with media uploaded via PUT /v2/calls/{id}/media. Read and write. | Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Calls is specific to Gong and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Transcripts Speaker-attributed, timestamped sentences retrieved via POST /v2/calls/transcript for one or more callIds; available only after asynchronous processing completes. Read-only. | Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Transcripts is specific to Gong and Tables to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Users Gong users and team members with roles, titles, email, and settings, read via GET /v2/users to map call owners and participants to CRM and warehouse identities. Read-only. | Views SQL views expose curated slices of data for outbound replication. | Users is specific to Gong and Views to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Interaction Stats (Activity) Aggregated talk/listen ratios, interaction stats, and day-by-day user activity retrieved via POST /v2/stats endpoints; read out for coaching and engagement reporting. Read-only. | Schemas Schema organization scopes which tables a sync connection can see. | Interaction Stats (Activity) is specific to Gong and Schemas to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Trackers & Scorecards Keyword and topic tracker definitions plus coaching scorecards, including answered scorecards, read from Settings as coaching and deal-risk signals. Read-only. | Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Trackers & Scorecards is specific to Gong and Persistent Classes to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| CRM Objects Accounts, opportunities, stages, and users uploaded into Gong through the CRM integration API so CRM context appears alongside conversations. Write (upload) path. | Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | CRM Objects is specific to Gong and Globals to InterSystems IRIS — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Gong for changes on an incremental schedule, reading only records changed since the previous pass. Polling POST /v2/calls/extensive on fromDateTime/toDateTime.
DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
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 Gong through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gong–InterSystems IRIS connection.
Changes in Gong or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Gong or InterSystems IRIS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Gong or InterSystems IRIS record.
Track your Gong ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Gong and InterSystems IRIS.
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.
Authenticate Gong 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.
Pick the Gong 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Gong and InterSystems IRIS: authenticate both systems, choose the objects to sync (such as Gong's Calls and Transcripts), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Gong side: Interaction Stats (Activity), Trackers & Scorecards, CRM Objects, Library, plus custom fields where Gong exposes them. On the InterSystems IRIS side: Schemas, Persistent Classes, Globals, Namespaces. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Gong and InterSystems IRIS: Product events onto CRM records; Internal tools without API code; Trigger workflows from CRM changes. Signup, usage, or lifecycle changes written to InterSystems IRIS sync onto the matching records in Gong, giving go-to-market teams live product context.
Gong: REST API on api.gong.io/v2 - retrieval endpoints (calls, transcript, users, stats, settings, library, logs) plus write endpoints for importing calls, uploading CRM data, and data-privacy erasure. Authentication: Basic authorization header combining an Access Key and Access Key Secret (created by a Gong technical admin, base64-encoded as key:secret); OAuth 2.0 Bearer tokens are supported for marketplace apps. InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
Gong: Rate limits default to 3 API calls per second and 10,000 calls per day per company; exceeding returns HTTP 429 with a Retry-After header, and limits can be raised by contacting Gong. InterSystems IRIS: InterSystems positions IRIS as the successor to Caché, and it is widely deployed under healthcare and financial applications. Stacksync's field mapping accounts for these differences between Gong and InterSystems IRIS without custom code.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 490 integrations available for Gong and InterSystems IRIS.