The trigger needs a bot token and the node wants OAuth, so you build both.
An n8n instance you host or rent, and a Slack app with the right token type
Messages, two-way sync.
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.
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.
| 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 | Both ways | Archive, close, create, invite, join, kick, leave, rename, set purpose, set topic, unarchive, and read history and replies. |
| Files, reactions and stars | Both ways | Upload and read files, add and remove reactions, manage stars. More than the native connectors in this directory offer. |
| Users and user groups | Both ways | Read users, update profiles and statuses, create and manage user groups. |
| Anything the node misses | Both ways | The HTTP Request node, using the same Slack credential, so an unsupported endpoint is a configuration rather than a blocker. |
Four of those six rows move in both directions. The two that do not are Messages into Slack and Messages out to n8n, and those are the rows that decide how you design around this rather than the ones in the brochure.
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. |
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.
Every row above travels as a file: five field mappings and three documented exclusions, each one's note, and the three 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.
The version-dependent behaviour is the one to write down somewhere your team will read: the same workflow behaves differently across an n8n upgrade, and in one direction it fails silently.
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. Pick one on each side and the grid marks the answer.
Pick one on each side.
| 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 |
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.
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.
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.
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.
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.
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.
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.
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.
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/slack-n8n/SKILL.md https://www.reversecontact.com/integrations-hub/skills/slack-n8n.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
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.
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.
WhyIt 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.
WhyFrom 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.
WhySome 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.
WhyThe 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.
WhyFrom 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.
WhySlack'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.
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.
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.
Searched for this pair by name, in the words a person would use. 14 threads from 2025 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.
Been using slack to trigger automations on my selfhosted n8n version and finally found a way to get this setup easily, made a q
r/n8n·June 2025·5 points
The word finally is doing the work. On a self-hosted instance Slack has to reach a Request URL it can verify, and the two-credential split above is the other half of why this takes an evening rather than ten minutes.
I built a n8n automated workflow to track daily team progress via slack
r/n8n·June 2026·9 points
Worth using. A published workflow shows which node versions and credential types the author actually used, which is exactly the detail the documentation makes you assemble yourself.
I have been exploring the best approach for integrating a Slack bot with an N8N agent, specifically to handle multi-turn (back-and-forth) conversations
r/n8n·April 2025·3 points
This is where the event subscription detail matters. If the event you need is not in the node's list, adding it as a bot event in Slack and selecting Any Event is the documented route, and it is not obvious from the node UI.
I am building out a wholesale real estate operation and need an end-to-end n8n, GHL and Slack integration
r/n8n·June 2025·13 points
Typical of how this pair is used. Slack is rarely the point; it is the surface a longer n8n workflow reports into, which is an argument for getting the posting rate right early rather than the feature set.
Been using slack to trigger automations on my selfhosted n8n version and finally found a way to get this setup easily, made a quick video ab
r/Slack·June 2025·3 points
The same author posting to r/Slack as well as r/n8n, which says something about where the confusion sits: it is a Slack app configuration problem as much as an n8n one, and the Slack side is where the scopes live.
Unusually for this directory, the threads are people building rather than people complaining. The recurring subject is connecting Slack to a self-hosted n8n, which is the configuration this page spends most of its length on, and the recurring artefact is somebody publishing their workflow for others to copy.
If you are starting from scratch, the fastest route is the manifest and somebody else's published workflow, in that order, because both encode the scope decisions this page lists one at a time.
The argument for n8n over a per-task tool on this pair is not features, it is the cost curve and who holds the credentials. Self-hosted n8n costs an instance and nothing per execution, so a workflow that fires ten thousand times a month costs the same as one that fires ten. Against that, somebody has to own the host, the upgrades and the credentials, which is a different kind of cost rather than a smaller one. That trade is the whole of the orchestration layer, and it is why this directory records who maintains an integration rather than only what it does.
The specific thing to design first here is the token model, because it is the one decision that is expensive to change. A build that listens and acts needs an access token for the trigger and, if you follow n8n's recommendation, OAuth2 for the node. Message search needs a user token, and several scopes a bot cannot hold at all. None of this is difficult, and all of it is invisible until something quietly does nothing, so write down which credential each node uses before you have fifteen of them.
Where this pair earns its place is the work no native connector will ever do: look a record up, decide something, and route the result to the channel that owns it. HubSpot's own Slack action cannot send to the channel associated with the deal that triggered it, which is the single most requested thing on that pair, and an hour in n8n is the documented way round it. Start there rather than rebuilding alerts a native app already sends perfectly well.
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 Slack, n8n 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.
More than most people expect. The Slack node covers channels, including archive, create, invite, kick, rename, set purpose and set topic; messages, including send, update, delete, search and send-and-wait-for-response; files; reactions; stars; users; and user groups. Anything the node does not cover can be called through the HTTP Request node using the same credential, which is the escape hatch that makes this pair open-ended rather than a fixed feature list.
Both, which is the awkward answer. n8n recommends OAuth2 for the Slack node and documents that the Slack Trigger node requires an API access token and does not support OAuth2. A build that both listens and acts therefore carries two Slack credentials, and the first sign of getting it wrong is a trigger that silently never fires.
Probably a bot token. From node version 2.7 the Message Search operation needs a user token rather than a bot token, and the Slack app has to have AI features enabled. Existing OAuth2 credentials also need reconnecting to pick up the newer search scopes. Several scopes are not available as bot token scopes at all, including channels:write and users.profile:write.
Nothing on the Slack side, and on the n8n side it depends on where it runs. Self-hosted n8n costs the instance and nothing per execution, which is the reason teams reach for it over a per-task tool once volume is real. n8n Cloud is priced per execution. Slack itself charges nothing for the API, though a free Slack workspace is limited to ten apps.
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.