Skip to content
Security and identity ⇄ CRM

Active Directory to Gong integration — real-time, two-way sync

Keep Active Directory and Gong 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 Active Directory and Gong

Keep the people Gong and Active Directory both track in agreement in real time: the internal users who own records in Gong, and the customer login accounts in Active Directory.

A CRM and an identity system usually describe different populations. Gong tracks customers, contacts, and the deals in motion; Active Directory governs who is allowed to sign in and what they can reach. Where the two meet is people. The reps who own records in Gong are the same employees Active Directory provisions and disables, and when Active Directory also runs the login accounts for your product, the customers in Gong are the same users Active Directory authenticates. Left unconnected, a departure in Active Directory leaves stale ownership sitting in Gong, and a signup in Active Directory never reaches the account it belongs to.

Stacksync syncs Interaction Stats (Activity), Trackers & Scorecards, CRM Objects, Library in Gong with Devices, Directory roles, Service principals & applications, Organizational units in Active Directory in real time and in both directions, matching on email or an external ID and mapping field by field. You decide which system owns which fields, and new users, role and group changes, deactivations, and account status move within seconds instead of waiting on a quarterly access review or a manual export.

Common use cases

  • 01 Upload warehouse- or CRM-derived Accounts, Opportunities, and stages into Gong through the CRM integration API so deal context shows alongside conversations.
  • 02 Submit data-privacy erase-data-for-email requests to Gong to fulfill GDPR/CCPA deletion across recorded conversations.
  • 03 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
  • 04 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.

Common sync patterns

Deactivation and record hand-off

When someone is disabled in Active Directory, the matching user in Gong is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.

Where Active Directory runs customer login accounts: identity on the customer record

Signup, account status, multi-factor enrollment, and last-login from Active Directory land on the matching contact or account in Gong, so go-to-market teams see who has actually activated and who has gone dormant.

Group and entitlement membership as CRM fields

Membership of a directory group or an entitlement in Active Directory maps to fields in Gong, such as product tier, plan, or internal team, so segmentation reflects real access rather than a manual guess.

What you can sync between Active Directory and Gong

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.

Active Directory objects Gong objects How this pairing syncs
Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. 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. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. Transcripts Speaker-attributed, timestamped sentences retrieved via POST /v2/calls/transcript for one or more callIds; available only after asynchronous processing completes. Read-only. Devices is specific to Active Directory and Transcripts to Gong — each maps to any object or custom field on the other side.
Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. 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. Directory roles is specific to Active Directory and Interaction Stats (Activity) to Gong — each maps to any object or custom field on the other side.
Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. Trackers & Scorecards Keyword and topic tracker definitions plus coaching scorecards, including answered scorecards, read from Settings as coaching and deal-risk signals. Read-only. Service principals & applications is specific to Active Directory and Trackers & Scorecards to Gong — each maps to any object or custom field on the other side.
Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. CRM Objects Accounts, opportunities, stages, and users uploaded into Gong through the CRM integration API so CRM context appears alongside conversations. Write (upload) path. Organizational units is specific to Active Directory and CRM Objects to Gong — each maps to any object or custom field on the other side.
Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. Library Call-library folders and folder content (curated calls and snippets) read via GET /v2/library/folders and /v2/library/folder-content. Read-only. Organizational contacts is specific to Active Directory and Library to Gong — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and Gong

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.

Active Directory Gong Sub-second propagation

DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.

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

Gong Active Directory Interval-based propagation

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

Rate-limit considerations

  • Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
  • Gong: 3 API calls per second and 10,000 calls per day per company by default; exceeding returns HTTP 429 with a Retry-After header, and limits can be raised by contacting Gong.
What ships with Active Directory ⇄ Gong

Connect Active Directory and Gong for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Gong connection.

Real-time

Two-way sync

Changes in Active Directory or Gong instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Active Directory or Gong 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 Active Directory or Gong record.

Observability

Monitoring

Track your Active Directory ⇄ Gong sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Active Directory and Gong.

How the Active Directory and Gong connectors work

Active Directory

Integration surface
Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
Authentication
OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
Change detection
Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
Capabilities
read · write · webhooks
Rate limits
Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.

Gong

Integration surface
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
Change detection
Polling POST /v2/calls/extensive on fromDateTime/toDateTime; the public API exposes no outbound webhooks or CDC, though a Gong admin can configure a product-side automation Rule that POSTs matching calls to a URL. Transcripts and analysis appear only after asynchronous processing.
Capabilities
read · write
Rate limits
3 API calls per second and 10,000 calls per day per company by default; exceeding returns HTTP 429 with a Retry-After header, and limits can be raised by contacting Gong.
Gong setup guide
How it works

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

    Choose tables

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

Active Directory and Gong 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 527 integrations available for Active Directory and Gong.

Popular · 7 of 527
All Active Directory integrations All Gong 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