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

# Apollo and Slack

> Generated from https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-slack-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 Apollo plan and a Slack workspace. An Apollo admin to connect it, and professional or organization for agents.

**What moves:** messages, activities, contacts, both ways.
**How it is built:** native, marketplace app, built on the api. **Effort:** minutes.

## The short version

This stopped being a notification integration and nobody updated the mental model. An Apollo admin connects it once for the whole workspace, and from then on anybody can prospect, enrich, sequence and report by typing in a Slack thread, under the permissions and credit limits they already have in Apollo. Notifications still exist and are configured in two separate places, which is the one genuinely confusing thing about it: system activity and tasks live in Apollo's notification settings, and anything from the AI assistant or a scheduled agent lives under AI Assistant, Channels. Email engagement alerts are in neither, and come from the Chrome extension or a workflow.

## Which parts of this need a higher Apollo plan

Rows: Apollo plan. Columns: What you get in Slack. Slack costs nothing here and Apollo gates one thing. The distinction is between a surface you go to and a surface that comes to you, and only the second one is behind a plan.

| Apollo plan | The app, and everything you type | System activity and task notifications | Agents that recommend unprompted |
|---|---|---|---|
| Free or basic | Included | Included | Not included |
| Professional | Included | Included | Included |
| Organization | Included | Included | Included |

- **Included.** Apollo states the Slack app is available on all Apollo plans, and every action you take through it is bounded by the plan, permission and credit limits you already have in the product rather than by anything Slack-specific.
- **Not included.** Apollo states that agents are available on professional and organization plans. Agents also run in the AI assistant, so upgrading is about having them at all rather than about having them in Slack.

Counted off that grid, of nine pairings: eight give you included, one gives you not included.

Two of the three columns read the same on every row, which makes the gate easy to describe: everything you ask for is included, and only the part that asks you is not. That is a cleaner split than most pairs in this directory manage, and it is worth saying because the integration is usually described as if the whole thing were free.

## 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 |
|---|---|---|
| Natural language requests | One way, in | Search, research, enrich, add to a list or sequence, export, ask about sequence performance, pause a sequence. The conversation is saved into Apollo's AI assistant. |
| Agent recommendations | One way, out | On professional and organization plans. They run on a schedule, arrive in Slack for review, and Apollo continues the work once you approve one. |
| System activity notifications | One way, out | Data request activity, either per completion or as a daily digest, enabled in Apollo's notification settings and ticked through to Slack. |
| Task notifications | One way, out | Configured in the same place, and aimed at reps with busy workloads rather than at admins. |
| Email opens and clicks | Events only | Not in either notification screen. They come from the Chrome extension's desktop alerts, or from a workflow with an email opened or email clicked trigger. |
| Credits | Events only | Spent from Slack exactly as they are in the app. Enriching ten contacts in a thread costs what enriching ten contacts costs. |

## Which field lands where

There is nothing to map on this pair. What there is instead is a list of things you can ask for, a list of things that notify you, and a boundary between the two that Apollo documents in separate articles and that nobody discovers by exploring the interface.

| In Apollo | In Slack | What to know about the match |
|---|---|---|
| Find people and companies | A search in the thread, on your criteria | Apollo's own example is five VPs of sales in San Francisco at software companies with 100 to 500 employees. Refining and expanding happen in the same thread rather than as a new request. |
| Research people and companies | Returned into the thread | The research half of the AI assistant, reachable from Slack. Nothing is written anywhere until you ask for it to be. |
| Enrich contacts | Verified emails and phone numbers | The action that spends credits, and the one a one-sentence request makes easiest. Costs exactly what it costs in the product. |
| Add contacts to a list or sequence | An existing Apollo list or sequence | Apollo's example is adding the first ten contacts to a named sequence. The sequence has to exist already, as it does everywhere else in Apollo. |
| Ask about performance | An answer in the thread | Reply rates and sequence performance questions, which is the cheapest thing on this list because it reads rather than writes. |
| Take a sequence action | Simple actions, such as pausing | Documented as simple actions rather than full sequence management, so treat the reporting and the pausing as the realistic scope. |
| Export | A CSV | The end of the documented chain: find, enrich, add to a list or sequence, or export. Worth knowing a rep can take a prospect list out of Apollo from Slack. |
| The conversation itself | Saved into Apollo's AI assistant | So the thread is not the only record of what was asked, which matters both for continuity and for anybody auditing what was spent. |

### Which notification lives in which settings screen

| The action | How it reads on the record |
|---|---|
| A data request completed, one by one | Settings, Notifications, under system activity |
| A daily digest of the day's data requests | Settings, Notifications, under system activity |
| Task notifications for a rep's workload | Settings, Notifications, under tasks |
| A scheduled agent's recommendation | AI Assistant, Channels. Configured separately |
| A long-running AI assistant task finishing | AI Assistant, Channels. Configured separately |
| An email being opened or clicked | Neither. The Chrome extension, or a workflow with that trigger |

**What does not cross:**

- Anything reaching a CRM. Work done here lands in Apollo, and the CRM timeline is a separate integration with its own page.
- A permission this integration grants on its own. Apollo states that each user can only take actions in Slack that they already have permission to perform, under the same plan, permission and credit limits.
- Creating a sequence or a list from scratch in a thread. The documented chain adds contacts to ones that exist; agents are the feature that proposes creating new ones.

## Connect it, in this order

**Who has to do it:** An Apollo admin, once, for the whole workspace. Nobody else has to do anything.
**How long:** Five minutes to connect. The thinking is about credits and about which notifications go where.

### 1. Check the plan against what you expect it to do

*Where:* Apollo: Settings, Plans

Apollo states the Slack app is available on all plans and that agents are available on professional and organization. If the reason you want this is unprompted recommendations rather than a surface to type into, that is a plan question before it is a setup one.

### 2. Decide who is allowed to spend credits before connecting

*Where:* Apollo: Settings, Users and teams

Apollo applies the same plan, permission and credit guardrails in Slack as in the product, so this is not a new permission model. It is a large reduction in friction against an existing one, which is the part worth discussing first.

### 3. Connect as an Apollo admin

*Where:* Apollo: Settings, Integrations, or AI Assistant, Channels

Click Connect beside Slack and sign in to the workspace. The integration is team-wide and only an admin can do it, so a non-admin seeing no Slack option is looking at the correct screen.

### 4. Set system activity and task notifications

*Where:* Apollo: Settings, Notifications

Tick what you want for system activity or tasks, then tick the option to receive them in Slack, then Save. System activity covers data request completions, either one by one or as a daily digest, which is the admin visibility half.

### 5. Set the AI assistant notifications separately

*Where:* Apollo: AI Assistant, Channels

Confirm Slack shows as connected, then choose which alerts you want: scheduled threads and long-running tasks. Apollo documents these as configured separately from the settings above, and that is the single most confusing thing about this pair.

### 6. Set up an agent if your plan carries them

*Where:* Slack: Agents and apps, Apollo.io, Manage

Agents run on a schedule and surface a recommendation in Slack for you to approve or decline. Approving one lets Apollo continue the work. They also run in the AI assistant, so Slack is where you see them rather than where they live.

### 7. Start a thread and chain the requests

*Where:* Slack: Apollo.io, Messages

Apollo's own advice is to be specific and chain: find prospects on criteria, then refine the search, then enrich with emails and phone numbers, then add to a list or sequence, then export. Each step continues in the same thread.

### 8. Decide where engagement alerts come from

*Where:* Apollo: the Chrome extension or workflows

Email opens and clicks are not in either notification screen. Apollo points at the Chrome extension for real-time desktop alerts, or a workflow with an email opened or email clicked trigger, which can send notifications to Slack users or channels.

Two of those eight steps are the connection and six are decisions about who does what. That ratio is the honest shape of this pair now, and it is a different page from the one this was a year ago, when the only question was which two events to route and which channel to route them to.

## How to check it worked

- Have a non-admin run a request in a thread. They should be able to do exactly what they can do in Apollo and nothing more, which is the guardrail working rather than a permissions problem.
- Enrich two contacts from Slack and then check the credit balance. Seeing the meter move for a one-sentence request is the point worth making to a team once.
- Set a system activity notification and an AI assistant notification, then confirm both arrive. They are configured in different places and it is easy to believe you have done both when you have done one.
- Ask the thread about a sequence you know the numbers for. Reporting questions are the cheapest way to test the connection without spending anything.

## 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 |
|---|---|---|
| There is no Connect option beside Slack | The Slack integration is team-wide and only an Apollo admin can connect it. | Ask an Apollo admin. There is no per-user alternative, and once they have connected it everybody in the workspace can use it without connecting anything themselves. |
| Notifications were configured and half of them never arrive | There are two separate screens. Settings, Notifications covers system activity and tasks; AI assistant notifications, including scheduled agents and long-running tasks, are configured under AI Assistant, Channels. | Set both. Apollo documents the separation explicitly, and it is the most common misconfiguration on this pair. |
| No recommendations ever arrive unprompted | Agents need a professional or organization plan. On a lower plan this is a surface you use rather than one that contacts you. | Check the plan before debugging the channel. Agents also run in the AI assistant, so if they exist at all you will see them there too. |
| Email opens and clicks are not reaching Slack | They are in neither notification screen. Apollo routes engagement alerts through the Chrome extension or through workflows. | Use the Chrome extension for real-time desktop alerts, or build a workflow with an email opened or email clicked trigger and a send notifications action pointed at a Slack user or channel. |
| A rep cannot do something in Slack that a colleague can | Working as intended. Each user can only take actions in Slack that they already have permission to perform in Apollo, under the same plan, permission and credit limits. | Fix the permission profile in Apollo rather than looking for a Slack setting. There is no Slack-side permission model to adjust. |
| Credits went down faster than anybody expected | Enrichment from a thread costs exactly what enrichment costs, and a one-sentence request is much easier to make than the same action in the product. | This is a policy problem rather than a configuration one. Decide who is allowed to enrich at volume, and use the system activity notifications, which exist precisely to make data requests visible. |
| A request returned nothing useful | Apollo's own guidance is to be specific and to chain requests rather than asking for everything at once. | Start with the criteria, then refine in the same thread, then enrich, then add to a list or sequence. Backing out and messaging Apollo again starts a new chat and loses the context. |
| A sequence could not be added to | The documented chain adds contacts to lists and sequences that already exist. Creating them is not part of it. | Build the sequence in Apollo first. This is the same prerequisite every sequencer pair in this directory has. |

## What breaks, from the vendors' own docs

- **Notifications are configured in two unrelated places.** Settings, Notifications covers system activity and tasks, and Apollo states that AI assistant notifications, including scheduled agents and long-running tasks, are configured separately under AI Assistant, Channels. Somebody who sets one and expects the other gets silence from the half they did not touch.
- **Agents need professional or organization.** The Slack app is on all Apollo plans and agents are not. Agents are the part that produces unprompted recommendations, so on a lower plan this is a surface you use rather than one that comes to you.
- **Only an admin can connect it, and it is workspace-wide.** A team-wide integration with no per-user authentication. The upside is nobody has to connect anything; the consequence is that the decision is made once for everybody by one person.
- **Convenience and the credit meter are the same thing.** Apollo applies the same plan, permission and credit guardrails in Slack as in the app. Enriching from a thread is not cheaper than enriching from the product, and it is considerably easier to do without thinking about it.
- **It does not update the CRM.** This pair moves work and attention, not records. The CRM timeline comes from Apollo's CRM integration, which is a separate thing to configure.

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

### Slack

- **Base:** `https://slack.com/api`
- **Auth:** `Authorization: Bearer xoxb-...` (bot token). Scope `chat:write`, plus `chat:write.public` to post to a channel the bot has not joined.

| Call | Request | What it does |
|---|---|---|
| `POST /api/chat.postMessage` | `{ "channel": "C0123", "text": "...", "blocks": [...] }` | The only call most of these workflows need. Use this when you need to choose the channel at runtime. |

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

- **HubSpot's Slack workflow action cannot route to the channel associated with the record.** It sends to a channel chosen at design time. If you need per-record routing, look the association up yourself and call `chat.postMessage` directly.
- Creating a Slack channel from a HubSpot workflow requires HubSpot Professional or Enterprise.
- Route only events a named human must act on within minutes. A channel that fires forty times a day gets muted, and a muted channel is indistinguishable from a working one in the admin screen.

Docs: https://api.slack.com/methods/chat.postMessage

## 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 Slack with Apollo: https://knowledge.apollo.io/hc/en-us/articles/22464817775117-Integrate-Slack-with-Apollo
- Apollo knowledge base: configure notifications on Apollo: https://knowledge.apollo.io/hc/en-us/articles/34009920880781-Configure-Notifications-on-Apollo
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-slack-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-slack-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.*
