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

# Outreach and Reverse Contact

> Generated from https://www.reversecontact.com/integrations-hub/outreach-integrations/outreach-reverse-contact-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:** A Reverse Contact API key and Outreach API access through an OAuth app

**What moves:** contacts, companies, one way, into Outreach.
**How it is built:** built on the api, zapier, make or n8n. **Effort:** hours.

## The short version

Outreach is the easiest sequencer in this directory to enrich against, and the reason is mundane: the rate limit is 10,000 an hour per user rather than a shared team budget, so a backfill over an existing prospect list is an ordinary thing to do rather than a negotiation. There is nothing to install, which is consistent with how Reverse Contact ships everywhere, and the real work is deciding what happens to a prospect whose lookup returned null before a cadence picks them up.

## How the five sequencers here meter the same enrichment

Rows: The sequencer. Columns: What that means for you. The build is nearly identical on all five: read the record, call the API, write it back. What differs is the metering, and the differences are large enough to change whether a backfill is an evening or a negotiation. Every figure below is from the vendor's own rate-limit documentation.

| The sequencer | The budget is yours rather than shared | A full backfill is an ordinary thing to do | No documented surcharge for deep paging | The key travels in a header, not a URL |
|---|---|---|---|---|
| Outreach: 10,000 an hour, per user | Yes | Yes | Yes | Yes |
| Salesloft: 600 cost a minute, per team | No | Partly | No | Yes |
| Smartlead Standard: 1,000 an hour, per key | Partly | No | Yes | No |
| lemlist: 20 per 2 seconds, per key | Partly | Partly | Yes | Yes |
| Instantly: 6,000 a minute, per workspace | No | Yes | Yes | Yes |

- **Yes.** Documented and unambiguous. Outreach meters per user, which means your enrichment credential has its own 10,000 an hour and does not compete with the dialler; Instantly publishes 6,000 a minute, which is enough that batching is politeness rather than necessity.
- **Partly.** True with a condition. Smartlead and lemlist meter per API key, so the budget is yours only in the sense that you hold the key, and both are small enough that a parallel worker will find the ceiling. Salesloft allows a backfill if you use a cursor poller on updated_at and not if you page deeply.
- **No.** Not true on that one. Salesloft's 600 cost a minute is a team budget and it says explicitly that one integration can affect another's; its page costs rise to 30 points past page 500; and Smartlead documents authentication as api_key in the query string, which URLs get logged.

Counted off that grid, of twenty pairings: eleven give you yes, four give you partly, five give you no.

The top row is why this page exists in the shape it does: on Outreach the metering is nobody else's business and a backfill is an afternoon. Salesloft meters per team instead and charges more for deep pages, which turns the identical build into a scheduling problem, and the last column is a reminder that the easiest API to call is not always the safest place to put a key.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| Trigger | One way, out | A webhook on prospect created, or a scheduled sweep over prospects missing a title. |
| The enrichment | One way, out | POST /v2/enrich/persons with the prospect email. 2 credits on a match, free for a prior freshness check. |
| Write-back | One way, in | PATCH the Outreach prospect with title, company, seniority and whatever else the schema holds. |
| Cadence entry | One way, in | Gate it on the enrichment having resolved, so an unknown prospect does not get the generic first touch. |

## Which field lands where

There is nothing to map in Outreach, because there is no app: a middle layer reads the prospect, calls Reverse Contact and PATCHes the answer back. What is worth laying out is which part of the response goes where, and which part of it should stop the send instead.

| In Outreach | In Reverse Contact | What to know about the match |
|---|---|---|
| Prospect emails | POST /v2/enrich/persons, 2 credits | Identity, the current role, history, education, skills and location on one schema. A miss returns null with a confidence score and costs nothing at all, because every 4xx and 5xx is free. |
| Account domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain or a company name. Run it on the account rather than once per prospect attached to it, which is both cheaper and more consistent. |
| A profile URL already on the prospect | POST /v2/fetch/persons, 1 credit | Half the price, and unmetered from the $249 plan rather than the $699 one. Prospects sourced from a profile rather than from a form often already carry one. |
| currentPosition.title | Prospect title, in a custom field | The field most cadence openers reference, and the one most likely to be out of date on a list built six months ago. |
| currentPosition.companyName | A suppression check, not a field | Compare it with the account the prospect is filed under. A disagreement is the single most useful signal on this page: that person has moved, and the cadence written for their old job is about to reach their new one. |
| metadata.updatedAt | A custom date field | When the record was last updated. Store it, and the next sweep can skip everything refreshed recently instead of paying to re-resolve it. |
| Prospect update | PATCH /api/v2/prospects/:id | One request against a limit of 10,000 an hour per user. Write the custom fields and leave the rep-maintained ones alone. |
| Anything outbound to Reverse Contact | Only what your middle layer sends | This is a read layer. No prospect, cadence or activity is sent anywhere, and there is nothing in the product to send it to. |

### The fields that should stop a send rather than improve one

Every page in this directory treats an enrichment response as a set of values to write. On a sequencer it is also a set of reasons not to send, and that is the half nobody builds. Each row below is a documented field in the response, and each one is a prospect who should leave the cadence rather than receive a better-personalised version of it.

| In the response | Why it is a reason not to send |
|---|---|
| isInRemembrance | The person has died. No amount of personalisation makes this email acceptable, and it is the one failure in outbound that cannot be apologised for |
| currentPosition.companyName disagrees with the account | They have changed job. The cadence was written for the old role and the pitch no longer applies, so this is a re-qualification rather than a refresh |
| isOpenToWork | They are looking to leave. Treat it as a reason to check the opener rather than an automatic stop, but it is a judgement a human should make once |
| data is null, with a confidence score | Nothing was confidently matched. Sending the fallback text is a choice, and on a cold list it is usually the wrong one |
| metadata.updatedAt, from a long time ago | The record is stale rather than wrong. This is the case for a 2-credit live refresh, and the only case for one |
| hasVerificationBadge and followersCount | Not suppression. Worth noting because they are the two fields teams reach for as a seniority proxy, and neither is one |

**What does not cross:**

- An app inside Outreach. There is no listing and nothing in the product that calls an external API, which is consistent with Reverse Contact maintaining apps on Clay, Zapier and Make and nothing inside any CRM or sequencer.
- A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and the email finder is asynchronous.
- Anything that repairs an email already sent. A sequencer renders at send time, so enrichment after cadence entry improves later steps and nothing before them.
- The Kaia endpoints, which are a different product with their own limits: 3 API calls a second and 6,000 a day, applied at org level rather than per user.

## Connect it, in this order

**Who has to do it:** Somebody who can register an OAuth app in Outreach, plus whoever hosts the middle layer and whoever can create a Reverse Contact API key.
**How long:** A day. The OAuth app is the slow part and the enrichment itself is an afternoon.

### 1. Decide where enrichment sits relative to cadence entry, because it cannot be undone

*Where:* Your own process, not a settings screen

A sequencer renders the first touch from whatever the prospect record holds at send time. Enriching somebody already two steps into a cadence improves the fourth email and cannot repair the first, which is the one that decided the reply. Everything else on this page is reversible and this is not.

### 2. Decide which prospect fields the enrichment owns

*Where:* Outreach: custom fields on Prospect

Use custom fields rather than the ones a rep edits between calls. A sequencer is the one place in a stack where a wrong value is not merely untidy: it is sent to somebody, with your name on it, and no later correction reaches them.

### 3. Register an OAuth application and ask for the narrowest scopes

*Where:* Outreach: the developer portal

There is no app to install and nothing in Outreach that calls an external API, so the only way in is the API itself. Reading and writing prospects needs prospects.read and prospects.write; asking for more is a conversation with whoever approves it.

### 4. Read X-RateLimit-Limit from a live response rather than hard-coding the number

*Where:* Any Outreach API response

The documented limit is 10,000 requests an hour per user, and Outreach states in as many words that it reserves the right to adjust limits at any time. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, the last aliased as Retry-After.

### 5. 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 an existing prospect list spends 2 credits only on the records that need it. On a list of any size this is the difference between a budget and a bill.

### 6. Write the suppression rule before the enrichment rule

*Where:* Your middle layer

The response carries more reasons not to send than reasons to send. A current employer that disagrees with the account on the prospect, an isInRemembrance flag, an isOpenToWork flag: each one is a prospect who should leave the cadence rather than receive a better version of it.

### 7. PATCH the prospect, then let the cadence pick it up

*Where:* Outreach: PATCH /api/v2/prospects/:id

Update the record first and add to the cadence second, in that order, every time. The sequence of those two calls is the whole content of this build, and getting it the other way round is the mistake step one is about.

### 8. Run a hundred prospects before you run the list

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

At 10,000 an hour per user you have room to be careless, which is its own hazard. A hundred-record pass tells you the real resolved rate on your own list, and that number rather than any published match rate is what decides whether the rest is worth running.

Only the first step is irreversible and it is the one with no screen attached to it. Outreach makes the mechanics easy enough that the ordering question is the entire design, which is the opposite of [the Salesloft version](pair:salesloft+reverse-contact), where the shared rate limit decides what is possible before anybody argues about ordering.

## How to check it worked

- Enrich one prospect, then look at the rendered preview of the first cadence step for that person. The preview is the only place you see what the recipient will see, and it is where a fallback that reads badly becomes obvious.
- Run the free check on a prospect you know is current and read the update date. If it is recent, a 2-credit live refresh buys you nothing, and knowing that on one record saves it on thousands.
- Enrich somebody whose current employer differs from the account they are filed under, deliberately. Your suppression rule should pull them out of the cadence, and this is the one test that proves the rule exists.
- Read X-RateLimit-Remaining after a hundred-record pass. That number against the hour tells you whether a full backfill is one sitting or several, and it is per user, so it is yours rather than the team's.

## 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 first email went out with the old job title in it | A sequencer renders each step from the record as it stands at send time, and the prospect was added to the cadence before the enrichment ran. | Enrich first, add to the cadence second, with no exceptions. Nothing repairs a sent email, which is why this is the one ordering decision on the page that matters. |
| A beautifully personalised email reached somebody who left the company | The enrichment wrote a title and nobody compared the returned current employer with the account the prospect sits under. | Compare currentPosition.companyName against the account and route disagreements out of the cadence. This is three lines in the middle layer and it is the highest-value check on the page. |
| A 429 and a rateLimitExceeded error | Outreach rate-limits per user at 10,000 requests an hour, and bulk endpoints and Kaia apply their own rules, with Kaia at 3 calls a second and 6,000 a day at org level. | Read X-RateLimit-Remaining and honour X-RateLimit-Reset, which is aliased as Retry-After. The error body names the limit it thinks you exceeded and the time it resets, which is more than most APIs give you. |
| The limit changed and the backfill stopped halfway | Outreach states that it reserves the right to adjust API rate limits at any time to safeguard platform performance and ensure fair use. | Read X-RateLimit-Limit from a live response rather than hard-coding 10,000. A worker that discovers its own ceiling survives a change that a worker with a constant in it does not. |
| The prospect record was updated and the cadence step did not change | Steps already rendered and sent are gone, and a step scheduled for later picks up the current record. There is nothing to re-render. | Check the rendered preview of the next step rather than the record. If the cadence has moved past the step that used the field, the enrichment improved nothing a recipient will see. |
| Everything stopped, including the calls that were free | Below 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2. | Watch quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a scheduled balance check never fails for the reason the lookup did. |
| The resolved rate is far below the published match rate | A published figure is a global average over a provider's whole corpus and your list is not that corpus. Reverse Contact publishes 70%+ as an identity match rate and says to measure your own. | Run 500 of your own rows and count. That number is the one that decides the economics of this build, and nothing else is a substitute for it. |
| An endpoint that worked last week returns nothing | /v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026. | Change both paths in the middle layer. On this route that is ordinary version-controlled code, which is one advantage of there being no app to configure. |

## What breaks, from the vendors' own docs

- **10,000 requests an hour, per user.** Outreach documents the limit as per-user rather than per-org, which is the opposite of how Salesloft meters the same thing. Bulk endpoints and Kaia have their own rules, and Kaia specifically is 3 calls a second and 6,000 a day at org level.
- **Outreach reserves the right to change it.** The documentation says so in as many words, which is worth quoting to anyone designing a backfill around the current figure. Read X-RateLimit-Limit from a live response rather than hard-coding 10,000.
- **Nothing is installed inside Outreach.** There is no app, no marketplace listing and no in-product step that calls an external API. Everything on this page is assembled from a webhook, something in the middle, and the Outreach API. Budget for the middle thing existing and being owned by somebody.
- **Enrichment after cadence entry is wasted.** A sequencer renders the first touch from whatever the record holds at send time. Enriching a prospect that is already two steps into a cadence improves the fourth email and cannot repair the first, which is the one that decided the reply.
- **Under 2 credits the free checks stop too.** When the Reverse Contact workspace has fewer than 2 credits left, even the free check endpoints return 402 rather than a result. A sweep designed to check cheaply first fails at the check rather than at the enrichment.

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

- Outreach API: getting started and rate limiting: https://developers.outreach.io/api/getting-started
- Salesloft: API rate limits: https://developer.salesloft.com/docs/platform/api-basics/rate-limits/
- Smartlead API: rate limits: https://api.smartlead.ai/guides/rate-limits
- lemlist API: rate limits: https://developer.lemlist.com/api-reference/getting-started/rate-limits
- Instantly API: rate limits: https://developer.instantly.ai/getting-started/rate-limit
- 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-11, summarised on the page: https://www.reversecontact.com/integrations-hub/outreach-integrations/outreach-reverse-contact-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/outreach-integrations/outreach-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.*
