---
name: gong-reverse-contact-integration
description: Connect Gong and Reverse Contact: what syncs, which editions carry it, the setup order, and the failures to expect. Covers activities, contacts, companies. Use when the user wants to set up, audit or troubleshoot Gong and Reverse Contact together, or asks why data is not moving between them.
---

# Gong and Reverse Contact

> Generated from https://www.reversecontact.com/integrations-hub/gong-integrations/gong-reverse-contact-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-28.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** A Gong technical administrator to create API credentials, a Reverse Contact API key, and somewhere to run the lookup

**What moves:** activities, contacts, companies, one way, out of Gong.
**How it is built:** built on the api. **Effort:** days.

## The short version

Gong knows exactly who was on the call and surprisingly little about them. Its own Enrich feature closes part of that gap with a waterfall over six named data partners, and Reverse Contact is not one of them, so this is an API build rather than a configuration. The fact worth the whole page is what Gong Enrich does when somebody has changed job: it checks, finds they have left, stops before querying anybody, and charges nothing. You learn that the record is wrong and not what it should say instead.

## Four routes to an enriched call participant

Rows: The route. Columns: What it gets you. Gong is the only partner in this directory that ships its own enrichment waterfall, which makes the comparison here a comparison of products rather than of plans. Every figure and every partner name below is from Gong's own documentation, and the first column is the one that explains why this page is an API page.

| The route | Reverse Contact can be the provider | A job change says where they went | A miss costs nothing | The answer reaches the Gong record |
|---|---|---|---|---|
| Gong Enrich, a partner on Gong credits | No | No | Partly | Yes |
| Gong Enrich, a partner on your own key | No | No | Partly | Yes |
| Reverse Contact through the Gong API | Yes | Yes | Yes | Partly |
| The CRM enriched, Gong reading it | Yes | Yes | Yes | Yes |

- **Yes.** Documented and unambiguous. Through the API or the CRM, Reverse Contact is the provider because you are choosing it rather than selecting it from a list, a reverse lookup from the email returns the current position, and every 4xx and 5xx is 0 credits with Find Email and Find Phone refunded when nothing is found. Gong already reads the CRM, so the last cell needs no new integration at all.
- **Partly.** True with a condition. Gong charges no credit when a partner finds nothing, and does charge one when a partner returns an email that then fails validation, so a miss is free and a bad answer is not. On the API route the answer reaches Gong only by way of the CRM or Gong's own CRM upload endpoint, because there is no field on a Gong call to write a person into.
- **No.** Not true on that one. Gong Enrich names six supported data partners and Reverse Contact is not among them; bring your own key is a credential swap on a supported partner rather than a way to add one. And Enrich treats a job change as a stop condition: it checks whether the contact still works at the account, halts if they do not, and uses no credits doing so.

Counted off that grid, of sixteen pairings: nine give you yes, three give you partly, four give you no.

The second column is the finding and it is worth stating plainly on a page the publisher of this directory pays for: Gong's own enrichment does detect that somebody has changed job, and then stops, because finding the new employer is not what a contact-details waterfall is for. The bottom row is best on every count and is also the least interesting build on this page, which is usually how it goes: enrich the CRM, let Gong read it, and touch the Gong API only for the participants that never reach a CRM at all.

## What actually syncs

Direction is written from Gong's point of view: out means out of Gong, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| The calls | One way, out | GET the calls for a date range, then read the internal and external participants on each. |
| The external participants | One way, out | Email addresses that may belong to nobody in your CRM, which is the gap this build exists to close. |
| The lookup | One way, out | POST /v2/enrich/persons on each external address. 2 credits on a match, nothing on an error. |
| The write | One way, in | To the CRM Gong already reads, or through Gong's own CRM upload endpoint if there is no CRM. |

## Which field lands where

There is nothing to map inside Gong, because the build reads from it rather than writing to it. What is worth laying out is which part of a call Gong hands you, which part of a person Reverse Contact hands back, and where the two meet, which is almost always a CRM record rather than either product.

| In Gong | In Reverse Contact | What to know about the match |
|---|---|---|
| A call, by date range | The Gong calls endpoint, cursor paged | One of 10,000 company-wide calls a day at 3 a second. The records field carries the page and the total, and a cursor arrives when there is more. |
| External participants on that call | Email addresses, and little else | Gong returns internal and external participants along with topics, trackers, public comments, scorecards and transcripts. An external participant who matches nothing in the CRM is the subject of this page. |
| That email address | POST /v2/enrich/persons, 2 credits | Identity, the current role, the history and the company behind it on one schema. A miss returns null with a confidence score and costs nothing. |
| The domain of that address | POST /v2/enrich/companies, 2 credits | Firmographics from a domain. A meeting booked from a personal address has no useful domain, which is the case where the person lookup is the only route to the account. |
| currentPosition.companyName | A comparison against the filed account | The one row on this table that justifies the build. Gong tells you the contact has left; this tells you where they went. |
| currentPosition.title and seniority | The CRM contact record | Who was actually in the room, in the terms a pipeline review uses. Gong has the attendance and not the seniority. |
| The resolved contact | Your CRM, which Gong already reads | One copy of the answer, no Gong calls spent, and it survives replacing the recorder. Gong's CRM upload endpoint is for the case where there is no CRM at all. |
| Anything outbound to Reverse Contact | Only the identifier you send | This is a read layer. No call, transcript or recording is sent anywhere, and there is nothing in the product to send it to. |

### What Gong knows about the person on the call

Gong is extremely good at the conversation and deliberately thin on the participant, and the split is not obvious from the outside. Each row below is something a pipeline review asks about an external attendee, with where the answer actually comes from.

| The question | Where the answer comes from |
|---|---|
| Were they on the call, and for how long | Gong, in detail. Internal and external participants are part of what the API is documented to return, alongside topics, trackers, scorecards and the transcript |
| What is their email address | Gong, if they were invited by it. Gong Enrich exists precisely because sometimes they were not, and that is the gap it is built for |
| What is their job title | Gong Enrich can make it available as related contact information, or a reverse lookup returns it with the rest of the record. Not something the call itself carries |
| Do they still work there | Gong Enrich checks this and uses it as a stop condition rather than as an answer. It will tell you no and then stop |
| If not, where did they go | Reverse Contact, from the same email address. This is the question Gong's own enrichment is designed not to answer, because answering it is not what a contact-details waterfall is for |
| How senior are they, and who do they report to | Neither, reliably. The response carries seniority and position history; reporting lines are not published by anybody here and should not be inferred from a follower count |

**What does not cross:**

- Reverse Contact inside Gong Enrich. The supported partners are LeadIQ, Wiza, RocketReach, Lusha, ZoomInfo and Findymail, and bring your own key applies to a partner on that list rather than adding to it.
- A published Gong credit rate. Gong says consumption varies by data type, provider and other factors, that the applicable rate is shown in the Admin Center, and that it may be updated prospectively, so no figure belongs on this page.
- The transcript. Nothing in this build reads what was said, and a transcript is the one thing on a call record that should not leave the company for an enrichment.
- A business email or a direct phone number from Reverse Contact. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and both are asynchronous, which is the same job Gong Enrich already does inside the product.

## Connect it, in this order

**Who has to do it:** A Gong technical administrator for the API credentials, an admin if Enrich is in scope, plus whoever hosts the middle layer and whoever can create a Reverse Contact API key.
**How long:** A day or two. The credentials and the participant extraction are the slow parts.

### 1. Decide whether you are turning Gong Enrich on, because that cannot be undone

*Where:* Gong: Admin center > Data enrichment

Gong states that once Enrich is enabled it cannot be disabled, though manual and flow permissions can be withdrawn afterwards. It is a separate question from this build and a cheaper answer to a narrower problem, so decide it deliberately rather than while looking for something else.

### 2. Work out what your Gong call budget already is

*Where:* Gong: whatever is already connected

The limit is 3 calls a second and 10,000 a day for the company, not for your integration. Before designing a sweep, find out what the CRM sync, the BI export and anything else are already spending, because this is the one number on the page that somebody else can exhaust for you.

### 3. Create API credentials as a technical administrator

*Where:* Gong: the API page, app.gong.io/company/api

You get an Access Key and an Access Key Secret, combined with a colon and base64 encoded for a Basic Authorization header, or a bearer token through the OAuth flow. The base URL is per company and is shown on the API authentication page rather than being a constant you can hard-code.

### 4. Pull the calls for a date range and read the participants

*Where:* Gong: the calls endpoints, with the cursor

A list response carries a records field with the page size, the page number and the total, plus a cursor when there is more. Repeat the call with that cursor and change nothing else, and remember that Gong may add JSON fields without warning so ignore what you do not use.

### 5. Separate the external participants from the internal ones

*Where:* Your middle layer

The internal ones are your colleagues and enriching them is a waste of credits and slightly rude. The external ones are the point, and the subset worth paying for is narrower still: the addresses that match nothing you already hold.

### 6. Check before you fetch, on the endpoint that costs nothing

*Where:* POST /v2/fetch/persons/check

The free check says whether a profile is cached and when it was last updated, so a sweep over a quarter of calls spends 2 credits only where the answer is genuinely new. Errors cost nothing either, which is the opposite of how the Gong side of this works.

### 7. Compare the returned employer against the account the call was filed under

*Where:* Your middle layer

This is the whole reason to do this rather than use Enrich. When Gong decides a contact has left the account it stops and tells you nothing further; a reverse lookup on the same address returns the current position, which is where they went. One comparison, and it is the most valuable line of code in the build.

### 8. Write the answer to the CRM, not to Gong

*Where:* Your CRM, through its own API

Gong already reads the CRM, so writing there gives one copy of the answer, costs none of the daily Gong allowance and survives a change of recorder. Gong's API can take CRM data if there is genuinely no CRM, and that is the only case where pushing into Gong is the right move.

### 9. Run one quarter of calls before running the archive

*Where:* Your middle layer, with a limit on it

A quarter tells you how many external participants a call actually has, how many of them are unknown, and therefore what the archive would cost in both credits and Gong calls. At 10,000 calls a day for the company, that arithmetic decides whether a backfill is a weekend or a month.

The first step is irreversible and unrelated to everything after it, which is an awkward combination: somebody evaluating this build can accidentally commit the company to a feature while looking at a different one. The seventh step is the one that earns the work, and it is three lines rather than an integration.

## How to check it worked

- Take a call with an external participant you know is not in the CRM, and follow it all the way through. If the account ends up on the record, the build works; if it ends up only in a log, it does not.
- Enrich somebody who has changed employer since the call, deliberately. The returned current position should name the new company, which is precisely the answer Gong Enrich declines to go and get.
- Read the records field and the cursor on a list response rather than assuming one page. A build that reads the first page of a quarter and reports success is the quiet failure here.
- Count your Gong calls for a day against 10,000 and remember whose budget it is. If the CRM sync is already using most of it, your sweep has to run when it is not.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| Reverse Contact is not in the data partner dropdown | Gong Enrich supports LeadIQ, Wiza, RocketReach, Lusha, ZoomInfo and Findymail, and the list is not extensible by the customer. | Stop looking for it and build on the API instead, or enrich the CRM and let Gong read it. Bring your own key will not help, because it attaches a credential to a partner that is already on the list. |
| Enrich reported that the contact has left and did nothing else | Gong checks whether the contact still works at the company on their record before querying any partner, and stops if they do not, using no credits. | That is the designed behaviour and it is also your signal. Take the same address to a reverse lookup, which returns the current position, and treat the Gong result as a trigger rather than as a dead end. |
| A Gong credit was charged for an email we could not use | Returned addresses are validated and a failing one is discarded, and Gong charges the credit anyway because the partner returned data. | Order the waterfall with the most accurate provider first rather than the cheapest, since a wrong answer costs the same as a right one. Nothing on the Gong side refunds it. |
| Enrich again did nothing on a record we know is stale | Within 90 days Enrich skips data partners it has already queried for that contact, so a second attempt may have nobody left to ask. | Wait for the 90 days, add a partner that has not been tried, or go round it with a lookup of your own. The second attempt is not a retry of the first. |
| A 429 from Gong halfway through a backfill nobody else was running | The limit is 3 calls a second and 10,000 a day at company level, shared with every other integration connected to Gong. | Honour Retry-After, and find out what the CRM sync and any BI export are spending before scheduling a sweep. Gong says support can raise the limits if required, which is a conversation rather than a setting. |
| The sweep read one page of calls and reported success | List endpoints page with a cursor, and a response carries a records field with the page size, page number and total. | Repeat the request with the cursor from the previous response and change nothing else. Compare the rows you processed against the total in the records field before believing any run. |
| A region came back with no data at all | Gong's enrichment controls carry settings to exclude people located in the European Union and people in California. | Check the exclusion settings before concluding anything about coverage. This is a configured policy rather than a gap in anybody's database. |
| The integration broke after an endpoint rename | Reverse Contact replaced /v2/resolve with /v2/enrich and /v2/search/persons with /v2/search/people, with the old pair documented as live only until 13 October 2026. | Change both paths in the middle layer. Gong separately warns that it may add JSON fields without notice, so a reader that ignores unknown fields survives both kinds of change. |

## What breaks, from the vendors' own docs

- **10,000 API calls a day, for the whole company.** Three a second and 10,000 a day, applied at company level rather than per integration, so the budget is shared with every other tool connected to Gong. A 429 carries Retry-After, and Gong states that support can change the limits if required.
- **Gong Enrich supports six providers and no others.** LeadIQ, Wiza, RocketReach, Lusha, ZoomInfo and Findymail, with email and phone kept in separate waterfalls that you order independently. Bring your own key applies per supported partner, so it changes the billing rather than the list.
- **Enrich stops at a job change rather than resolving it.** Before querying any partner, Gong checks whether the contact still works at the company on their record, and if they do not, or if it cannot match them to a company at all, enrichment stops and no credits are used. That is a sensible way to avoid paying for a dead record and it means the most valuable fact in the response is the one you never get.
- **A Gong credit is spent on an email you are not allowed to use.** Returned addresses are validated and a failing one is discarded, and Gong says the credit is still charged because the partner did return data. Reverse Contact's own Find Email refunds when nothing is found, so the two products disagree about what a miss is.
- **Enrich cannot be switched off once it is on.** Gong says that once you enable Enrich it cannot be disabled, although permissions for manual and automatic enrichment can be removed afterwards. It is also the one step here that an admin takes rather than a developer.
- **A partner already queried is skipped for 90 days.** Within 90 days Enrich skips data partners it has already asked about that contact, and after 90 days the full waterfall can run again. So a second attempt on a stale record is not the same operation as the first, which matters when somebody reports that Enrich again did nothing.
- **EU and California contacts can be excluded wholesale.** The enrichment controls carry settings to exclude people located in the European Union and people in California. Useful, blunt, and worth checking before anybody concludes that a region has no data.
- **A low balance on either side stops a different thing.** With no Gong credits, contact enrichment stops while account enrichment carries on, manual enrichment becomes unavailable and flows continue without enriching. With no Reverse Contact credits even the free check endpoints answer 402 NO_CREDITS, and GET /v2/usage keeps answering.

## The APIs, if you are building around it instead

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Gong: what the Gong API provides: https://help.gong.io/docs/what-the-gong-api-provides
- Gong API: introduction, auth and limits: https://help.gong.io/apidocs/introduction-2
- Gong: about Gong Enrich: https://help.gong.io/docs/about-gong-enrich
- Gong: about Enrich configuration: https://help.gong.io/docs/about-enrich-configuration
- Gong: configure Enrich: https://help.gong.io/docs/configure-enrich-1
- Gong: how Enrich consumes credits: https://help.gong.io/docs/how-enrich-consumes-credits
- Gong: enrich a contact: https://help.gong.io/docs/enrich-a-contact
- Gong: enrich contacts from a flow: https://help.gong.io/docs/enrich-contacts-from-a-flow
- Reverse Contact API documentation: https://docs.reversecontact.com/getting-started
- Reverse Contact: credits: https://docs.reversecontact.com/guides/credits
- Reverse Contact: rate limits: https://docs.reversecontact.com/guides/rate-limits
- Reverse Contact pricing: https://www.reversecontact.com/pricing
- 14 practitioner threads read on 2026-10-28, summarised on the page: https://www.reversecontact.com/integrations-hub/gong-integrations/gong-reverse-contact-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/gong-integrations/gong-reverse-contact-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
