Gong call recordings fail to upload to a Salesforce opportunity most often because Gong can't match the call's participants to a contact or lead tied to an open opportunity. Missing email addresses, broken field mappings, insufficient Salesforce permissions on the Gong integration user, or opportunity stage rules also block the sync.
How Gong Decides Which Opportunity Gets the Call
Gong doesn't upload every recording to every record. It runs matching logic that ties a call to a Salesforce opportunity through the people on the call. If a participant's email matches a Contact or Lead, and that Contact is linked to an open opportunity, Gong logs the activity there. Break any link in that chain and the recording lands nowhere—or on the account instead of the opportunity.
Most teams get this wrong by assuming Gong knows business context. It doesn't. It only knows email addresses, activity records, and whatever mapping you configured.
The Most Common Reasons Uploads Fail
Missing or Unmatched Email Addresses
This is the number one cause. If external participants dialed in without a calendar invite, or the invite used a personal email that isn't on any Contact, Gong has nothing to match against. Internal-only calls also won't attach to an opportunity because there's no customer contact to anchor the match.
Fix it by making sure the meeting invite includes the prospect's work email and that email exists as a Contact or Lead in Salesforce.
No Open Opportunity on the Account
Gong typically attaches calls to open opportunities. If the deal is closed-won, closed-lost, or no opportunity exists yet, the call logs to the account or contact instead. Check whether the opportunity is still open and in a stage Gong is configured to sync to.
Broken or Missing Field Mappings
In Gong's Salesforce settings, activity fields map to Salesforce Task or Event fields. A renamed field, a deleted custom field, or a mapping pointed at a field the integration user can't write to will silently fail the upload. Review your mapping under Company Settings → CRM → Salesforce whenever your Salesforce admin changes objects or fields.
Integration User Permission Gaps
Gong writes to Salesforce as a dedicated integration user. If that user's profile lacks Create/Edit on Tasks, Events, or the opportunity object—or lacks Field-Level Security on a mapped field—the write fails. Validation rules and required fields on the Task object are a frequent culprit; if Gong doesn't populate a required custom field, Salesforce rejects the record. This overlaps with how Gong handles access controls across your CRM.
Sync Delay vs. True Failure
Gong's CRM sync isn't instant. Recordings can take from several minutes up to a few hours to appear, especially during high-volume periods or Salesforce API throttling. Before troubleshooting, confirm you've actually waited past the normal delay window.
A Quick Diagnostic Checklist
Run through these in order before opening a support ticket:
- Confirm the call has an external participant with a work email that matches a Salesforce Contact or Lead.
- Verify the account has an open opportunity in a synced stage.
- Check that the Gong integration user has Create/Edit permissions and Field-Level Security on all mapped fields.
- Review Salesforce validation rules and required fields on Task/Event objects.
- Look at the Gong deal or call page for a "not matched" or sync error indicator.
- Wait past the normal sync window, then re-check.
Field Mapping and Permission Reference
| Failure point | What breaks | Where to fix |
|---|---|---|
| Email match | Participant email not on any Contact/Lead | Salesforce Contacts; meeting invites |
| Opportunity state | No open opp, or stage not synced | Salesforce opportunity; Gong sync settings |
| Field mapping | Renamed/deleted mapped field | Gong CRM settings |
| Permissions | Integration user lacks write access | Salesforce profile / permission set |
| Validation rules | Required field not populated by Gong | Salesforce Task/Event validation rules |
When It's a Salesforce-Side Problem
Sometimes Gong is doing everything right and Salesforce blocks the write. API limits, duplicate rules, and Apex triggers on the Task object can all reject Gong's inserts. If your org fires an Apex trigger that requires fields Gong doesn't send, every activity insert from the integration user fails. Ask your Salesforce admin to check the debug logs filtered to the Gong integration user—the exact error code usually points straight at the offending rule or trigger.
Gong's own Salesforce integration documentation covers the required permission set and object access in detail, and it's worth cross-checking against your current profile after any Salesforce release.
Preventing Future Upload Failures
Keep your Contact data clean so email matching stays reliable, and coordinate with your Salesforce admin before changing any object mapped in Gong. Reliable activity logging feeds the analytics that help you improve pipeline velocity, so a broken sync costs more than a missing recording—it corrupts your reporting.
Key Takeaways
Gong uploads a recording to a Salesforce opportunity only when a call participant's email matches a Contact tied to an open opportunity, the field mappings are intact, and the integration user has full write permissions. Start diagnosing with email matching and opportunity state, then check permissions and validation rules. When in doubt, pull the Salesforce debug log for the Gong integration user—the error code names the exact blocker.