> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revyops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Apollo

> Use your Apollo API key in Find data workflow steps to look up a person's email and LinkedIn URL.

## What This Integration Does

Apollo is a data provider and an email verifier. Connecting it lets a workflow's [Find data step](https://docs.revyops.com/user-guide/workflows.md#find-data-step) look a person up with Apollo and add the email or LinkedIn URL it finds to that person in RevyOps. Choose **Apollo** as the step's **Data provider**.

Apollo is connected per workspace, with one API key for both uses. Find data steps on Apollo spend credits from that Apollo account.

> [!NOTE]
>
> A super admin can switch Apollo off for an agency. Its tile then shows "Upgrade to Enterprise to Access" and Find data steps on Apollo stop with "Apollo is not available on your plan. Ask your agency admin."

## Setup

Apollo is connected in its email verification panel, which also sets what each of Apollo's email results means in RevyOps. Follow [Email Verification](https://docs.revyops.com/integrations/email-verification.md#setup): go to **Settings → Integrations**, open **Apollo** in the **Data Providers** section, paste a master API key, click **Verify & Connect**, and choose a status for each Apollo result. Once the key is saved and checked, Find data steps on Apollo can use it.

The **Connect Apollo** link on a Find data step opens this panel directly.

## How A Person Is Looked Up

Apollo matches the person on everything they already have: their LinkedIn URL, their email, and their name with their company domain. One match returns the person's work email and their LinkedIn URL.

| What the step finds | Apollo credits |
| - | - |
| **Email** | 1 per match, **even when the match has no email** |
| **LinkedIn URL** | Comes from the same match |
| **Mobile phone** | Not available yet |

A match with no person costs nothing. A person needs a LinkedIn URL, an email, or a last name and a company domain to be looked up; with none of these, Apollo is not called.

Apollo sends mobile numbers later, to a webhook, rather than in the match itself, so Find data can't get them from Apollo yet. A mobile phone on an Apollo step is skipped with the reason "Apollo returns mobile numbers later, not available in Find data yet". Use [MoltSets](https://docs.revyops.com/integrations/moltsets.md) or [AI Ark](https://docs.revyops.com/integrations/aiark.md) on that step to find mobile phones.

A LinkedIn URL found on the way to an email is added to the person too, but only when they have none.

When Apollo says it matched the person with low confidence, nothing from that match is added, because it may be someone else. The step lists each value as skipped with the reason "Apollo matched this person with low confidence, not added".

## Email Status

A new email gets the status your Apollo mapping gives its result, the same mapping you set in the Apollo panel; see [Changing Your Setup](https://docs.revyops.com/integrations/email-verification.md#changing-your-setup) to edit it. Until a result is mapped, `verified` is **Valid**, `unavailable` is **Unknown**, and any other result, such as `unverified` or `likely_to_engage`, is **Risky**, because Apollo has not confirmed the mailbox. An email whose result you map to **Invalid** is not added; the step's result lists it as skipped. The test results and Run History show Apollo's own result next to the status, such as "Apollo result likely to engage, Catchall".

## When Apollo Says No

| Apollo answer | What happens |
| - | - |
| The key is refused | The step fails with "Apollo refused the API key. Reconnect Apollo under Integrations." |
| The plan has no API access | The step fails with "Your Apollo plan does not include API access." |
| No credits left | The step fails with "Apollo has no credits left on this account. Top up Apollo, then rerun." |
| The hourly or daily request limit is used up | The step fails with "Apollo's hourly request limit is used up. Rerun these records in an hour." or the daily one, "Rerun these records tomorrow." |
| Apollo rejects the input | The lookup is skipped with the reason "Apollo rejected the input" |
| Too many requests, or Apollo is down | The step waits and tries again |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.