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

# Slack and n8n

> Generated from https://www.reversecontact.com/integrations-hub/slack-integrations/slack-n8n-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 n8n instance you host or rent, and a Slack app with the right token type

**What moves:** messages, both ways.
**How it is built:** zapier, make or n8n, built on the api. **Effort:** hours.

## The short version

This is the most capable Slack integration in the directory and the one with the most ways to misconfigure the credential. The node reaches almost the whole Slack surface and the HTTP Request node covers the rest, so the question is never whether you can do something, it is which token you did it with. n8n recommends OAuth2 for the node, the Slack Trigger requires an access token and refuses OAuth2, message search needs a user token rather than a bot token, and several scopes are not available to bots at all. Get the token model right on day one and this pair is the cheapest Slack automation you can run.

## Which credential carries which half

Rows: Credential in n8n. Columns: What you are building. There is no plan gate on either side of this pair. n8n is self-hosted or rented and Slack charges nothing for an app, so the grid that decides whether it works is about credentials rather than money.

| Credential in n8n | Actions on the Slack node | A Slack trigger | Custom bot identity |
|---|---|---|---|
| OAuth2 only | Works | Does not work | Does not work |
| Access token only | Works | Works | Works |
| Both configured | Works | Works | Works |

- **Works.** That half has the credential it needs. Note the middle row: an access token alone covers everything, which is why some teams skip OAuth2 entirely despite it being the recommended method for the node.
- **Does not work.** The Slack trigger requires an API access token and will not take OAuth2, and from node version 2.6 a custom bot profile photo needs the access token path too.

Counted off that grid, of nine pairings: seven give you works, two give you does not work.

The top row is the trap, because it is the configuration a careful person arrives at by following the recommendation and stopping there.

## 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 |
|---|---|---|
| Messages into Slack | One way, in | Send, update, delete, get permalink, and send-and-wait-for-response, which pauses the workflow until a human answers. |
| Messages out to n8n | One way, out | Through the Slack Trigger node, which requires an access token and does not support OAuth2. |
| Channels | Two-way sync | Archive, close, create, invite, join, kick, leave, rename, set purpose, set topic, unarchive, and read history and replies. |
| Files, reactions and stars | Two-way sync | Upload and read files, add and remove reactions, manage stars. More than the native connectors in this directory offer. |
| Users and user groups | Two-way sync | Read users, update profiles and statuses, create and manage user groups. |
| Anything the node misses | Two-way sync | The HTTP Request node, using the same Slack credential, so an unsupported endpoint is a configuration rather than a blocker. |

## Which field lands where

There are no records to map. What matters is which credential each operation needs and which scopes a bot token can actually hold.

| In Slack | In n8n | What to know about the match |
|---|---|---|
| The Slack node | OAuth2 credential | n8n's recommended method for the node itself. |
| The Slack Trigger node | API access token credential | Required. The trigger does not take OAuth, which is why this pair needs two credentials. |
| A custom bot icon or emoji | Access Token authentication only, from node 2.6 | It needs chat:write.customize, which is a bot-token scope that the OAuth2 user-token path cannot use. |
| A Slack event n8n does not list | Any Event in the node | Add it as a bot event in Slack first, then select Any Event. |
| A search request | 20 results, about 10 requests a minute | From node version 2.7, with Channel Types, date filters and a Keyword Search Only option that disables semantic search. |

**What does not cross:**

- Scopes that are not available to bot tokens, including channels:write and stars:read.
- A custom bot profile photo over OAuth2 from node 2.6 onwards, and on 2.5 and below the option appears and is ignored.
- Sustained posting above roughly one message per second per channel.

## Connect it, in this order

**Who has to do it:** Whoever administers the n8n instance, plus a Slack workspace member who can create an app. The Slack app is the integration; n8n is the thing calling it.
**How long:** An hour, most of it spent on scopes.

### 1. Create the Slack app from a manifest, not from scratch

*Where:* Slack: Your Apps, Create New App, From a manifest

n8n publishes a manifest. Pasting it sets the scopes and the event subscriptions in one step, which is considerably less error-prone than ticking scopes by hand and discovering the missing one at run time.

### 2. Expect to create two credentials, not one

*Where:* n8n: credentials

n8n recommends OAuth2 for the Slack node and requires an API access token for the trigger. Those are two separate credentials against the same Slack app, and assuming one will serve both is the most common first-hour mistake on this pair.

### 3. Check the scopes you need are available to a bot token

*Where:* Slack: OAuth and Permissions

n8n lists scopes that do not exist as bot token scopes, including channels:write and stars:read. If your workflow needs one of those, the design changes rather than the configuration.

### 4. Subscribe to events, including ones not on the list

*Where:* Slack: Event Subscriptions

After Slack verifies the Request URL you can manage subscriptions in the app manifest under settings.event_subscriptions. For an event n8n does not list, add it as a bot event in Slack and select Any Event in the node.

### 5. Know which auth your version needs for a custom bot identity

*Where:* The Slack node, Message, Send

From node version 2.6, Custom Bot Profile Photo works only with Access Token authentication. It relies on chat:write.customize, a bot-token-only scope the OAuth2 user-token path cannot use. On 2.5 and below the option still appears with OAuth2 and Slack ignores it, which is worse than it being hidden.

### 6. Design the posting rate before you build the loop

*Where:* Your workflow

Slack allows roughly one message per second per channel with a workspace ceiling above it, and gives no guarantee beyond short bursts. Batch into one message rather than iterating.

Two credentials and a manifest is the shape to remember. Everything that goes wrong on this pair afterwards is a scope that was never granted or a version that silently ignores an option.

## How to check it worked

- Fire the trigger and confirm it uses the access token credential rather than failing on OAuth.
- Send a message with a custom bot icon. If it posts with the default icon and no error, you are on OAuth2 with a node version that ignores the option.
- Run a search and count the results. From node version 2.7 you get 20 per request, which is a cap rather than an empty result.
- Post twice in quick succession to the same channel and watch for throttling before you build anything that loops.

## 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 trigger will not authenticate | It is configured with OAuth2. n8n requires an API access token for the Slack Trigger node. | Create a second credential of the access token type against the same Slack app. |
| A custom bot icon is ignored | From node version 2.6 the option needs Access Token authentication, because chat:write.customize is a bot-token-only scope. On 2.5 and below the option is shown with OAuth2 and Slack ignores it. | Switch that workflow to the access token credential. There is no error to find, which is why this one survives upgrades. |
| A scope cannot be granted | Some scopes do not exist for bot tokens at all, including channels:write and stars:read. | Check n8n's list before designing around the operation. This is a redesign rather than a permission request. |
| An event n8n does not list is needed | The node exposes a set of events, and yours is not in it. | Add the event as a bot event in Slack, then select Any Event in the node and branch on the payload. |
| Search returns only twenty results | From node version 2.7 search returns 20 per request and is limited to roughly 10 requests a minute. | Paginate deliberately and narrow with the Channel Types and date filters rather than fetching everything. |
| Messages drop during a loop | Slack's posting limit of roughly one message per second per channel, with no guarantee beyond short bursts. | Batch the output into a single message. This is the same constraint every Slack integration in this directory hits. |

## What breaks, from the vendors' own docs

- **Two credentials, because the trigger will not take OAuth.** n8n documents OAuth2 as the recommended method for the Slack node and an API access token as required for the Slack Trigger, which does not support OAuth2. Any workflow that both listens to Slack and writes back therefore holds two Slack credentials. The failure is quiet: the trigger simply never fires, and nothing in the workflow says why.
- **Bot tokens cannot do several things.** n8n lists scopes that are not available as bot token scopes, including channels:write, stars:read, stars:write, users.profile:write and the private search scopes, and notes that some Slack endpoints only work with user tokens. If the operation you need is in that set, the token type is the design decision rather than a setting you flip later.
- **Search is rate limited and capped.** From node version 2.7 search returns 20 results a request and is limited to roughly 10 requests a minute per user, Return All was removed in favour of a Limit capped at 50, and output field names changed, so `text` became `content`. n8n says plainly that search is not built for exhaustive retrieval. Semantic ranking on question-style queries needs a paid Slack AI plan.
- **Slack's own posting limits still apply.** Roughly one message per second per channel, with a workspace ceiling above it, and Slack gives no guarantee that messages are stored or displayed when a burst goes too far. A workflow that posts per record rather than per digest fails selectively and silently, which is harder to notice than failing outright.

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

### n8n

- **Base:** `Self-hosted or n8n Cloud`
- **Auth:** Credentials are stored in n8n, not in the workflow JSON, so the workflow stays safe to export and review.

| Call | Request | What it does |
|---|---|---|
| `NODE HTTP Request` | `Authentication: Generic > Header Auth. Name: Authorization. Value: Bearer rc_your_api_key` | There is no dedicated Reverse Contact node and you do not need one. Five minutes to configure, and no node update can break it. |
| `NODE HubSpot Trigger` | - | Authenticates with a **developer API key from a HubSpot developer account**, not a private app token, because that is how HubSpot exposes the webhooks API. Free to create, and nobody expects it. |
| `NODE Wait + IF` | - | The polling loop for Reverse Contact's /live endpoints: Wait 5s, GET the webhook id, IF status != succeeded loop back. |

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

- HubSpot allows **one webhook URL per app**. Route several object types through one subscription and branch inside n8n with a Switch node.
- Self-hosting is usually the reason this route was chosen: records never leave infrastructure you control. Do not quietly move it to a third-party cloud.
- n8n must be reachable by HubSpot for webhook triggers to fire.

Docs: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest

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

- n8n docs: Slack node: https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.slack
- n8n docs: Slack credentials: https://docs.n8n.io/integrations/builtin/credentials/slack
- Slack developer docs: Web API rate limits: https://docs.slack.dev/apis/web-api/rate-limits/
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-n8n-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-n8n-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.*
