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

# Apollo and Outreach

> Generated from https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-outreach-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:** An Outreach contract, a paid Apollo plan, and an admin Outreach account to connect

**What moves:** contacts, lists, one way, out of Apollo.
**How it is built:** native. **Effort:** minutes.

## The short version

A deliberately narrow integration that does one thing cleanly: it turns an Apollo search result into an Outreach prospect in a sequence, without a CSV. There is no record sync, no activity writeback and nothing coming the other way, which is the right scope when Apollo is the data layer and Outreach is the sending layer. Two things to get right on day one: connect an admin Outreach account, because only one account can be connected at a time and a non-admin one hides sequences from everybody else; and check the field list, because thirteen fields travel and your personalisation may need a fourteenth.

## What each permission profile lets a rep send from

Rows: Can send emails from, on the permission profile. Columns: Which Outreach mailboxes appear to the rep. The plan requirements are short: an Outreach contract, a paid Apollo plan, and one Outreach account connected at a time. The setting worth a grid is the one that decides whose mailbox a rep can send a sequence from, because it defaults to all of them.

| Can send emails from, on the permission profile | Their own | Their Apollo teammates' | Everybody's |
|---|---|---|---|
| All users | visible | visible | visible |
| Other users on the same team | visible | visible | hidden |
| Self only | visible | hidden | hidden |

- **visible.** The mailbox appears in the send-from list at the moment of enrolment. Self only matches on the signed-in user's email address, so it shows Outreach mailboxes whose address matches theirs plus their own Apollo mailboxes.
- **hidden.** Not offered. Narrowing the profile does not change anything already enrolled, so a sequence already sending from somebody else's mailbox keeps doing it.

Counted off that grid, of nine pairings: six give you visible, three give you hidden.

The top row is the default and it is the widest: Apollo shows every mailbox in Outreach until an admin changes the permission profile. In a team where a rep sending from a colleague's address would be a problem, this is the one setting to change before anybody is trained on the push.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| Net new people | One way, out | Pushed from Apollo's people search after saving, with Add to Outreach. Creates the prospect in Outreach. |
| Saved contacts | One way, out | Pushed from the contact's own profile, after which Apollo keeps a shortcut between the two records. |
| Sequence enrolment | One way, out | Optional at push time, with the sending mailbox chosen in the same step. Click Refresh if a new sequence does not appear. |
| Thirteen contact fields | One way, out | Name, LinkedIn and website URLs, title, city, state, country, email, phone, street, postal code and time zone, where Apollo holds them. |
| Outreach activity back to Apollo | One way, in | Nothing. Replies, opens and sequence progress stay in Outreach, so Outreach is where you read performance. |

## Which field lands where

Thirteen fields travel in one direction and nothing travels back. That is the whole contract, and the useful work on this pair is reading the list against your own sequence templates rather than configuring anything.

| In Apollo | In Outreach | What to know about the match |
|---|---|---|
| First name, last name | The Outreach prospect's name | Pushed as long as Apollo holds them. A contact Apollo only knows by email arrives without a name and personalises as a blank. |
| Email | The prospect email | Apollo warns at enrolment on unverified or missing emails rather than refusing, so an unverified address can be sequenced if you click through the warning. |
| Phone | The prospect phone | One phone field. Apollo's distinction between a mobile and a direct dial does not survive the push. |
| Title | The prospect title | The field most sequences personalise on after the name, and the one most likely to be stale on an older Apollo contact. |
| LinkedIn URL, website URL | The matching prospect fields | Both travel, which is more than most handoffs manage, and the LinkedIn URL is what makes a manual LinkedIn step in Outreach usable. |
| City, state, country, street, postal code | The prospect address fields | Five of the thirteen are address. Worth knowing if you assumed the budget was spent on richer firmographics. |
| Time zone | The prospect time zone | The one field that changes sending behaviour rather than copy, since Outreach schedules against it. |
| Everything else in Apollo | Nothing | Employee count, industry, funding, technologies, intent signals, Apollo lists and stages all stay in Apollo. A template that needs one of them needs a different source. |

### What happens to a contact that is not eligible for the sequence

| The action | How it reads on the record |
|---|---|
| Already in another sequence | A warning before enrolment, which you can review or continue past |
| An unverified or missing email | A warning, on the same screen |
| Information Apollo considers outdated | A warning, on the same screen |
| Blocked by a workspace sending policy | Not enrolled, and not offered as a choice |
| The sequence is inactive | The sequence does not appear in the list at all, which reads as a missing sequence |
| You lack edit access to the sequence | The same symptom, and the fix is the sequence owner sharing access |

**What does not cross:**

- Anything from Outreach. Replies, opens, meetings and sequence progress stay there, so performance is read in Outreach and the list is built in Apollo.
- Companies. Sequences enrol contacts rather than companies, so a companies list has to be turned into people first.
- Mailbox rotation on a CSV push. Apollo documents that rotation is unavailable when adding contacts by CSV, and the route around it is importing to a list first and adding the list.

## Connect it, in this order

**Who has to do it:** An Apollo admin, and an Outreach admin account to authenticate with. The second one is the step that is hard to change later.
**How long:** Ten minutes to connect. The rest is checking what travels before you move a campaign.

### 1. Get the Outreach permission before you start

*Where:* Outreach: governance profile settings

The connecting user needs permission to create prospects in Outreach. Apollo points at Outreach's own governance profile documentation for it, and without it the authentication completes and the pushes do not.

### 2. Authenticate with an admin Outreach account

*Where:* Apollo: Settings, Integrations, Outreach

Click New Authentication, log into Outreach, then Finish. Apollo allows one Outreach account connected at a time and recommends an admin one specifically so the whole team can reach every Outreach sequence from Apollo.

### 3. Narrow which mailboxes reps can send from

*Where:* Apollo: Settings, Users and teams, Permission profiles

By default, send emails from shows every mailbox in Outreach. Under email permissions, Can send emails from takes All users, Self only, or Other users on the same team. The grid below is this setting, and the default is the widest one.

### 4. Check the thirteen fields against your sequence templates

*Where:* Your Outreach templates

First and last name, LinkedIn URL, website URL, title, city, state, country, email, phone, street, postal code and time zone. A merge field outside that list renders empty rather than failing, which degrades a campaign quietly.

### 5. Save the people before you push them

*Where:* Apollo: People search, Net New

Use search filters, click Net New, tick the prospects and click Save. Add to Outreach, then Push new contacts to Outreach, appears after that. An unsaved person pushed from a profile has to be saved first and Apollo redirects you there.

### 6. Pick the sequence and the sending mailbox in the same step

*Where:* Apollo: Add to Outreach

Enrolling in a sequence is optional at push time and the sending address is chosen alongside it. If a sequence you just built is not in the list, Apollo documents a Refresh that resyncs Outreach sequences and mailboxes rather than a wait.

### 7. Expect warnings and read them rather than clicking through

*Where:* Apollo: the enrolment dialog

Apollo warns before enrolment where it could create duplicate outreach, hurt deliverability or conflict with permissions: contacts already in another sequence, unverified or missing emails, outdated information. Contacts blocked by a workspace sending policy are not enrolled at all.

### 8. Use the shortcut to confirm the join worked

*Where:* Apollo: the contact record

A successful push creates a shortcut between the two platforms, and clicking Outreach on the Apollo contact opens the same person there. No Outreach option on a contact means the push did not land, and the fix is the Push to Outreach item in its menu.

Two of those eight are decisions rather than clicks: which Outreach account authenticates, and which mailboxes a rep is allowed to send from. Both are set once, both default to the permissive answer, and both are invisible from the push dialog where the consequences show up. The rest of this page is about what does not travel, which matters more here than on any other pair in the [engagement layer](layer:engage).

## How to check it worked

- Push one contact and open it in Outreach through the shortcut Apollo creates. If the shortcut is absent, the push failed rather than being slow.
- Run one sequence email to yourself through a template that uses every merge field you rely on. Any blank is a field outside the documented thirteen, and it is better to see it in your own inbox.
- Push a batch of twenty deliberately containing somebody already in that sequence. The skip and the warning are what you want to see once, because in production they look like a broken push.
- Check what mailboxes a non-admin rep can see in the send-from list. If it is all of them, the permission profile is still on the default.

## 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 team cannot see most of the Outreach sequences | A non-admin Outreach account was connected. Apollo allows one at a time and recommends an admin account precisely so the whole team can reach every sequence. | Reconnect with an admin account. Confirm first that the connecting user has permission to create prospects in Outreach, which is a separate Outreach governance setting. |
| A sequence you just created is not in the list | Apollo's cached copy of Outreach sequences and mailboxes is stale, or the sequence is inactive. | Click Refresh in the push dialog, which Apollo documents as the resync. If it still does not appear, activate the sequence in Outreach and check you have edit access to it. |
| A push of 200 enrolled 170 | Apollo skips contacts it considers ineligible: unsubscribed, bounced, marked Do Not Contact, already in that sequence, or limited by ownership and permissions. Anything blocked by a workspace sending policy is never enrolled. | Read the warnings on the enrolment screen and the Activities tab on each contact. The number is normal and the explanation is per contact rather than per batch. |
| A merge field is rendering empty in Outreach | The field is outside the documented thirteen, or Apollo does not hold it for that contact. Neither case produces an error. | Check your templates against the list before moving a campaign. Anything beyond those thirteen has to reach Outreach from the CRM or from an import rather than from this integration. |
| Insufficient credits when the workspace clearly has credits | Apollo may check credits for the whole batch before enrolment starts rather than per contact, so a large push can fail against a balance that would cover most of it. | Try a smaller batch, and review the waterfall enrichment settings, which is what Apollo's own documentation suggests for this error. |
| Mailbox rotation is not available on a CSV push | Documented: rotation cannot be selected when contacts are added by CSV. | Import the contacts into an Apollo list first, then add the list to the sequence and select two or more mailboxes. Same contacts, rotation available. |
| A contact in Apollo has no Outreach shortcut | The push did not complete. Apollo creates the shortcut between the two records as part of a successful push. | Use the Push to Outreach item in the contact's menu to retry. The shortcut is also the quickest way to audit whether a batch actually landed. |
| Contacts added by a workflow are not in the sequence yet | A workflow or the outbound copilot enrols on its own trigger and schedule, such as hourly or daily, rather than immediately. | Check the workflow's trigger conditions before debugging the integration. This is the one route where a delay is expected rather than a symptom. |

## What breaks, from the vendors' own docs

- **One Outreach account, and it should be an admin.** Apollo connects a single Outreach account at a time. Connect a non-admin one and the team sees only the sequences that account can reach, which looks like missing data and is a permissions choice made once at setup. The connecting user also needs permission to create prospects in Outreach.
- **Thirteen fields, and no more.** The documented list is first and last name, LinkedIn URL, website URL, title, city, state, country, email, phone, street, postal code and time zone. Anything your sequences personalise on beyond that has to arrive another way. This is the limit that quietly degrades a campaign rather than breaking it, because the merge field is simply empty.
- **Nothing comes back.** There is no writeback of replies, opens, meetings or sequence state into Apollo. Apollo is where the list is built and Outreach is where performance lives, and any report that needs both has to join them somewhere else, usually in the CRM both of them already write to.
- **Silent skips during enrolment.** Contacts that are unsubscribed, bounced, marked Do Not Contact, already in the sequence, or limited by ownership and permission settings are skipped rather than failed. That is correct behaviour and it means a push of 200 can enrol 170 with no error. The Activities tab on each contact records what happened.

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

- Apollo knowledge base: integrate Outreach with Apollo: https://knowledge.apollo.io/hc/en-us/articles/4414469672077-Integrate-Outreach-with-Apollo
- Apollo knowledge base: add contacts to a sequence: https://knowledge.apollo.io/hc/en-us/articles/4409396985741-Add-Contacts-to-a-Sequence
- Apollo knowledge base: use Apollo with LinkedIn: https://knowledge.apollo.io/hc/en-us/articles/5694087661325-Use-Apollo-with-LinkedIn-to-Send-Personalized-Messages
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-outreach-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-outreach-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.*
