Real-time
Two-way sync
Changes in Gong or Supabase instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Database
Gong to Supabase integration — real-time, two-way sync
Keep Gong and Supabase 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 Supabase
Treat Gong like part of your database: its records live in Supabase as real tables, and writes in either place sync to the other in seconds.
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 Supabase, where it can be queried and joined like everything else.
Stacksync mirrors Transcripts, Users, Interaction Stats (Activity), Trackers & Scorecards from Gong into Schemas, auth.users, Row Level Security Policies, JSONB Columns in Supabase 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.
Common use cases
- 01 Sync Interaction Stats such as talk ratios and per-rep activity into a coaching database for engagement and rep-performance dashboards.
- 02 Import externally recorded dialer or web-conference calls into Gong via POST /v2/calls so they get transcribed and analyzed like native Gong calls.
- 03 Push product events captured in Supabase Postgres to marketing tools for lifecycle campaigns
- 04 Consolidate Supabase project data into a warehouse for analytics while keeping the app database as the system of record
Common sync patterns
Product events onto CRM records
Signup, usage, or lifecycle changes written to Supabase sync onto the matching records in Gong, giving go-to-market teams live product context.
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Gong API, limits, and retries.
Trigger workflows from CRM changes
Field and stage updates in Gong arrive as row changes in Supabase, ready to drive jobs and notifications.
What you can sync between Gong and Supabase
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 | Supabase objects | How this pairing syncs | |
|---|---|---|---|
| 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 Read-side projections exposed to outbound syncs. | Users is specific to Gong and Views to Supabase — 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 Namespaces (public and custom) that scope sync access. | Interaction Stats (Activity) is specific to Gong and Schemas to Supabase — 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. | auth.users Managed authentication users, often mirrored into CRM or support systems. | Trackers & Scorecards is specific to Gong and auth.users to Supabase — 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. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | CRM Objects is specific to Gong and Row Level Security Policies to Supabase — 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. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | Library is specific to Gong and JSONB Columns to Supabase — 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. | Database Functions Postgres functions that can transform or validate synced rows. | Data Privacy (Erasure) is specific to Gong and Database Functions to Supabase — each maps to any object or custom field on the other side. |
How changes propagate between Gong and Supabase
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 Supabase 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 applied to Supabase as a row-level write, with types converted between the two schemas.
Supabase Gong Sub-second propagation
DetectionSupabase pushes changes as they happen — webhook events backed by change data capture. Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime.
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.
- Supabase: SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits.
What ships with Gong ⇄ Supabase
Connect Gong and Supabase for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gong–Supabase connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Gong or Supabase 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 Supabase record.
Observability
Monitoring
Track your Gong ⇄ Supabase 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 Supabase.
How the Gong and Supabase 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.
Supabase
- Integration surface
- Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST)
- Authentication
- Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer
- Change detection
- Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works
How to connect Gong to Supabase — 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.
- 01
Connect your apps
Authenticate Gong and Supabase with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Gong
connected
Supabase
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Gong and Supabase 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.
objects · Gong ⇄ SupabaseCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Gong SupabaseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Gong and Supabase integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Gong and Supabase: authenticate both systems, choose the objects to sync (such as Gong's Users and Interaction Stats (Activity)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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. Supabase: Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST). Authentication: Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer. Stacksync manages authentication, retries, and rate limits on both sides.
-
Gong: Transcript retrieval is a POST to /v2/calls/transcript that accepts callIds and returns speaker-attributed, timestamped sentences only for calls that have finished processing. Supabase: Every Supabase project is a full PostgreSQL database, so standard Postgres drivers, SQL tooling, and log-based CDC apply directly. Stacksync's field mapping accounts for these differences between Gong and Supabase without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Gong and Supabase records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Gong and Supabase connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Gong–Supabase integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Gong and Supabase. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 563 integrations available for Gong and Supabase.
Popular · 8 of 563
-
Gong ⇄ Azure SQL Database -
Gong ⇄ Citus -
Gong ⇄ Couchbase -
Gong ⇄ DuckDB -
Supabase ⇄ Nimble -
Supabase ⇄ Nutshell -
Supabase ⇄ Oracle CX Sales -
Supabase ⇄ Outreach
No integrations match .
