Apollo and Slack

Not an alert feed any more: you prospect, enrich and sequence by typing in Slack.

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, two-way sync.

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.

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.

WhatDirectionWhat 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 Event 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 Event only Spent from Slack exactly as they are in the app. Enriching ten contacts in a thread costs what enriching ten contacts costs.

Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.

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 ApolloIn SlackWhat 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

Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.

The actionHow it reads on the record
A data request completed, one by oneSettings, Notifications, under system activity
A daily digest of the day's data requestsSettings, Notifications, under system activity
Task notifications for a rep's workloadSettings, Notifications, under tasks
A scheduled agent's recommendationAI Assistant, Channels. Configured separately
A long-running AI assistant task finishingAI Assistant, Channels. Configured separately
An email being opened or clickedNeither. The Chrome extension, or a workflow with that trigger

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

Every row above travels as a file: eight field mappings, six action rows and three documented exclusions, each one's note, and the two 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.

Field map

The second table is the part to screenshot for whoever sets this up. Three kinds of notification in one screen, two in another, and one in neither is not a design anybody would infer, and the usual symptom is a team concluding the integration is half broken when it is fully configured in one place and untouched in the other two.

Which parts of this need a higher Apollo plan

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. Pick one on each side and the grid marks the answer.

Pick one on each side.

Apollo planThe app, and everything you typeSystem activity and task notificationsAgents 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.

How to connect Apollo to Slack

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
An Apollo admin, once, for the whole workspace. Nobody else has to do anything.
How long it takes
Five minutes to connect. The thinking is about credits and about which notifications go where.
Setup checklist 0 of 8 done

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.

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.

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.

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.

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.

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.

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.

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.

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 and it has the whole pair without reading two sets of vendor docs first.

curl -o .claude/skills/apollo-slack/SKILL.md https://www.reversecontact.com/integrations-hub/skills/apollo-slack.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.

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.

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 8 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.

01

There is no Connect option beside Slack

WhyThe 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.

02

Notifications were configured and half of them never arrive

WhyThere 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.

03

No recommendations ever arrive unprompted

WhyAgents 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.

04

Email opens and clicks are not reaching Slack

WhyThey 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.

05

A rep cannot do something in Slack that a colleague can

WhyWorking 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.

06

Credits went down faster than anybody expected

WhyEnrichment 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.

07

A request returned nothing useful

WhyApollo'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.

08

A sequence could not be added to

WhyThe 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.

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

  • Prospecting and enriching without leaving the channel the work is discussed in
  • Asking what a sequence is doing without opening a reporting tab
  • Reply handling where speed is the whole advantage

Do not bother when

  • Nobody has decided who is allowed to spend credits
  • You actually need CRM logging, which is a different integration
  • You expect unprompted recommendations below the professional plan

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 the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2024 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.

There is a ceiling on how many integrations a workspace can carry

That 10-15 integration range is the sweet spot. Going past that usually just add

r/Slack·April 2026·1 points

Cut where the cached comment is. The number is one practitioner's rule of thumb rather than a measurement, and the shape is what matters: every integration you add competes for the same attention, so a new one has to displace something rather than join it.

The safeguard people reach for is an approval step, not a permission

Keeping the permissions away from the LLM is the right move. If the model can decide its own limits, it'll eventually find a way to skip a check. Having that rigid logic in the backend for write actions is how we handle it too. I'd much rather have the friction of an approve button than deal with a rogue agent deleting a channel or a ticket.

r/Slack·April 2026·1 points

Written about Slack agents generally, and it describes exactly how Apollo built this: permissions are enforced in Apollo rather than decided in the thread, and an agent recommendation waits for you to approve it before Apollo continues the work. The friction is the feature.

One channel per subject beats one channel per tool

i've tried a bunch of setups, but what works best for me is just one main slack channel per client keeps things simple and less noisy i use threads for updates, feedback, random questions, so stuff doesn't get lost

r/agency·July 2025·1 points

The structural advice that makes this pair work, from somebody organising client work rather than sales alerts. Since Apollo now works in a thread, the thread is where the context lives, and a channel organised by subject keeps those threads findable in a way a per-tool channel does not.

A notification is a prompt to look, not a record

you should have a saved search that will always show at any given time what orders are approved and ready for fulfillment. NetSuite is your source of truth. The saved search is what tells you at any given time how many orders are approved and ready for fulfillment. The slack notification is just a

r/Netsuite·June 2026·1 points

About a different system entirely, and it is the clearest statement of the principle this page rests on. The quote is cut where the cached comment is. Apollo stays the source of truth, the thread is saved back into the AI assistant, and the Slack message is a prompt rather than the account of what happened.

The tool-count problem is what people actually complain about

Apollo for data. Clay for enrichment. Smartlead for sending. Aircall for calls. HubSpot for CRM. Bombora for intent. Six tools.

r/microsaas·April 2026·1 points

From somebody with five years running outbound ops for agencies. It is the honest argument for this pair: not another place to be notified, but one fewer tab for the part of the job that was already happening in Slack conversations anyway.

What the threads add up to

Searching this pair by name is a trap worth recording: Apollo is also the name of a well-known discontinued Reddit client, and the first search returned a subreddit full of iOS push-notification threads about it. Searched properly, almost nobody discusses Apollo and Slack together, so this is a job search about getting sales work and alerts into the channel where the team already is. The recurring theme is restraint, from people who have watched a channel become unreadable.

None of these is about Apollo and Slack specifically, because almost nothing is. They are about the medium, and they agree with each other: fewer integrations, a human approval in front of anything that writes, and a channel organised around a subject rather than a tool. All three describe how this integration is built, which is a better endorsement than a thread about it would have been.

The longer answer

The reason to re-read this pair is that it changed category. It used to be an alert feed, and the advice was subtractive: route replies and bookings, leave opens and clicks off, keep the channel quiet enough to stay useful. That advice still applies to the notification half. What has been added underneath it is a full working surface, where a rep can run a search, enrich the results, push them into a sequence and ask how the sequence is doing, all in one thread.

Which moves the governance question somewhere new. Apollo is explicit that a person in Slack can only do what they could already do in Apollo, with the same credit limits, so nothing is being granted that was not granted before. What changes is friction: enriching fifty contacts used to mean opening the product and meaning it, and now it means typing a sentence. A team that has never had to think about who spends credits will start having that conversation, and it is better had before the connection than after the invoice.

For the rest of the stack, the division of labour is unchanged. This pair is where work happens and where attention is directed; the record lives in the CRM, and getting it there is Apollo and Salesforce or the HubSpot equivalent. Treating Slack as the system of record is the one failure this integration makes easy, because the thread looks like a complete account of what happened and is not.

Checked by

Reverse Contact

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 · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

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
2 vendor documents
Paid placement
None

The integration moves the record. Something has to fill it.

Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Apollo, Slack and everything else in this directory, and it returns null with a confidence score rather than a guess.

Free trial, no card required, and 500 credits to start.

Apollo and Slack, asked and answered

What can Apollo actually do inside Slack?

Find people and companies matching criteria, refine or expand the search, research them, enrich contacts with verified emails and phone numbers, add them to a list or a sequence, export to CSV, ask questions about your Apollo data and sequence performance, and take simple sequence actions such as pausing one. You type it in natural language in a thread with the Apollo app, and the conversation is saved back into Apollo's AI assistant. This is a working surface rather than a notification feed, which is what it used to be.

Who can connect it, and what does each person get?

Only an Apollo admin can connect it, because it is a team-wide integration rather than a personal one. After that every user in the workspace can use it, and Apollo applies the same guardrails it applies in the product: each person can only take actions they already have permission to perform, under the same plan, permission and credit limits. One connection, no per-user authentication, and no new permission surface.

Is any of it gated by plan?

The Slack app itself is on all Apollo plans. Agents, which run on a schedule and proactively recommend leads to find, sequences to create and sequences to improve, need professional or organization. Agents also run inside Apollo's AI assistant, so Slack is a delivery channel for them rather than a requirement.

Does this log anything to my CRM?

No. Work done here lands in Apollo, and getting sequence activity onto a CRM timeline is Apollo's CRM integration, which is a separate thing to configure and a separate page on this site. The thing to watch is that enriching a contact from Slack spends credits exactly as it would in the app, so the convenience and the meter are the same convenience and the same meter.

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