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

# Slack and Outreach

> Generated from https://www.reversecontact.com/integrations-hub/slack-integrations/slack-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, an Outreach admin, and permission to add apps to Slack

**What moves:** messages, activities, events only.
**How it is built:** native, marketplace app. **Effort:** minutes.

## The short version

Lighter than the other Slack pairs here, and personal rather than broadcast. One admin connects the instance over Slack OAuth, Outreach maps users to their Slack accounts automatically, and from then on each person chooses which alerts reach Slack instead of the in-app feed, email or the browser. The channel story is thin on purpose: only the Kaia meeting summary is documented at account level, one channel per account, and turning that on makes account notifications visible to everyone in the channel. Read it as a better inbox for reps, not as a team alerting system.

## Which notifications Slack can carry and which it cannot

Rows: What you want to be told about. Columns: Where Outreach will deliver it. Nothing here is gated by a plan on either side: the app is free and Outreach includes the notifications with the contract. What varies is the delivery channel, and Outreach states outright that not all notifications support all channels.

| What you want to be told about | Slack | A browser notification |
|---|---|---|
| A reply from an unexpected address | Delivered | Not available |
| Meeting updates and voicemails | Delivered | Not available |
| Bounce limit warnings | Delivered | Not available |
| A prospect opening, clicking or replying | Not available | Delivered |
| An incoming call | Not available | Delivered |

- **Delivered.** Listed on Outreach's Slack notification table and toggled per user under Personal Settings, General, Notifications. The admin connection has to exist first and the user has to be mapped.
- **Not available.** Listed only under browser notifications, which Outreach says need OS-level permission and will not work if popups are blocked. There is no setting that moves one of these into Slack.

Counted off that grid, of ten pairings: five give you delivered, five give you not available.

Three rows go one way and two go the other, with no overlap, which is the cleanest possible statement of the thing teams get wrong. Slack carries the exceptions and the warnings, the ones that mean something has gone sideways; the browser carries the engagement, the ones that mean somebody is interested right now.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| Personal notifications | One way, in | Email-reply mismatches, meeting updates, new voicemails, bounce limits, CRM plug-in errors, mentions and overdue tasks, to the user who owns them. |
| Kaia meeting summaries | One way, in | Sent automatically when ready, and the one notification documented at account level, with a single Slack channel per account. |
| Deal Agent suggestions | One way, in | AI-detected opportunity updates from a call recording, which a user can accept, reject or edit from Slack. |
| Accepting a suggestion | One way, out | The decision travels back to Outreach and updates the opportunity field, which is the only thing moving in this direction. |
| Prospects, sequences and activity | Events only | Nothing. This is a notification surface. The records stay in Outreach and in whichever CRM it syncs with. |

## Which field lands where

Nothing syncs. There are two separate notification systems here, a personal one and an account one, and they overlap in exactly one place. Knowing which events belong to which is the whole configuration.

| In Slack | In Outreach | What to know about the match |
|---|---|---|
| Somebody other than the recipient replying | Personal, available in Slack | A prospect replies from a different address, belonging either to another prospect or to somebody Outreach does not know. The notification exists because the reply would otherwise be invisible. |
| Meeting updates | Personal, available in Slack | Booked via your public calendar link, reassigned to another prospect, rescheduled, or scheduled on your behalf by another Outreach user. |
| New voicemails | Personal, available in Slack | One trigger, one notification. The simplest thing on the list. |
| Bounce limits | Personal, available in Slack | Three thresholds: 50% of the bounce rate, 80%, and a final warning when you cannot send for the next 24 hours. The one notification on this page that stops work if ignored. |
| Plug-in and sync errors | Personal, available in Slack | Issues with the connected CRM, and a disconnected mailbox or calendar that has stopped synchronising. Worth routing somewhere a person actually reads. |
| Mentions and urgent tasks | Personal, available in Slack | Being mentioned in the Kaia chat, and an urgent task going past its due date. |
| Kaia meeting summary | Personal and account-level | The only event that exists in both systems, and the only one an account channel can deliver. |
| An account to a channel | One channel per account, public only | Selected from an autocomplete on the account details page. The Outreach app does not need to be invited to the channel, which is unusual and worth knowing. |

### The three events everybody wants in Slack, and where they actually go

| The action | How it reads on the record |
|---|---|
| A prospect opens an email | Browser notification only, with OS-level permission required |
| A prospect clicks a link | Browser notification only |
| A prospect replies to an email | Browser notification only |
| An incoming call | Browser notification only |
| An overdue urgent task | Browser, and also available as a Slack notification |
| A Kaia meeting summary | Slack, personally or into a channel attached to the account |

**What does not cross:**

- Email engagement into Slack. Opens, clicks and replies are browser notifications, and Outreach states plainly that not all notifications support all channels.
- More than one Slack channel per account, or a private one. The autocomplete offers public channels and each account links to a single one.
- Any account notification other than the Kaia meeting summary. Outreach says more types may be added in future releases; that is the entire list today.

## Connect it, in this order

**Who has to do it:** An Outreach admin to connect the instance, then every user for their own notifications, and whoever owns an account for its channel.
**How long:** Ten minutes for the admin. Then it is never finished, because the useful part is per person and per account.

### 1. Check you can add apps to the Slack workspace

*Where:* Slack: app management

Outreach lists it as a prerequisite before anything else. The connection is made from Outreach, but it installs an app in Slack, and a locked-down workspace will stop the admin halfway through.

### 2. Connect at the instance level

*Where:* Outreach: Administration, Organization, Org info, General

Scroll to Slack notifications and follow the prompts. This is Slack OAuth once for the whole org rather than per user, and once it is done Outreach tries to map Outreach users to their Slack users automatically.

### 3. Decide the account-channel question before you enable it

*Where:* Outreach: the same screen

Allow users to connect Slack channels to Outreach accounts is a separate switch, and Outreach warns what it means: account-related notifications sent to those channels may be visible to all channel members. That is a disclosure decision rather than a feature toggle.

### 4. Tell people their notifications are personal

*Where:* Outreach: Personal Settings, General, Notifications

The admin connection enables nothing by itself. Each user toggles their own Slack notifications, and a user who does not see Slack as an option has not been mapped yet rather than hit a bug.

### 5. Set the browser notifications separately, and expect to

*Where:* The browser, after clicking Enable browser notifications

Three of the most-wanted events are browser-only: a prospect opening an email, clicking a link or replying. Outreach notes these need OS-level permission, so a blocked popup setting silently disables them.

### 6. Attach a channel to an account only where it earns one

*Where:* Outreach: the account details page

The notifications for Slack panel sits under the account name in the top right. Pick a public channel from the autocomplete, and note that the Outreach app does not need to be invited to it, unlike most Slack integrations.

### 7. Know what the account channel can actually deliver

*Where:* The same panel

One notification type is supported today: the Kaia meeting summary, triggered after a call associated with that account once Kaia has processed the recording. Outreach says more may be added; today that is the list.

### 8. Accept one channel per account

*Where:* The same panel

Each account links to a single Slack channel, changed by returning to the account page. Outreach recommends this for teams running dedicated deal channels, which is exactly the shape it fits.

The admin step takes ten minutes and enables nothing visible, which is why this pair is so often reported as not working on the day it is connected. Everything a person actually sees is switched on by that person or by whoever owns the account, and that distribution is what the [collaboration layer](layer:collab) demands of every tool that writes into a channel.

## How to check it worked

- Have one non-admin check Personal Settings for a Slack option. Its absence means the user mapping has not happened, which is the documented answer and not a permissions problem.
- Trigger a prospect open or click and watch where it arrives. It will be a browser notification rather than a Slack message, and that surprises people who assumed everything routes everywhere.
- Attach a test account to a channel and run a Kaia call against it. The summary arrives after the call ends and after Kaia has processed the recording, so a short delay is expected rather than a failure.
- Before enabling account channels for everybody, post one account notification to a channel and look at who is in it. Outreach warns the content may be visible to all channel members, and seeing it once makes the point.

## 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 |
|---|---|---|
| A user cannot see Slack in their notification settings | Outreach answers this one directly: Slack must be enabled by an Outreach admin and mapped to the user's account. | Confirm the instance-level connection exists, then check the user mapping. Outreach maps users automatically after connecting, so an unmapped person usually joined afterwards. |
| Nothing happened after the admin connected it | Correct behaviour. The admin connection enables the channel and switches nothing on; each user toggles their own notifications. | Send people to Personal Settings, General, Notifications. This is the single most common reason the integration is reported as broken on day one. |
| Opens and clicks never arrive in Slack | They are browser notifications rather than Slack ones. Outreach states that not all notifications support all channels. | Enable browser notifications and grant the OS-level permission. There is no configuration that routes engagement events into Slack. |
| Browser notifications are enabled and still nothing appears | Popups are blocked, or the OS permission was never granted. Outreach says the browser asks after you press Enable browser notifications. | Check both the browser and the operating system settings. Outreach answers this in its own FAQ, which is a sign of how often it happens. |
| The channel selector is missing on an account | Either Slack is not connected to the Outreach org, or the account-channel feature has not been enabled by an admin. | An admin connects the integration and enables the feature in Org info. You also need edit permission on the account you are configuring. |
| An account channel receives nothing but meeting summaries | That is the full list. Outreach supports only the Kaia meeting summary at account level today. | Use personal notifications for everything else. Outreach notes additional types may come in future releases, which is not something to plan around. |
| The meeting summary arrived late | It is triggered post-call and sent after Kaia has processed the recording. Outreach documents a short delay. | Wait rather than reconfiguring. If it never arrives, check the call was actually associated with that account. |
| Account notifications are visible to people who should not see them | Outreach warns about this when the feature is enabled: account-related notifications sent to a channel may be visible to all channel members, and only public channels can be selected. | Treat channel membership as the access control, because it is. This is a decision to take before enabling the feature across the org. |

## What breaks, from the vendors' own docs

- **Channel alerting is barely supported.** Outreach documents only the Kaia meeting summary at account level, with one Slack channel per account. Teams expecting reply alerts routed to a deal channel will not find that here, and the documentation is itself inconsistent, with release notes describing Slack features the core setup article does not list. Check what your instance actually offers before designing around it.
- **Account channels expose account notifications.** The admin setting that lets users connect Slack channels to Outreach accounts carries an explicit warning that account-related notifications sent to those channels may be visible to all channel members. In a shared or client-facing channel that is a disclosure decision rather than a configuration one, and it belongs with whoever owns the account relationship.
- **Not every notification supports every channel.** Outreach states it plainly: not all notifications support all channels. So a notification a rep expects in Slack may only exist in the in-app feed or by email, and the toggle for it simply will not be there. The only reliable way to know is the notifications screen in a real account.
- **User mapping has to work first.** The integration maps Outreach users to Slack users automatically after connection, and personal notifications depend on that mapping succeeding. Where it fails, the user sees no option to enable Slack at all, which looks like a missing feature rather than an unmapped account and is the first thing to check.

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

- Outreach support: admin configuration of Outreach app for Slack: https://support.outreach.io/support/solutions/articles/159000425170-admin-configuration-of-outreach-app-for-slack
- Outreach support: configure in-app notifications and notifications for Slack: https://support.outreach.io/support/solutions/articles/159000425264-configure-in-app-notifications-and-notifications-for-slack-in-outreach
- Outreach support: account-level notifications in Outreach for Slack: https://support.outreach.io/support/solutions/articles/159000430400-account-level-notifications-in-outreach-for-slack
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-outreach-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-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.*
