Skip to content
CRM ⇄ Accounting and finance

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

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

Sync customers, invoices, and payment status between Recurly and Gong in real time, so sales sees the money and finance sees the relationship.

Finance and sales describe the same customers in different systems. Gong knows the relationship: who the contacts are and what is in motion with the account. Recurly knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.

Stacksync links Accounts, Subscriptions, Plans, Invoices in Recurly to Trackers & Scorecards, CRM Objects, Library, Data Privacy (Erasure) in Gong with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.

Common use cases

  • 01 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 02 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
  • 03 Import externally recorded dialer or web-conference calls into Gong via POST /v2/calls so they get transcribed and analyzed like native Gong calls.
  • 04 Upload warehouse- or CRM-derived Accounts, Opportunities, and stages into Gong through the CRM integration API so deal context shows alongside conversations.

Common sync patterns

Billing detail changes flow back

When a contact or address is corrected in Gong, Recurly gets the update before the next invoice goes out.

Collections with context

Finance sees the account owner and relationship history from Gong when chasing a balance, and sales sees that the chase is happening.

Where Gong tracks deals: closed-won creates the finance record

A won opportunity creates or updates the customer in Recurly with the right billing details, so invoicing starts without re-keying.

What you can sync between Gong and Recurly

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 Recurly objects How this pairing syncs
Transcripts Speaker-attributed, timestamped sentences retrieved via POST /v2/calls/transcript for one or more callIds; available only after asynchronous processing completes. Read-only. Subscriptions Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting. Transcripts is specific to Gong and Subscriptions to Recurly — 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. Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Users is specific to Gong and Plans to Recurly — 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. Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Interaction Stats (Activity) is specific to Gong and Invoices to Recurly — 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. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Trackers & Scorecards is specific to Gong and Transactions to Recurly — 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. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. CRM Objects is specific to Gong and Line Items to Recurly — 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. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Library is specific to Gong and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.

How changes propagate between Gong and Recurly

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

Recurly Gong Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

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.
  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with Gong ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works

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

    Choose tables

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

Gong and Recurly 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.

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 524 integrations available for Gong and Recurly.

Popular · 8 of 524
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.