Skip to content
CRM ⇄ ERP

Gong to Odoo integration — real-time, two-way sync

Keep Gong and Odoo 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 Odoo

Close the gap between front office and back office: Gong and Odoo share customers and status in real time, in both directions.

Gong holds the customer relationship; Odoo runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.

Stacksync syncs Library, Data Privacy (Erasure), Calls, Transcripts in Gong with Products (product.template / product.product), CRM Leads (crm.lead), Purchase Orders (purchase.order), Inventory Transfers (stock.picking) in Odoo field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 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.
  • 02 Sync Interaction Stats such as talk ratios and per-rep activity into a coaching database for engagement and rep-performance dashboards.
  • 03 Mirror invoices and journal entries into a warehouse for consolidated financial reporting across entities.
  • 04 Keep product and price list data aligned between Odoo and storefronts or marketplaces.

Common sync patterns

One customer master

Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.

Where Odoo manages people and org data: keep Gong aligned

Owners, territories, and org structure informed by Odoo stay current in Gong.

Where Odoo handles order-to-cash: closed-won flows through

A deal won in Gong creates or updates the customer in Odoo with clean data, so fulfillment and invoicing start without re-entry.

What you can sync between Gong and Odoo

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 Odoo objects How this pairing syncs
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. Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. Interaction Stats (Activity) is specific to Gong and Invoices (account.move) to Odoo — 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. Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools. Trackers & Scorecards is specific to Gong and Products (product.template / product.product) to Odoo — 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. CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems. CRM Objects is specific to Gong and CRM Leads (crm.lead) to Odoo — each maps to any object or custom field on the other side.
Library Call-library folders and folder content (curated calls and snippets) read via GET /v2/library/folders and /v2/library/folder-content. Read-only. Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems. Library is specific to Gong and Purchase Orders (purchase.order) to Odoo — 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. Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. Data Privacy (Erasure) is specific to Gong and Inventory Transfers (stock.picking) to Odoo — 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. Employees (hr.employee) HR records read for directory and provisioning syncs. Calls is specific to Gong and Employees (hr.employee) to Odoo — each maps to any object or custom field on the other side.

How changes propagate between Gong and Odoo

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

Odoo Gong Sub-second propagation

DetectionOdoo notifies Stacksync of record changes through webhook events. Polling on the write_date timestamp every record carries.

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.
  • Odoo: Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits.
What ships with Gong ⇄ Odoo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Odoo

Integration surface
XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink)
Authentication
Database user credentials or per-user API keys
Change detection
Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules
Capabilities
read · write · webhooks
Rate limits
Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits
How it works

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

    Choose tables

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

Gong and Odoo 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 543 integrations available for Gong and Odoo.

Popular · 6 of 543
All Gong integrations All Odoo 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