Skip to content
CRM ⇄ Business productivity

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

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

Sync what happens in Microsoft Teams 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 Teams 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 Channel Messages, Chats & Chat Messages, Team Members & Users, Online Meetings in Microsoft Teams to Interaction Stats (Activity), Trackers & Scorecards, CRM Objects, Library in Gong with bi-directional, real-time sync. Activity and record changes in Microsoft Teams update the matching contact or account in Gong, and CRM data flows the other way wherever Microsoft Teams can store and use it.

Common use cases

  • 01 Archive channel messages into a warehouse for compliance and communication analytics.
  • 02 Post CRM deal-stage changes or new-lead alerts into a sales channel as they sync.
  • 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 Teams 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 Teams supplies contact or company data

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

Where Microsoft Teams can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Gong sync into Microsoft Teams, so people working there have the context without switching tools.

What you can sync between Gong and Microsoft Teams

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 Teams 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. Team Members & Users Membership synced with identity, HR, or CRM ownership data. Calls is specific to Gong and Team Members & Users to Microsoft Teams — 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. Online Meetings Meeting records synced with scheduling and CRM activity timelines. Transcripts is specific to Gong and Online Meetings to Microsoft Teams — 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. Tabs & Installed Apps App configuration read to audit or provision team workspaces. Users is specific to Gong and Tabs & Installed Apps to Microsoft Teams — 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. Teams Team containers provisioned or read to mirror org and project structure. Interaction Stats (Activity) is specific to Gong and Teams to Microsoft Teams — 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. Channels Channel targets used for routing synced notifications and updates. Trackers & Scorecards is specific to Gong and Channels to Microsoft Teams — 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. Channel Messages Posted messages read for archiving or written to broadcast record changes. CRM Objects is specific to Gong and Channel Messages to Microsoft Teams — each maps to any object or custom field on the other side.

How changes propagate between Gong and Microsoft Teams

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

Microsoft Teams Gong Sub-second propagation

DetectionMicrosoft Teams notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) for messages and membership.

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 Teams

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Gong ⇄ Microsoft Teams 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 Teams.

How the Gong and Microsoft Teams 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 Teams

Integration surface
REST API (Microsoft Graph)
Authentication
OAuth 2.0 via Microsoft Entra ID; reading message content at scale requires Microsoft-approved protected-API access
Change detection
Graph change notifications (webhooks) for messages and membership; delta queries on some resources
Capabilities
read · write · webhooks
How it works

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

    Choose tables

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

Gong and Microsoft Teams 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 468 integrations available for Gong and Microsoft Teams.

Popular · 5 of 468
All Gong integrations All Microsoft Teams 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