Does Gong integrate with Outreach?

Yes, and it is worth knowing that there are two separate integrations rather than one, each going the other way. Gong's own documentation, read 10 October 2026, opens with: Connect Gong to Outreach so that Gong can retrieve calls directly from Outreach. That is the Outreach to Gong direction, it is set up by a tech admin, and the doc says it is Available on: Any Gong plan. The other direction is documented by Outreach, not by Gong: Outreach Kaia can import existing call recordings from Gong through a direct API connection. So calls dialled in Outreach can land in Gong for analysis, and recordings captured by Gong can land in Kaia. Both pipes carry calls that have already ended.

What does the Gong Outreach integration actually sync?

On the Outreach to Gong side, Gong's doc names the fields it brings over: it imports the call outcome, imports the call purpose, indicates whether the call is inbound or outbound, and indicates if the call is recorded using stereo or mono. It also automatically imports the last 90 days of calls when you connect, so there is a backfill window rather than only new activity. Users are matched on the Email field, which means a rep whose Outreach email does not match their Gong email will not have their calls attributed. On the Gong to Kaia side the unit is the recording itself: existing Gong call recordings sync into Kaia, with a choice between syncing all recordings or only recordings from active Outreach users.

What does the integration not sync?

This is the part most setup guides skip, and it is in Gong's own compatibility list. Gong's Outreach doc marks four categories as not supported: short calls under 30 seconds, call attempts, non-recorded calls and voicemail calls. For an SDR team that is a large share of the day. If you are connecting the two tools in order to measure dial activity, the dials that did not connect and the voicemails that did are exactly the rows that will be missing from Gong, and the numbers in the two systems will not reconcile. Measure activity where the dialling happens, in Outreach, and use Gong for the conversations that actually took place.

What licence do you need to sync Gong recordings into Outreach Kaia?

Outreach states the requirement in one sentence: The Amplify package is required. On top of that, the documentation says your organization must already be enabled for both Outreach Kaia and Gong, and that you need a Gong Admin API key before you start. So this direction is not a toggle on a standard seat, it is a package purchase plus two enabled products plus an admin credential. The other direction is cheaper to switch on: Gong says its Outreach integration is Available on: Any Gong plan and that a tech admin can do it.

Is there a security catch when Gong recordings sync into Kaia?

There is one and Outreach publishes it plainly, which is to its credit, but you have to read the article to find it. The sentence is: Recordings synced from Gong whose host is not recognized as an Outreach user will be treated as public, since Kaia's current governance model has no other way to restrict access to them. Read that against a real org chart. Any call hosted by somebody who has left, by a contractor, or by a colleague who uses Gong but has no Outreach seat, arrives in Kaia as a public recording. The mitigation is in the same article: choose to sync only recordings from active Outreach users rather than syncing all recordings. Decide that before the first sync, not after.

Does Gong or Outreach help a rep during the live call?

One of them does and it is not Gong. Outreach Kaia runs a live meeting assistant with content cards that appear during the conversation, and Outreach documents what gates it: Only users who have been assigned a Kaia license will have their calls joined by Kaia, Kaia for Voice functionality including content cards is only available with Outreach Voice, other features of Kaia such as Content Cards, Smart Meeting Assist and Custom Topics are only supported in English, and Only your Reps can currently see the Live Kaia experience. For video calls Kaia joins the meeting as a participant, and the Zoom meeting host must be in the meeting and grant recording permission to Kaia. Gong, by contrast, claims nothing in the live minute. We read the Gong Enable page on 10 October 2026 looking for an in-call claim and the only sentence containing the word live is about practising every upcoming customer meeting through live AI role-play before it happens. Neither of the two sync pipes between the products moves anything while a call is running.

Do you still need both Gong and Outreach if they are integrated?

The integration does not remove the overlap, it only makes the overlap visible. Both products can capture and analyse the same conversation, so once the pipes are open you are paying two vendors to hold one call and you have to decide which of them is the source of truth for call data. The common split is Outreach as the execution layer, sequences, dials and meetings, and Gong as the analysis layer across the whole revenue motion. If instead you are evaluating Outreach Kaia against Gong as the single conversation intelligence product, the licence stack matters more than the feature grid: Kaia Live needs a Kaia licence, the Gong import needs Amplify, and the Voice feature set needs Outreach Voice.

Compare / Gong Outreach integration

The Gong and Outreach integration is two one-way pipes, and both of them move finished calls

Objeq whispers the next line on your live sales calls. See it answer "We already have Gong and Outreach." →

Every claim below read off help.gong.io and support.outreach.io on October 10, 2026, and quoted rather than summarised · By the Objeq team

Short answer. There is no single "Gong Outreach integration". There are two, they point in opposite directions, and each one is documented by a different vendor. Gong's own doc says "Connect Gong to Outreach so that Gong can retrieve calls directly from Outreach", it is "Available on: Any Gong plan", and it "automatically imports the last 90 days of calls". Outreach's doc covers the other way: "Outreach Kaia can import existing call recordings from Gong through a direct API connection", and for that one "The Amplify package is required". Four call types never arrive at all on the Outreach to Gong side: voicemail, calls under 30 seconds, call attempts and non-recorded calls. And both pipes carry calls that already ended. The only live thing in this pair is Outreach Kaia's content cards, which need a Kaia licence, English, and a host who admits the assistant to the meeting.

What moves, in which direction, and who pays for it

	Outreach → Gong	Gong → Outreach Kaia
Who documents it	Gong, in its own help centre	Outreach, in its support portal
What the doc says it does	"Connect Gong to Outreach so that Gong can retrieve calls directly from Outreach"	"Outreach Kaia can import existing call recordings from Gong through a direct API connection"
Plan or package needed	"Available on: Any Gong plan"	"The Amplify package is required", plus both products already enabled
Who switches it on	"Who can use this: Tech admin"	An admin holding a Gong Admin API key
Backfill	"automatically imports the last 90 days of calls"	"existing" recordings, with no window published in the article
Field level detail	Call outcome, call purpose, inbound or outbound, stereo or mono	The recording itself, all of them or only those from "active Outreach users"
What it refuses	Voicemail calls, "short calls (under 30 seconds)", "call attempts", "non-recorded calls"	Nothing stated, but see the governance line below
How people are matched	On the "Email" field	Host recognised as an Outreach user, or not
Anything during the call	No	No

Both columns are the vendors' own published words, read 10 October 2026. Green marks the easier side of that row only.

Pipe one: Outreach to Gong, cheap to turn on and selective about what it takes

This is the direction most teams mean when they search for the integration. A rep dials from Outreach, and the call plus its metadata should end up in Gong where the analysis lives. Gong documents it as a direct connection rather than a middleman, and it says so in a sentence worth keeping:

"Connect Gong to Outreach so that Gong can retrieve calls directly from Outreach."

"This is more reliable than going through a third party and makes troubleshooting easier."

"Who can use this: Tech admin" · "Available on: Any Gong plan" · it "automatically imports the last 90 days of calls".

What comes with each call: "Imports the call outcome" · "Imports the call purpose" · "Indicates whether the call is inbound or outbound" · "Indicates if the call is recorded using stereo or mono".

Gong, help.gong.io on the Outreach API integration, read 10 October 2026.

Two things in there are more useful than they look. The 90 day backfill means the integration has a history on day one, so you can connect it on a Monday and look at last quarter's calls on the Tuesday. And stereo or mono is not a trivia field: a mono recording mixes both voices into one channel, which is what makes talk ratio and interruption numbers unreliable. If your Outreach dialler records mono, Gong will still ingest the call and the speaker level metrics on it will be softer than they look.

And four kinds of call that never arrive

Gong's compatibility list marks these as not supported, and this is the line that explains why the two systems never reconcile:

Not imported: "short calls (under 30 seconds)" · "call attempts" · "non-recorded calls" · "voicemail calls".

User identification relies on the "Email" field matching.

Gong, help.gong.io on the Outreach API integration, read 10 October 2026.

For an SDR desk that is most of the day. Dials that rang out, voicemails left, the eleven second call where the gatekeeper hung up: all of it stays in Outreach and none of it lands in Gong. So if the reason you are wiring these two together is activity reporting, you are about to build a report that disagrees with itself. Count activity in Outreach, where the dialling happens. Use Gong for the conversations that actually occurred. And check the email addresses match in both systems before anyone asks why a rep's calls vanished.

Pipe two: Gong to Kaia, and the one sentence to read twice

The other direction is an Outreach feature, not a Gong feature, and the gate on it is a package name rather than a toggle.

"Outreach Kaia can import existing call recordings from Gong through a direct API connection."

"The Amplify package is required."

"Your organization must already be enabled for both Outreach Kaia and Gong", and you need a Gong Admin API key before setup.

You choose between "Sync all recordings" and "Only sync recordings from active Outreach users".

Outreach, support.outreach.io on syncing Gong recordings to Kaia, read 10 October 2026.

Now the sentence that should decide your sync setting, published by Outreach itself:

"Recordings synced from Gong whose host is not recognized as an Outreach user will be treated as public, since Kaia's current governance model has no other way to restrict access to them."

Outreach, same article, read 10 October 2026.

Read it against a real company. People leave. Contractors run calls. Customer success and support sit in Gong and have never had an Outreach seat. Every recording hosted by one of those people arrives in Kaia as a public recording, and nobody gets a warning, because the governance model has nowhere else to put it. Outreach is being straight with you by printing this. It is still a decision you have to make before the first sync rather than after it, and the mitigation is in the same article: sync only recordings from active Outreach users. Credit where it is due, a vendor that publishes its own worst paragraph is a vendor worth reading closely.

See what a live whisper looks like

Price printed on the page · From $99 / seat / mo · cancel in one click

The live half of this pair belongs to Outreach, not to Gong

People searching for this integration are often really asking a different question: once both tools are connected, does anything help the rep while the call is happening. The honest answer has two halves.

Gong does not claim the live minute. We opened the Gong Enable page the same morning, looking for an in-call claim, because finding one would have changed this page. The features named there are AI Call Reviewer, Coaching Inbox, AI Trainer, AI Coach, Lessons, Dry Run, Initiative Tracking, Coaching Metrics, Team Insights and Market Insights. The only sentence on it with the word "live" is "Practice every upcoming customer meeting through live AI role-play before it happens". That is a rehearsal.

Outreach Kaia does claim it, with content cards that surface during the conversation. What Outreach documents around that is the gate:

"Only users who have been assigned a Kaia license will have their calls joined by Kaia."

"Kaia respects your Outreach Voice recording settings. If you auto-record, Kaia will automatically join."

"Kaia for Voice functionality (transcription, note-taking, content cards, action items, analytics, and recording) is only available with Outreach Voice."

"Other features of Kaia (e.g., Content Cards, Smart Meeting Assist, Custom Topics, etc.) are only supported in English."

"Only your Reps can currently see the Live Kaia experience."

On video calls: "Outreach Kaia is currently compatible with the following platforms: Zoom, Microsoft Teams, Google Meet, WebEx", and "the Zoom meeting host must be in the meeting and grant recording permission to Kaia".

On the one-sided recording variant: "This feature only functions when a user has a Kaia Live license applied to them via the Subscriptions page. The Orchestrate license is required."

Outreach, Kaia live meeting assistant in Outreach Voice FAQ, Outreach Kaia meetings FAQ and one-sided call recording, all read 10 October 2026. Gong, gong.io Gong Enable, read the same day.

Count the names you have to buy before a single word appears on a rep's screen during a call: a Kaia licence, Outreach Voice for the Voice feature set, Orchestrate for Kaia Live on one-sided calls, and Amplify if you also want the Gong recordings in there. That is four package names, in two products, for one live sentence. Add the mechanics: the assistant joins the meeting as a participant, and on Zoom the host has to be present and grant it recording permission, so a buyer who declines the bot removes the feature from that call.

Where this leaves you, and where Objeq fits

If you already run both products, open the pipes. They are well documented, the Outreach to Gong side costs nothing extra on any Gong plan, and 90 days of backfill on day one is a genuine gift. Just set the Kaia sync to active Outreach users only, and stop counting dials in Gong.

What neither pipe does is help the rep in the moment the deal is actually lost. Both of them carry calls that have already finished, to tools that score them afterwards. The only live help in the pair is Kaia's, and it is behind a licence stack, English only, visible to reps only, and dependent on a host letting the assistant into the room.

That gap is the whole reason Objeq exists, and you should read this paragraph as the bias it is. It does one thing: it reads the browser tab the call is playing in and writes the next line on the rep's screen while the buyer is still talking. Nothing joins the meeting, so no participant list changes and no host has to approve anything. The price is printed on the pricing page, $99 a seat for Starter and $149 for Pro, flat, with no package to add before the live part works. It runs in Hebrew end to end, which is why it was built. And what it does not do is long: no dialler, no sequences, no forecasting, no CRM writes, no analytics across hundreds of calls. It replaces neither Gong nor Outreach. It sits next to both of them in the one minute they both skip.

Try the live whisper on your own objection

$99 / seat / mo after a 3-day trial · full refund within 14 days of the first charge

What we did not verify, said out loud

We read vendor documentation, not a sandbox. We did not price the Amplify, Orchestrate or Outreach Voice packages, because Outreach does not publish a dollar figure for them on the pages we opened, so treat "four package names" as a procurement question and not as a quote. The Kaia platforms article lists Zoom, Microsoft Teams, Google Meet and WebEx as compatible and does not split that list into live versus after the call, so we are not claiming which platforms carry the live content cards. Outreach does not publish a backfill window for the Gong to Kaia import the way Gong publishes 90 days for the other direction. And none of this is tested against your tenant. If either vendor changes a line, this page is wrong until we read it again, and the date at the top is there so you can tell how stale it is.

Questions people ask next

Is Outreach Kaia the same thing as Gong?

They overlap on conversation intelligence and they are not interchangeable. Kaia sits inside the Outreach execution layer, next to sequences, the dialler and meetings, and it has a live meeting assistant with content cards. Gong is broader and deeper after the call, across the whole revenue motion. If you are picking one, the deciding factor is usually which layer you want to own the recording, plus the licence stack on the Kaia side. The head to head we keep updated is Gong vs Outreach.

Will my Outreach dial activity show up in Gong?

Partly, and the missing part is predictable. Gong's doc lists four categories it does not import: calls under 30 seconds, call attempts, non-recorded calls and voicemail calls. Connected conversations arrive with outcome, purpose, direction and channel metadata. So activity totals belong in Outreach and conversation analysis belongs in Gong, and anyone comparing the two counts will find a gap that is working as documented.

Do I need the Amplify package for both directions?

No. Amplify is named in Outreach's article for the Gong to Kaia import. The other direction is Gong's own integration and its doc says "Available on: Any Gong plan", set up by a tech admin. So you can get Outreach calls into Gong without buying anything new, and getting Gong recordings into Kaia is the side that costs a package.

Why would synced recordings become public in Kaia?

Because Kaia decides access from the host identity, and a Gong recording can have a host who has no Outreach seat. Outreach's own sentence: recordings "whose host is not recognized as an Outreach user will be treated as public, since Kaia's current governance model has no other way to restrict access to them". Pick "Only sync recordings from active Outreach users" unless you have checked every host in Gong.

Does either tool talk to the rep during the call?

Kaia does, inside its own live meeting assistant, gated by a Kaia licence, English only, visible to reps only, and with the assistant joining the meeting. Gong does not claim it anywhere we read; its one live feature is role-play before the meeting. If the live minute is the thing you are buying, compare on real-time call coaching rather than on integration diagrams.

Sources, all opened by us rather than quoted from a summary: Gong on the Outreach API integration, Outreach on syncing Gong recordings to Kaia, Kaia live meeting assistant FAQ, Outreach Kaia meetings FAQ, Outreach on one-sided call recording and Gong Enable, all read 10 October 2026. Objeq's own prices are on our pricing page. Related: Gong vs Outreach, Objeq vs Outreach, Salesloft vs Outreach, sales coaching software comparison.