Real-time
Two-way sync
Changes in Folk CRM or Gong instantly reflect in both systems. No stale data, no manual imports.
CRM
Folk CRM to Gong integration — real-time, two-way sync
Keep Folk CRM 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 Folk CRM and Gong
Run Folk CRM and Gong side by side with the same accounts and contacts in both, whether they serve different teams or one is replacing the other.
Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.
Stacksync syncs People, Companies, Groups, Custom fields in Folk CRM with Data Privacy (Erasure), Calls, Transcripts, Users in Gong in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.
Common use cases
- 01 Sync folk people and companies with a marketing or outbound tool so outreach lists stay current.
- 02 Push enriched contact data from a data warehouse into folk custom fields.
- 03 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.
- 04 Sync Interaction Stats such as talk ratios and per-rep activity into a coaching database for engagement and rep-performance dashboards.
Common sync patterns
Where both track pipeline: deal visibility across systems
Deal stage and value on shared accounts stay visible from either CRM.
Post-acquisition consolidation
Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.
Migration with a parallel run
When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.
What you can sync between Folk CRM 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.
| Folk CRM objects | Gong objects | How this pairing syncs | |
|---|---|---|---|
| Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | Trackers & Scorecards Keyword and topic tracker definitions plus coaching scorecards, including answered scorecards, read from Settings as coaching and deal-risk signals. Read-only. | Custom fields is specific to Folk CRM and Trackers & Scorecards to Gong — each maps to any object or custom field on the other side. | |
| Notes Free-text context attached to people and companies, readable for reporting. | CRM Objects Accounts, opportunities, stages, and users uploaded into Gong through the CRM integration API so CRM context appears alongside conversations. Write (upload) path. | Notes is specific to Folk CRM and CRM Objects to Gong — each maps to any object or custom field on the other side. | |
| Reminders Follow-up items that can be created from external triggers. | Library Call-library folders and folder content (curated calls and snippets) read via GET /v2/library/folders and /v2/library/folder-content. Read-only. | Reminders is specific to Folk CRM and Library to Gong — each maps to any object or custom field on the other side. | |
| People Contact records; the primary entity synced with outreach and enrichment tools. | 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. | People is specific to Folk CRM and Data Privacy (Erasure) to Gong — each maps to any object or custom field on the other side. | |
| Companies Organization records linked to people and kept aligned with billing or CS systems. | 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. | Companies is specific to Folk CRM and Calls to Gong — each maps to any object or custom field on the other side. | |
| Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | Transcripts Speaker-attributed, timestamped sentences retrieved via POST /v2/calls/transcript for one or more callIds; available only after asynchronous processing completes. Read-only. | Groups is specific to Folk CRM and Transcripts to Gong — each maps to any object or custom field on the other side. |
How changes propagate between Folk CRM 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.
Folk CRM Gong Sub-second propagation
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.
DeliveryEach detected change is written to Gong through its API, with automatic retries and rate-limit backoff.
Gong Folk CRM 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 Folk CRM through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Folk CRM: Subject to the platform's API rate limits.
- 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 Folk CRM ⇄ Gong
Connect Folk CRM and Gong for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Folk CRM–Gong connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Folk CRM 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 Folk CRM or Gong record.
Observability
Monitoring
Track your Folk CRM ⇄ Gong sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Folk CRM and Gong.
How the Folk CRM and Gong connectors work
Folk CRM
- Integration surface
- REST API
- Authentication
- API key (Bearer token)
- Change detection
- Webhook subscriptions for record events, with polling of list endpoints as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
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.
How it works
How to connect Folk CRM 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.
- 01
Connect your apps
Authenticate Folk CRM 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.
Folk CRM
connected
Gong
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Folk CRM 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.
objects · Folk CRM ⇄ GongCustomers 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.
Folk CRM GongCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Folk CRM and Gong integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Folk CRM and Gong: authenticate both systems, choose the objects to sync (such as Folk CRM's Custom fields and Notes), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Folk CRM side: People, Companies, Groups, Custom fields, plus custom fields where Folk CRM exposes them. On the Gong side: Data Privacy (Erasure), Calls, Transcripts, Users. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Folk CRM and Gong: Where both track pipeline: deal visibility across systems; Post-acquisition consolidation; Migration with a parallel run. Deal stage and value on shared accounts stay visible from either CRM.
-
Folk CRM: REST API. Authentication: API key (Bearer token). 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Folk CRM: The API surface covers people, companies, groups, deals, notes, reminders, and interactions, plus webhook subscriptions for record events. 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. Stacksync's field mapping accounts for these differences between Folk CRM and Gong without custom code.
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 439 integrations available for Folk CRM and Gong.
Popular · 5 of 439
No integrations match .
