---
name: salesforce-zoominfo-integration
description: Connect Salesforce and ZoomInfo: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, companies, lists. Use when the user wants to set up, audit or troubleshoot Salesforce and ZoomInfo together, or asks why data is not moving between them.
---

# Salesforce and ZoomInfo

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

**What you have to buy first:** ZoomInfo Sales with Enrich, the AppExchange package, and a Salesforce edition with API access

**What moves:** contacts, companies, lists, one way, into Salesforce.
**How it is built:** native, marketplace app. **Effort:** hours.

## The short version

This is the deepest enrichment integration in the directory and the one with the most ways to spend money you did not plan to. The capability is real: Instant Enrich fills a lead, contact or account as it is created, Scheduled Enrich keeps the back catalogue current, and you control matching, accuracy thresholds and field-level overwrite behaviour. What decides whether the project goes well is three documented details nobody mentions in a demo: a sandbox run charges credits exactly like production, the Person Has Moved setting rewrites employers unless you turn it off, and Instant Enrich spends two Salesforce API calls on every record it touches. That last allocation is shared with every other integration in the org, which is why this one usually gets discovered from somewhere else.

## What each enrichment mode costs you

Rows: Enrich mode. Columns: Environment. ZoomInfo quotes its editions rather than publishing them, so the grid that decides this project is not licence against licence. It is which enrichment mode you run against which environment, because both sides meter you and only one of them is obvious.

| Enrich mode | Production | Sandbox |
|---|---|---|
| Instant Enrich, on create | Two API calls per record | Credits charged anyway |
| Scheduled Enrich, 200 per batch | Most Bulk API calls | Credits charged anyway |
| Scheduled Enrich, 10K per batch | Fewest Bulk API calls | Credits charged anyway |

- **Two API calls per record.** ZoomInfo documents two Salesforce API calls for every record Instant Enrich touches as it is created. At form-fill volumes that is the line item people forget when they size their API allowance.
- **Most Bulk API calls.** The smallest batch size makes the most Bulk API calls for the same number of records. Choose it only if something in your org genuinely cannot take a larger transaction.
- **Fewest Bulk API calls.** The largest batch size makes the fewest calls and is the default choice unless you have a reason. The records enriched and the credits charged are identical either way.
- **Credits charged anyway.** A sandbox run consumes credits exactly as production does. There is no free rehearsal, so test with ten records rather than with a copy of the database.

Counted off that grid, of six pairings: one gives you two API calls per record, one gives you most Bulk API calls, one gives you fewest Bulk API calls, three give you credits charged anyway.

The two meters do not move together, which is the trap: tuning the batch size down to be gentle on one system spends more of the other, and neither shows up on the invoice you were watching.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| New leads, contacts and accounts | One way, in | Instant Enrich appends ZoomInfo data as the record is created, optionally filtered by a SOQL query so only the right teams' records are enriched. |
| Existing records | One way, in | Scheduled Enrich jobs run on a cadence over all records, a list view, or criteria you define. Jobs begin at 12:00 AM Eastern on the scheduled day. |
| Intent and Scoops | One way, in | Written to a ZoomInfo custom object rather than onto the standard record. |
| Buying committee contacts | One way, in | Creates and enriches new contacts on matched accounts, charged as credits and reported separately on the dashboard. |
| Anything back to ZoomInfo | One way, out | Nothing on this integration. Enrich is a one-way pipe into Salesforce. |

## Which field lands where

Mapping here is explicit and per field, which is unusually controllable. The thing to understand is not where a field lands but whether it is allowed to overwrite what is already there.

| In Salesforce | In ZoomInfo | What to know about the match |
|---|---|---|
| A ZoomInfo data point | Any Salesforce field, custom included | Chosen row by row, so nothing lands anywhere you did not pick. |
| Update Option | Overwrite, or complete only if missing | Set per mapping. This single column is the difference between enrichment that reps trust and enrichment they work around. |
| Intent and Scoops | A ZoomInfo custom object | Deliberately not written onto the standard record, so your reporting has to reach into the custom object to use them. |
| Buying committee contacts | New contacts on the matched account | Created rather than matched, and chargeable. A hard limit of up to 10 contacts per account is available and worth setting. |
| Anything at all | Back to ZoomInfo | Nothing. Enrich is a one-way pipe into Salesforce, so your corrections stay yours and never improve the source. |

**What does not cross:**

- Any record below your accuracy threshold. It is marked No Match with the reason given, which is a feature rather than a gap.
- A contact with no account relationship, usefully. Salesforce treats an account-less contact as private to its creator, so a created contact that lands without an account is invisible to the rest of the team.
- Anything flowing back. There is no return path, so a field a rep corrects is corrected only in Salesforce.

## Connect it, in this order

**Who has to do it:** A Salesforce admin who can install a package, and a ZoomInfo admin with the Admin Portal. Plus one dedicated Salesforce user that nobody logs in as.
**How long:** An hour to connect. The field mapping and the accuracy threshold are the decisions, and they deserve a meeting.

### 1. Install the package, and pick the environment deliberately

*Where:* Salesforce AppExchange: ZoomInfo, GTM Intelligence Platform

Click Get It Now and choose Production or Sandbox. ZoomInfo documents that running Enrich in a sandbox still consumes credits, so a sandbox trial is a real purchase rather than a free rehearsal.

### 2. Create a Salesforce user that exists only to run Enrich

*Where:* Salesforce: Users

ZoomInfo asks you to connect as a user dedicated to Enrich. That user's permissions become the integration's permissions, and a named person's account takes the integration down with them when they leave.

### 3. Connect from the ZoomInfo side

*Where:* ZoomInfo Admin Portal: Integrations, Connect Enrich

Under Scheduled Enrich, click Connect on the Salesforce tile, choose the environment and click Grant Access. The authorisation opens in a popup, so a popup blocker makes this look like a failed connection rather than a blocked window.

### 4. Create one job per object, not one job for everything

*Where:* Admin Portal: Manage, New Job

A job takes a single Object Type of Accounts, Contacts or Leads. Name it, decide whether you want email alerts, and set the recurrence; jobs start at midnight, so a daily job is an overnight job.

### 5. Set a credit limit on the job before you run it once

*Where:* The job: Credit Usage Limits

The default is No limit, which enriches every record in the run and charges for all of it. Limiting credits per job run is the setting that turns a misconfigured filter into a small mistake instead of a month of budget.

### 6. Choose the batch size with your Salesforce API allowance in mind

*Where:* The job: Batch Size

The options are 10K, 1K, 500 and 200 records per Bulk API call. A larger batch means fewer calls; reducing it increases Salesforce API consumption, which matters because that allowance is shared with every other integration in the org.

### 7. Set the accuracy score, and agree the number with whoever reads the dashboard

*Where:* The job: Accuracy Score for Enrichment

Records matched below the threshold are not enriched and are marked No Match with the reason Below selected Accuracy Score. That is a better outcome than a confident guess, and it is also the number somebody will use to judge the integration later.

### 8. Map fields last, and decide overwrite per field

*Where:* The job: field mapping

Each row pairs a ZoomInfo field with a Salesforce field, custom fields included, and each has an Update Option of overwrite or complete only if missing. Default to complete if missing on anything a human types into.

Two of those eight are the whole project: the credit limit, which caps the downside, and the overwrite option, which decides whether reps keep trusting the record.

## How to check it worked

- Run one job against a filtered list of ten records and read the credit charge before scheduling anything recurring.
- Check a record that came back No Match and confirm the reason reads Below selected Accuracy Score rather than something else.
- Pick a field a rep typed into and confirm it survived the run. If it did not, the Update Option on that mapping is wrong.
- Watch your Salesforce API consumption over the first full cycle, not the first job. Batch size and Instant Enrich both draw on the same allowance as everything else in the org.

## 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 |
|---|---|---|
| The connection window never appeared | A popup blocker. ZoomInfo opens the Salesforce authorisation in a popup and says so. | Disable the blocker for the Admin Portal and reconnect. Nothing is wrong with the credentials. |
| Credits went in a single run | Credit Usage Limits defaults to No limit, so the job enriched every record it matched. | Set a per-run credit limit before the next schedule, and test any new filter against ten records first. |
| Created contacts are invisible to everybody except one user | A Salesforce contact with no account relationship is private to its creator, which is Salesforce behaviour rather than ZoomInfo behaviour. | Make sure created contacts attach to an account. Practitioners use a placeholder account everyone can see, or route to the Lead object instead. |
| Records come back as No Match in bulk | They matched but fell below the accuracy threshold, and the reason field says so. | Read the reason before lowering the threshold. A lower score buys coverage with confidence, and that trade should be a decision rather than a reflex. |
| Reps say the data is wrong and they fixed it last week | An Update Option set to overwrite on a field people type into, or Person Has Moved rewriting an employer. | Switch those mappings to complete only if missing, and check the Person Has Moved setting, which is on unless somebody turned it off. |
| Other integrations in the org started failing | Salesforce API consumption. Instant Enrich costs two calls per record and a small batch size multiplies scheduled calls, all drawn from one shared daily allowance. | Raise the batch size, narrow the job filters, and check the org's API usage rather than ZoomInfo's job log, because the failure appears somewhere else entirely. |
| A feature in the guide is missing from your org | Some capabilities need the ZoomInfo Sales native application at version 1.33 or higher. | Upgrade the AppExchange package before raising a support ticket about a missing screen. |

## What breaks, from the vendors' own docs

- **The sandbox is not free.** ZoomInfo states that running Enrich in a Salesforce sandbox incurs bulk credit charges in the same way as production, and recommends testing in small batches. Teams used to rehearsing data projects against a full sandbox copy should not do that here. Size your test as a sample, and get your implementation specialist involved before any job points at the whole database.
- **Person Has Moved rewrites employers by default.** The setting is enabled unless you turn it off, so a contact who changed jobs is enriched to their new organisation inside your CRM. Turn it off and the company fields are still enriched as though no move happened, with the enrich status set to Company Match Only. Either choice is defensible; not making the choice means your CRM quietly disagrees with your historical reporting about who worked where.
- **Instant Enrich costs two API calls a record.** ZoomInfo documents two Salesforce API calls per record enriched: one to read the existing field values so the update option can be honoured, and one to write. Salesforce allocates 100,000 requests plus 1,000 per Salesforce licence per 24 hours on Enterprise and on Professional with API access, shared across every integration in the org, so a busy inbound week is measurable against that number rather than invisible.
- **A smaller batch size costs more API calls.** Scheduled Enrich queries through the Bulk API in batches of 10,000 by default, and you can reduce that to 1,000, 500 or 200. ZoomInfo is explicit that reducing it increases Salesforce API consumption. The instinct to be gentle on the org by shrinking batches therefore does the opposite, and the right lever for caution is the credit limit per job run, not the batch size.

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

### Salesforce

- **Base:** `https://{instance}.my.salesforce.com/services/data/v60.0`
- **Auth:** OAuth 2.0 through a connected app. **API access is an edition feature**: editions without it cannot run any of this.

| Call | Request | What it does |
|---|---|---|
| `PATCH /sobjects/Contact/{id}` | `{ "RC_Title__c": "VP Sales" }` | Update a record. Custom fields carry the __c suffix. |
| `POST /composite/sobjects` | `{ "allOrNone": false, "records": [...] }` | Batch up to 200. `allOrNone: false` so one bad row does not roll back the batch. |
| `GET /query?q=SELECT+Id,Email+FROM+Contact+WHERE+Title=null` | - | SOQL for the filtered slice. |

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

- **Validation rules, required fields, duplicate rules and Apex triggers all apply to your writes.** A completed run is not a successful write. Read the per-record errors.
- **The daily API allocation is shared across the whole org**, set by edition and licence count. A row-by-row job competes with every other integration; the symptom of exhausting it is other people's integrations failing.
- Test in a sandbox with ten records before production. The rules you will hit were written years ago by somebody who has left.
- Installing anything usually needs Modify Metadata, Download AppExchange Packages and Customize Application. That is an admin on their own schedule.

Docs: https://developer.salesforce.com/docs/apis

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### 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

- ZoomInfo: Enrich for Salesforce integration guide (PDF): https://tech-docs-library.zoominfo.com/enrich-for-salesforce-integration-guide.pdf
- Salesforce developer limits and allocations quick reference (PDF): https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-zoominfo-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-zoominfo-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.*
