---
title: "Salesforce and Outreach integration: what syncs, and what it needs"
description: "Salesforce and Outreach: what moves, in which direction, which plan carries it, and the limits that bite. Verified October 2026."
url: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-outreach-integration
format: markdown twin of the page above, generated at build time
---

New Unlimited plans are here. Fetch, search and enrich without counting credits. [See plans →](https://www.reversecontact.com/integrations-hub//pricing#plans)

Reverse Contact

### Products

Data

People Data

Company Data

Our Data Quality Standard

Delivery methods

API

Webhooks

CSV Enrichment

MCP

CLI

Integrations

### Use cases

[Sales Product](https://www.reversecontact.com/integrations-hub//use-case/sales-products)[Recruiting Product](https://www.reversecontact.com/integrations-hub//use-case/recruiting-products)[Internal Data Teams](https://www.reversecontact.com/integrations-hub//use-case/internal-data-teams)[AI Products](https://www.reversecontact.com/integrations-hub//use-case/data-for-ai)[CRM Enrichment](https://www.reversecontact.com/integrations-hub//use-case/crm-enrichment)

### Features

[Email Finder API](https://www.reversecontact.com/integrations-hub//feature/email-finder-api)[Phone Number Enrichment](https://www.reversecontact.com/integrations-hub//feature/phone-number-enrichment)[People Search API](https://www.reversecontact.com/integrations-hub//feature/people-search-api)[Agentic Search API](https://www.reversecontact.com/integrations-hub//feature/agentic-search-api)[People Lookalike API](https://www.reversecontact.com/integrations-hub//feature/people-lookalike-api)[Company Search API](https://www.reversecontact.com/integrations-hub//feature/company-search-api)[Person Enrichment API](https://www.reversecontact.com/integrations-hub//feature/person-enrichment-api)[Company Enrichment API](https://www.reversecontact.com/integrations-hub//feature/company-enrichment-api)[Person Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-person-api)[Company Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-company-api)

Security

Pricing

Docs

[Log in](https://app.reversecontact.com/auth/login) [Book a demo](https://www.reversecontact.com/contact?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header) [Start for free](https://app.reversecontact.com/auth/signup?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header)

# Salesforce and Outreach

Featured

Per-object, per-field control in both directions, and Essentials cannot run it at all.

Checked by **Reverse Contact** · Verified 2026-10-11 · No paid placement

## What you have to buy first

An Outreach contract, a Salesforce edition with REST API calls, and a Salesforce admin

## What moves

Contacts, Companies, Deals, Activities, two-way sync.

This is the integration Outreach was built around, and it shows: per-object polling, per-field outbound toggles, conditions on what pushes and manual stage mapping. It is also the one project on this site where the connector is the easy part. The edition question comes first and is absolute, because Essentials has no REST API access even with an add-on and Professional has to buy the Web API package, and behind it sit the permissions, the sandbox and the admin's change window. Budget days rather than hours, and spend the first of them on the API allocation rather than on field mapping.

## What actually syncs

Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.

| What | Direction | What that means in practice |
| --- | --- | --- |
| Leads, contacts and accounts | Both ways | Salesforce is the source of truth for creation. Updates run both ways, with outbound update enabled only on the fields you choose. |
| Opportunities | Both ways | Bidirectional where in-line editing is on. Without it, Outreach recommends every push and outbound toggle off, so updates happen in Salesforce only. |
| Opportunity contact roles | Both ways | Including outbound delete, which few integrations in this directory will do at all. |
| Tasks, calls and emails | One way, out | Always one way, Outreach into Salesforce. Outreach recommends conditions so only completed or delivered activity pushes. |
| Events | One way, out | One way, which is why polling does nothing for them. Condition them or a connected calendar pushes historical internal meetings. |
| Users | One way, in | Updates in only, with polling off. Polling here imports every CRM user, and a user cannot be deleted afterwards. |

Three of those six rows move in both directions. The three that do not are Tasks, calls and emails, Events and Users, and those are the rows that decide how you design around this rather than the ones in the brochure.

## Which field lands where

Mapping is explicit and per object, and the behaviour that matters is not where a field lands but what happens when both systems change it at once.

| In Salesforce | In Outreach | What to know about the match |
| --- | --- | --- |
| Accounts, contacts, leads, opportunities | `The Outreach equivalents` | Create, read and edit, bounded by the integration user's profile and field-level security. |
| A field changed on both sides at once | `A field-by-field merge` | Outreach scans the record field by field rather than taking a row lock or letting one system win wholesale. |
| Completed activity in Outreach | `Salesforce, in near real time` | Usually visible in 30 to 45 seconds, slower during a high-volume force sync. |
| New and updated Salesforce records | `Outreach, in bulk` | Polling detects up to 2,000 changed records in one API call and imports 200 per call after that, which is a Salesforce limit rather than an Outreach choice. |
| The whole sync configuration | `An exportable file` | Importable into another environment, which is the supported route from sandbox to production. |

### What does not cross

Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.

- Anything the integration user cannot see. Field-level security on that profile is the ceiling for the entire plugin.
- Anything historic. Nothing backfills, so the go-live date is a decision rather than a detail.
- Any object on Salesforce Essentials, which has no REST API access even with an add-on.

Every row above travels as a file: five field mappings and three documented exclusions, each one's note, and the three vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.

The import rate is the number to plan around: 2,000 changed records costs eleven API calls, so a bulk update in Salesforce is an API event in Outreach whether or not anybody meant it to be.

## Which Salesforce edition carries this

Outreach sets no tier of its own on the integration, so the grid has one column. The Salesforce side decides everything, and it decides it on API access rather than on features. Pick one on each side and the grid marks the answer.

| Salesforce edition | Any Outreach contract |
| --- | --- |
| Essentials | Not possible |
| Professional | Needs the API package |
| Enterprise or Unlimited | REST API included |

- **Not possible** — Outreach states that Essentials does not support REST API access even with an add-on. There is no configuration and no purchase that makes this work.
- **Needs the API package** — Professional requires the Web API package and purchased API call bundles. Price those before you price the seats, because the call volume below is what you will be buying against.
- **REST API included** — REST API is included, and the only remaining question is your daily allocation against everything else connected to the org.

Counted off that grid, of three pairings: one gives you not possible, one gives you needs the API package, one gives you REST API included. The top row is the one worth saying out loud in a procurement meeting: on Essentials this integration cannot be bought at any price, which is unusual enough that people assume it is a configuration problem.

## How to connect Salesforce to Outreach

Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.

- **Who has to do it** — A Salesforce administrator, connecting as a dedicated integration user rather than as themselves.
- **How long it takes** — A day to connect and map. Longer if nobody has agreed which fields Outreach is allowed to own.

Salesforce Setup: Company Information, Organization Edition

Outreach is explicit: Enterprise and Unlimited include REST API; Professional needs the Web API package and purchased API call bundles; Essentials does not support REST API access even with an add-on. The last one ends the project rather than delaying it.

Salesforce: profile and user

That profile needs create, read and edit on every object Outreach will show, including accounts, contacts, leads, opportunities and user roles, field-level security that permits viewing and modifying every mapped field, and API Enabled under System Permissions. The last one is the single most common thing missing.

Outreach: the Salesforce plugin

Outreach lists admin credentials as a common connection error for a reason. Connect to the sandbox or production deliberately, and know which you are on before you start mapping.

The plugin: Limits

An admin can cap how many calls Outreach may make per day. Outreach recommends setting global usage to 70 to 80 per cent of your total allocation, which leaves room for every other integration drawing on the same org.

The plugin: Object Setup, Set Field Mapping

This is the bulk of the work and the part that decides whether reps trust either system. Conflict resolution scans field by field rather than locking a row, so a field both sides write to will flip rather than fail, which is harder to notice.

The plugin: the three dots, Export CRM Sync Configuration

Outreach supports exporting and importing the sync configuration, which is how you move a validated setup from sandbox to production and how you recover one after a sandbox refresh. Doing it at the end of a good day is cheaper than rebuilding it after a bad one.

The order protects two things that are expensive to retrofit: the integration user, which decides what the plugin can ever see, and the API budget, which decides whether it takes the org down with it.

Hand it to an agent instead

The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at [this pair as a skill](https://www.reversecontact.com/integrations-hub/skills/salesforce-outreach.md) and it has the whole pair without reading two sets of vendor docs first.

curl -o .claude/skills/salesforce-outreach/SKILL.md https://www.reversecontact.com/integrations-hub/skills/salesforce-outreach.md

## What breaks, and what nobody tells you

Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.

- **Essentials cannot run this, at any price** — Outreach documents that Enterprise and Unlimited include the REST API calls the sync needs, that Professional requires the Web API Package and API Call Bundles, and that Essential has no REST API access even with an add-on. Confirm the edition in Setup, Company Information before anything else, and ask your Salesforce representative rather than reading API usage statistics, because usage figures do not reveal whether the package was purchased.
- **Polling Users is a one-way door** — Outreach recommends leaving polling off for the User object, because polling imports every user in the CRM and a user cannot subsequently be deleted from Outreach. The same advice applies to Leads until setup is complete. This is the clearest example on the pair of a default that is cheap to get right and expensive to undo.
- **The API allocation is a budget you have to set** — Outreach advises setting the global API limit to 70 to 80 percent of your total calls and the Outreach-specific limit to 20 to 30 percent, and notifies admins as the limit approaches. When the limit is reached, syncing stops, and the window is a rolling 24 hours rather than a daily reset at midnight. Salesforce allocates 100,000 calls plus 1,000 per Salesforce licence on Enterprise, shared with every other integration in the org.
- **Nothing backfills, and conflicts resolve per field** — Only new and updated records move during polling, so history needs a separate import and your switch-on date is the start of the record. Conflicts are resolved field by field rather than by a winning system, which means the governance question is per field too: decide which side owns each one before you enable an outbound toggle, because the connector will implement whatever you hand it.

Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.

## The 6 failures people actually hit

Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.

### The connection refuses admin credentials

WhyOutreach lists this first among connection errors: the credentials used must be a Salesforce administrator, for sandbox and production alike.

Connect with an admin account, ideally the dedicated integration user rather than a person.

### The connection drops every day or two

WhySalesforce session timeout settings, which Outreach calls out specifically for sandboxes breaking every 24 to 48 hours.

Check the session timeout in Salesforce rather than reconnecting repeatedly, which treats the symptom.

### Records sync for some users and not others

WhyIncorrect user mappings, one of the five errors Outreach lists as common, alongside unmapped lead queues.

Open the plugin logs, which export the last 10,000 errors, and fix the mappings rather than the records.

### Writes fail with no obvious pattern

WhyValidation errors or required fields missing on the Salesforce side, which the plugin surfaces rather than the record does.

Filter Activity by System Update, Plugins, Plugin Sync Error. The failures are there and nowhere else.

### A field keeps changing back

WhyBoth systems are writing it. Conflict resolution merges field by field, so the last writer wins quietly rather than erroring.

Decide an owner for that field and stop one side writing it. Nothing in the plugin will flag the fight.

### The org ran out of API calls overnight

WhyAn unbounded Outreach budget against a shared allocation, often triggered by a bulk change in Salesforce that the poll then imported 200 records at a time.

Set the limit to 70 to 80 per cent of total as Outreach recommends, and treat large Salesforce updates as API events in their own right.

If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The [same symptom on another pair](https://www.reversecontact.com/integrations-hub/errors) is often the same cause, so the directory indexes all of them by the message rather than by the integration.

## When this is the right integration

### Set it up when

- Salesforce is the system of record and Outreach is where reps work
- You need per-field control over what leaves the CRM
- Activity has to appear on the opportunity, not in a second tool

### Do not bother when

- Your edition is Essentials, or Professional with no API package
- There is no Salesforce admin time in the next few weeks
- Nobody has decided which system owns which field

The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.

## What practitioners say about it

Searched for this pair by name, in the words a person would use. 14 threads from 2022 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.

### Troubleshooting it is a known rite of passage

> I had never experienced incandescent rage in a professional context until trying to troubleshoot an Outreach integration issue.

[r/salesforce](https://www.reddit.com/r/salesforce/comments/1aljthd/anyone_here_a_salesforce_admin_that_also/) · February 2024 · 5 points

The rest of that comment describes the integration consuming something overnight, which is exactly what the API budget setting exists to bound. Set it on day one and this class of incident becomes a throttle rather than an outage.

### The admins who inherit it struggle, and say so publicly

> Lordy lord I struggle with this platform and its ratchet integration. Anyone here has to admin both platforms and feels like they have got it figured out?

[r/salesforce](https://www.reddit.com/r/salesforce/comments/1aljthd/anyone_here_a_salesforce_admin_that_also/) · February 2024 · 11 points

Worth reading as a staffing signal rather than a product verdict. This integration has a documented setup path and a real configuration surface, and the people struggling with it are usually the ones who did not build it.

### The alternatives people name are native rather than API-based

> We may be switching to Groove for a similar reason to yours. Groove is native to Salesforce rather than api. makes for much more efficient data

[r/salesforce](https://www.reddit.com/r/salesforce/comments/yjq95n/outreach_salesforce_integration_fix/) · November 2022 · 5 points

The architectural point behind every other complaint here. An API integration spends your allocation and a native package does not, which is why the API budget is the first setting to configure and the first thing to look at when something breaks.

### Salesforce now competes with the thing it is integrating

> Have you tried Sales Engagement native to Salesforce? That is on my next sprint to replace cadences in outreach since Salesforce announced it comes free as part of the Sales Cloud

[r/salesforce](https://www.reddit.com/r/salesforce/comments/zy8nlw/outreach_or_salesloft_whats_your_experience/) · December 2022 · 6 points

Worth knowing before a renewal, and worth checking against your own contract rather than a 2022 comment. The comparison this page supports is narrower: what the integration does, what it costs in API calls, and what it cannot do at all.

### Where reps actually work is a design decision, not an accident

> generally in the enterprise, AEs will only use Outreach for the cadence functionality on a personalized, account-driven process. BDRs will operate with ABI or territorial information and utilize a low touch sequence

[r/salesforce](https://www.reddit.com/r/salesforce/comments/ytmbm7/how_does_your_sales_team_use_outreach_whats_best/) · November 2022 · 5 points

Useful when deciding which fields each system owns. If AEs live in Salesforce and BDRs live in Outreach, the field-by-field conflict resolution above is resolving a disagreement between two teams rather than two tools.

What the threads add up to

This is the angriest set of threads in the directory. Salesforce admins who inherited Outreach describe the integration as the hard part of the platform, and the specific failure they describe is the one the documentation tells you to prevent: an API allocation consumed overnight. The alternatives people reach for are consistently native-to-Salesforce rather than API-based, which is a comment on the architecture rather than on the product.

Every complaint in those threads maps onto a setting in the setup list, which is the encouraging reading: this integration is configurable enough to be got wrong, and the documentation says how.

## The longer answer

The reason this takes days is almost never the integration. Installing it is short; the queue in front of it is not. You need an administrator with Modify Metadata and Customize Application, a sandbox to test the write path, and a change window, and in most companies those sit with three different people.

Teams that treat this as a RevOps task and discover the dependency in week two lose a fortnight, and nothing about that is technical difficulty. Book the admin before you book the kickoff.

The second thing worth doing before any field mapping is arithmetic on the API allocation. Salesforce gives an Enterprise org 100,000 calls plus 1,000 per Salesforce licence in a rolling 24 hours, and every integration in the org draws on it. Outreach will happily take a configured share and stop syncing when it reaches the ceiling, which is the correct behaviour and a confusing symptom: the thing that breaks is often somebody else's connector failing, not yours. Agree the split, set the limits Outreach recommends, and write down who gets the alert.

Everything after that is governance wearing the costume of configuration. Conflicts resolve field by field, which sounds like a feature and is really a question: for each field both systems can write, which one wins. Three steps answer it:

- Decide on paper, for the dozen fields that actually matter, which system owns each one.
- Enable outbound updates only on those fields, and only in the direction you chose.
- Leave everything else reading from Salesforce, so there is nothing to resolve.

The pairs in this directory that go badly are almost never the ones with thin feature sets. They are the ones where two systems were given permission to write the same field and nobody chose, which is why the [HubSpot pairing](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-outreach-integration) is a useful contrast: it offers much less control and therefore far fewer ways to get this wrong.

## If this is not the one

The integrations people compare this against, or set up alongside it.

Split a stack into layers and this pair sits on two of them: the [CRM layer](https://www.reversecontact.com/integrations-hub/stack/crm), which 33 of the 68 integrations here touch, and the [engagement layer](https://www.reversecontact.com/integrations-hub/stack/engagement), which 20 do.

[**HubSpot and Salesforce**Two CRMs, one connector, and an edition requirement on both sides. Two-way sync](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-salesforce-integration)[**HubSpot and Outreach**Contacts both ways, email one way, and HubSpot rather than Outreach owns it. Two-way sync](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-outreach-integration)[**Salesforce and LinkedIn**The original CRM Sync target, with the same Advanced Plus gate. Two-way sync](https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-linkedin-integration)

## [Reverse Contact](https://www.reversecontact.com)

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. [What has changed since](https://www.reversecontact.com/integrations-hub/changes) · [How we checked](https://www.reversecontact.com/integrations-hub/methodology), and what we will not claim

[Eugene Suslov](https://www.linkedin.com/in/eysuslov/)

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

- **Verified** — 2026-10-11
- **Sources** — 3 vendor documents
- **Paid placement** — None

### Read from

- [Outreach support: Salesforce configuration for Outreach, end to end guide](https://support.outreach.io/support/solutions/articles/159000426522)
- [Outreach support: Outreach and CRM connection overview](https://support.outreach.io/support/solutions/articles/159000426014)
- [Salesforce developer limits and allocations quick reference (PDF)](https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf)

## Salesforce and Outreach, asked and answered

### Which Salesforce edition do I need for Outreach?

The sync runs on the REST API, so the edition has to carry API calls. Outreach documents that Enterprise and Unlimited include them, that Professional Edition requires the Web API Package and API Call Bundles, and that Essential has no REST API access even with an add-on. That last line ends the evaluation for some teams before any feature discussion starts. Check Setup, Company Information for your edition, and note that API usage statistics will not tell you whether the add-on was ever purchased.

### What permissions does the connecting user need?

The Outreach admin who connects the plugin needs create, read and edit access on every object shown in Outreach, including Accounts, Contacts, Leads, Opportunities and User Roles, field-level security that lets the profile view and modify every mapped field, and the API Enabled system permission. The profile also has to carry a licence of type Salesforce. Connecting production or a sandbox needs a Salesforce administrator login, so this is a change window rather than an afternoon.

### How often does it sync, and can I change it?

Polling defaults to ten minutes and is adjustable per object. Outreach detects up to 2,000 changed records per API call and imports 200 per call, and changes made in Outreach usually appear in Salesforce within 30 to 45 seconds. Only new and updated records move during polling; history needs a separate import. Outreach recommends leaving polling off for Users entirely, and off for Leads until setup is finished.

### Do tasks and meetings sync both ways?

No, and this is the most misread part of the configuration. Task syncing is always one way, from Outreach into Salesforce, and events are one way too, which is why polling does them no good. Outreach recommends conditions on both so that only completed or delivered activity pushes, and so that connecting a rep's calendar does not flood Salesforce with every historical internal meeting they have ever held.

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant
