Real-time
Two-way sync
Changes in Asana or Gong instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ CRM
Asana to Gong integration — real-time, two-way sync
Keep Asana 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 Asana and Gong
Sync what happens in Asana 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 Asana 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 Users, Portfolios, Tags, Teams / Workspaces in Asana to Trackers & Scorecards, CRM Objects, Library, Data Privacy (Erasure) in Gong with bi-directional, real-time sync. Activity and record changes in Asana update the matching contact or account in Gong, and CRM data flows the other way wherever Asana can store and use it.
Common use cases
- 01 Push support tickets or intake requests from an operational database into Asana Tasks, then read completion and status Custom fields back when work finishes.
- 02 Sync Stories and completion changes from Asana into a database so downstream dashboards and tools react to project progress in near real time.
- 03 Submit data-privacy erase-data-for-email requests to Gong to fulfill GDPR/CCPA deletion across recorded conversations.
- 04 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.
Common sync patterns
Where Asana supplies contact or company data
Enriched fields land directly on records in Gong, and refreshes keep them from going stale.
Where Asana can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Gong sync into Asana, so people working there have the context without switching tools.
Where Asana 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 Asana 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.
| Asana objects | Gong objects | How this pairing syncs | |
|---|---|---|---|
| Users Members of a workspace or organization referenced by assignee and follower fields; read to resolve GIDs to names and emails. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Portfolios Collections of Projects for program-level rollup; read for cross-project status and progress reporting (Business and Enterprise). | 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. | Portfolios is specific to Asana and Interaction Stats (Activity) to Gong — each maps to any object or custom field on the other side. | |
| Tags Labels applied across Tasks; synced as a many-to-many attribute for filtering and categorization. | Trackers & Scorecards Keyword and topic tracker definitions plus coaching scorecards, including answered scorecards, read from Settings as coaching and deal-risk signals. Read-only. | Tags is specific to Asana and Trackers & Scorecards to Gong — each maps to any object or custom field on the other side. | |
| Teams / Workspaces Organizational containers that hold projects and members; used to scope which projects a given sync covers. | CRM Objects Accounts, opportunities, stages, and users uploaded into Gong through the CRM integration API so CRM context appears alongside conversations. Write (upload) path. | Teams / Workspaces is specific to Asana and CRM Objects to Gong — each maps to any object or custom field on the other side. | |
| Tasks The primary unit of work and main record; created, updated, completed, and deleted via REST and synced two-way. Subtasks are Tasks with a parent reference. | Library Call-library folders and folder content (curated calls and snippets) read via GET /v2/library/folders and /v2/library/folder-content. Read-only. | Tasks is specific to Asana and Library to Gong — each maps to any object or custom field on the other side. | |
| Projects Collections of Tasks with a layout (list, board, timeline, calendar); each project maps to a synced table scope and its custom fields define the mapping. | 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. | Projects is specific to Asana and Data Privacy (Erasure) to Gong — each maps to any object or custom field on the other side. |
How changes propagate between Asana 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.
Asana Gong Sub-second propagation
DetectionAsana notifies Stacksync of record changes through webhook events. Resource-scoped webhooks (established with an X-Hook-Secret handshake) POST events on create, change, and delete.
DeliveryEach detected change is written to Gong through its API, with automatic retries and rate-limit backoff.
Gong Asana 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 Asana through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Asana: Per token: 1,500 requests/minute on paid plans, 150/minute on free; the Search API is capped at 60/minute; concurrency caps at 50 GET and 15 write requests. Exceeding a limit returns HTTP 429 with a Retry-After header, and a separate cost-based limiter applies to complex graph traversals.
- 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 Asana ⇄ Gong
Connect Asana and Gong for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Asana–Gong connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Asana 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 Asana or Gong record.
Observability
Monitoring
Track your Asana ⇄ Gong sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Asana and Gong.
How the Asana and Gong connectors work
Asana
- Integration surface
- REST API (app.asana.com/api/1.0, JSON responses), plus resource-scoped Webhooks and a sync-token Events API
- Authentication
- OAuth 2.0 for multi-user apps, Personal Access Tokens (PATs) for single-account use and testing, and organization-scoped Service Accounts (Enterprise) for admin-level access
- Change detection
- Resource-scoped webhooks (established with an X-Hook-Secret handshake) POST events on create, change, and delete; the sync-token Events API returns incremental changes on a task or project when webhooks are not used
- Capabilities
- read · write · webhooks
- Rate limits
- Per token: 1,500 requests/minute on paid plans, 150/minute on free; the Search API is capped at 60/minute; concurrency caps at 50 GET and 15 write requests. Exceeding a limit returns HTTP 429 with a Retry-After header, and a separate cost-based limiter applies to complex graph traversals.
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 Asana 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 Asana 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.
Asana
connected
Gong
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Asana 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 · Asana ⇄ 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.
Asana GongCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Asana and Gong integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Asana and Gong: authenticate both systems, choose the objects to sync (such as Asana's Users and Portfolios), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Asana side: Users, Portfolios, Tags, Teams / Workspaces, plus custom fields where Asana exposes them. On the Gong side: Trackers & Scorecards, CRM Objects, Library, Data Privacy (Erasure). 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 Asana and Gong: Where Asana supplies contact or company data; Where Asana can store CRM context: fields kept current; Where Asana handles support or shared inboxes. Enriched fields land directly on records in Gong, and refreshes keep them from going stale.
-
Asana: REST API (app.asana.com/api/1.0, JSON responses), plus resource-scoped Webhooks and a sync-token Events API. Authentication: OAuth 2.0 for multi-user apps, Personal Access Tokens (PATs) for single-account use and testing, and organization-scoped Service Accounts (Enterprise) for admin-level access. 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.
-
Asana: Webhooks are established per resource with an X-Hook-Secret handshake and filtered by resource type and action, so a sync covering many projects registers and maintains a webhook on each target. Gong: Authentication uses a Basic authorization header built from an Access Key and Access Key Secret generated by a Gong technical admin, or OAuth 2.0 Bearer tokens for marketplace apps. Stacksync's field mapping accounts for these differences between Asana 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 534 integrations available for Asana and Gong.
Popular · 8 of 534
-
Asana ⇄ Freshsales -
Asana ⇄ Freshworks CRM -
Asana ⇄ Gladly -
Asana ⇄ Gorgias - Gong ⇄ ServiceNow
-
Gong ⇄ Slack -
Gong ⇄ BetterContact -
Gong ⇄ Agiloft
No integrations match .
