Skip to content
CRM ⇄ Business productivity

Gong to Microsoft Dynamics 365 integration — real-time, two-way sync

Keep Gong and Microsoft Dynamics 365 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 Gong and Microsoft Dynamics 365

Sync what happens in Microsoft Dynamics 365 with the customer records in Gong, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Microsoft Dynamics 365 holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Products, Activities, Custom Tables, Accounts in Microsoft Dynamics 365 to Calls, Transcripts, Users, Interaction Stats (Activity) in Gong with bi-directional, real-time sync. Activity and record changes in Microsoft Dynamics 365 update the matching contact or account in Gong, and CRM data flows the other way wherever Microsoft Dynamics 365 can store and use it.

Common use cases

  • 01 Enrich leads from external data sources and write scores back onto Dynamics records.
  • 02 Two-way sync of accounts and contacts with a Postgres or SQL database so engineers query SQL while sales works in Dynamics.
  • 03 Submit data-privacy erase-data-for-email requests to Gong to fulfill GDPR/CCPA deletion across recorded conversations.
  • 04 Pull call Transcripts by callId into a warehouse or vector store to power search, RAG, and deal-review summaries over what was said on calls.

Common sync patterns

Where Microsoft Dynamics 365 handles support or shared inboxes

Tickets and conversations attach to the right contact and account in Gong, so sales sees open issues before the next call.

Where Microsoft Dynamics 365 supplies contact or company data

Enriched fields land directly on records in Gong, and refreshes keep them from going stale.

Where Microsoft Dynamics 365 processes payments

Charges, refunds, and subscription changes appear on the account in Gong, so revenue context lives with the relationship.

What you can sync between Gong and Microsoft Dynamics 365

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 Microsoft Dynamics 365 objects How this pairing syncs
Library Call-library folders and folder content (curated calls and snippets) read via GET /v2/library/folders and /v2/library/folder-content. Read-only. Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. Library is specific to Gong and Opportunities to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Data Privacy (Erasure) GDPR/CCPA deletion handled by POST /v2/data-privacy/erase-data-for-email, with data-for-email lookups on the read side; a write path used for compliance deletions. Cases (Incidents) Support records shared with ticketing tools and product databases. Data Privacy (Erasure) is specific to Gong and Cases (Incidents) to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
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. Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. Calls is specific to Gong and Quotes, Orders & Invoices to Microsoft Dynamics 365 — 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. Products Catalog records aligned with ERP item masters. Transcripts is specific to Gong and Products to Microsoft Dynamics 365 — 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. Activities Emails, calls, and tasks captured for engagement analytics. Users is specific to Gong and Activities to Microsoft Dynamics 365 — 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. Custom Tables Dataverse tables that carry business-specific entities through the same API surface. Interaction Stats (Activity) is specific to Gong and Custom Tables to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.

How changes propagate between Gong and Microsoft Dynamics 365

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.

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

Microsoft Dynamics 365 Gong Sub-second propagation

DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.

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

Rate-limit considerations

  • 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 Gong ⇄ Microsoft Dynamics 365

Connect Gong and Microsoft Dynamics 365 for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gong–Microsoft Dynamics 365 connection.

Real-time

Two-way sync

Changes in Gong or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Gong or Microsoft Dynamics 365 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 Gong or Microsoft Dynamics 365 record.

Observability

Monitoring

Track your Gong ⇄ Microsoft Dynamics 365 sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Gong and Microsoft Dynamics 365.

How the Gong and Microsoft Dynamics 365 connectors work

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

Microsoft Dynamics 365

Integration surface
REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
Authentication
Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities)
Change detection
Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties
Capabilities
read · write · CDC · webhooks
Microsoft Dynamics 365 setup guide
How it works

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

    Choose tables

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

Gong and Microsoft Dynamics 365 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
CSA STAR
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 536 integrations available for Gong and Microsoft Dynamics 365.

Popular · 8 of 536
All Gong integrations All Microsoft Dynamics 365 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