Skip to content
CRM ⇄ Business productivity

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

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

Sync what happens in Wrike 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 Wrike 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 Spaces, Tasks, Folders & Projects, Custom Fields in Wrike to Interaction Stats (Activity), Trackers & Scorecards, CRM Objects, Library in Gong with bi-directional, real-time sync. Activity and record changes in Wrike update the matching contact or account in Gong, and CRM data flows the other way wherever Wrike can store and use it.

Common use cases

  • 01 Mirror Folders, Projects, and Timelogs into a warehouse for cross-team reporting on status, timelines, and logged hours without manual exports.
  • 02 Push support tickets or intake requests from an operational database into Wrike Tasks, then read completion and status Custom Fields back when work finishes.
  • 03 Upload warehouse- or CRM-derived Accounts, Opportunities, and stages into Gong through the CRM integration API so deal context shows alongside conversations.
  • 04 Submit data-privacy erase-data-for-email requests to Gong to fulfill GDPR/CCPA deletion across recorded conversations.

Common sync patterns

Where Wrike supplies contact or company data

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

Where Wrike can store CRM context: fields kept current

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

Where Wrike 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.

What you can sync between Gong and Wrike

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 Wrike objects How this pairing syncs
Library Call-library folders and folder content (curated calls and snippets) read via GET /v2/library/folders and /v2/library/folder-content. Read-only. Spaces Top-level containers that hold Folders, Projects, and their members; used to scope which Folders a given sync covers. Library is specific to Gong and Spaces to Wrike — 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. Tasks The primary unit of work and main record; created, updated, completed, and deleted via the REST v4 API and synced two-way. Subtasks are Tasks linked by superTask/subTask references. Data Privacy (Erasure) is specific to Gong and Tasks to Wrike — 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. Folders & Projects The container hierarchy: Folders group Tasks, and Projects add dates, an owner, and a status. Each maps to a synced table scope, and its structure defines what a sync covers. Calls is specific to Gong and Folders & Projects to Wrike — 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. Custom Fields Typed fields (Text, Numeric, Date, DropDown, Contacts, Checkbox) defined at account or space level; mapped to database columns, with values written by field ID. Transcripts is specific to Gong and Custom Fields to Wrike — 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. Comments Discussion and activity entries attached to Tasks and Folders; read out for history and reporting or written back as comments. Users is specific to Gong and Comments to Wrike — 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. Timelogs Time-tracking entries logged against Tasks; read for billing and utilization reporting or written back when hours are recorded elsewhere. Interaction Stats (Activity) is specific to Gong and Timelogs to Wrike — each maps to any object or custom field on the other side.

How changes propagate between Gong and Wrike

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

Wrike Gong Sub-second propagation

DetectionWrike notifies Stacksync of record changes through webhook events. Webhooks scoped to a folder, a space, or the whole account fire on events like TaskCreated, TaskStatusChanged, and FolderCreated, with event.

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.
  • Wrike: Approximately 400 requests/minute per user (estimated on a per-second basis) with a higher per-IP ceiling; exceeding the limit or tripping Wrike's internal overload protection returns HTTP 429, handled with exponential backoff.
What ships with Gong ⇄ Wrike

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Wrike

Integration surface
REST API v4 (JSON), single account endpoint such as www.wrike.com/api/v4; the data-center host (US or EU) comes from the OAuth token response, plus REST-managed Webhooks
Authentication
OAuth 2.0 for multi-user apps (Authorization header carrying access_token and requested scopes), and a legacy Permanent Access Token for single-account and testing use
Change detection
Webhooks scoped to a folder, a space, or the whole account fire on events like TaskCreated, TaskStatusChanged, and FolderCreated, with event filtering and custom payload fields; polling the task updatedDate is the fallback
Capabilities
read · write · webhooks
Rate limits
Approximately 400 requests/minute per user (estimated on a per-second basis) with a higher per-IP ceiling; exceeding the limit or tripping Wrike's internal overload protection returns HTTP 429, handled with exponential backoff
Wrike setup guide
How it works

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

    Choose tables

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

Gong and Wrike 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 534 integrations available for Gong and Wrike.

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

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