Skip to main content
The Gong integration does two things. It uploads dialed calls to Gong, recording and all, so they are transcribed, tracked, and scored alongside the rest of your team’s conversations. And for teams on Gong Engage, it imports your open call tasks into the dialer and marks them done when you call. Unlike the CRM integrations, Gong is connected once per team, and only a team admin can change its configuration. Connect it from Settings → Connections & API → Gong.

​
Architecture

​
Permissions required to connect

Salesfinity authorizes with Gong through OAuth. Gong restricts app authorization to users with technical administrator rights, so have your Gong technical admin do the connection. The consent screen asks for these scopes: The connection is stored for the team. Gong access tokens last about a day and Salesfinity refreshes them automatically; Gong rotates the refresh token on every use, and Salesfinity keeps the newest one so the two never drift.

​
Configuration

Open Configure on the Gong card. There are two tabs, and both are admin-only.
Pairs each Salesfinity user with a Gong user. The mapping decides which Gong user an uploaded call belongs to and whose Engage tasks a rep imports.Map every rep who dials. A call from a rep with no mapping is still uploaded, but under one of the other mapped users, so it lands on the wrong person’s Gong profile.
Maps each Salesfinity disposition to a Gong call outcome. The outcome is sent with every uploaded call. Leave a disposition unmapped and the call is uploaded without an outcome.

​
What Salesfinity sends to Gong

Every call is uploaded through Gong’s calls API as an outbound call titled “Salesfinity Call” with: Gong rejects a second upload carrying an ID it has already seen. Salesfinity treats that as success, which makes retries safe: a call is never duplicated in Gong.

​
Which calls are uploaded

Calls are uploaded on two paths, depending on where the contact came from.
  • Contacts imported from Gong Engage. Every logged call is uploaded, together with the task it belonged to, and the task is marked done when you finished the call. This runs as the contact’s primary sync, the same slot a CRM sync occupies for a HubSpot contact.
  • Contacts from anywhere else (CSV, HubSpot, Salesforce, Outreach, and so on). The call is uploaded after its CRM sync, and only if it is a real conversation: at least ten seconds long, recorded, and not a left-voicemail disposition. Short dials, unrecorded calls, and voicemails are skipped so they do not clutter Gong.
Uploaded calls are marked on the Salesfinity call log, so a call is never sent twice even if its sync is retried.

​
Gong Engage call tasks

If your team uses Gong Engage, import with Gong as the list source and Salesfinity pulls your open call tasks into a list named “All tasks”. A task qualifies when it is:
  • a manual task or a flow step, whose action is a call,
  • open, assigned to the Gong user mapped to you,
  • due today or earlier.
Each imported contact carries the task ID, the flow and step it came from, and the contact’s CRM ID and URL from Gong. Gong Engage tasks can only be imported this way; there is no list picker, because Engage has no lists to pick from. After you log the call, Salesfinity marks the task done in Gong as the mapped user. If Gong reports that no task changed, for example because the task was already closed or reassigned, the call log records that so the rep can see the task still needs attention.

​
Gong data inside Salesfinity

  • Contact card. The Gong Calls card lists a contact’s past Gong calls, found by their phone numbers and email, with direction, disposition, participants, and a link to the call in Gong.
  • AI Companion. The Gong specialist can pull calls, transcripts, activity and interaction stats, scorecards, trackers, library folders, tasks, flows, users, workspaces, and audit logs to answer questions such as “summarize my last three calls with Acme” or “which trackers fired on yesterday’s demo”.

​
Troubleshooting