Does n8n integrate with Slack?
Yes — native node
Yes. n8n integrates natively with Slack via a built-in node and trigger — no middleware. You connect with OAuth2 or a bot Access Token from a Slack app you create at api.slack.com. The common gotcha is OAuth scopes: you must add the scopes for each action (chat:write, channels:read, users:read, etc.) or the node returns a missing-scope error.
| Integration method | Native — Built into n8n as the Slack node (n8n-nodes-base.slack) for messages, channels, users, and files, plus a Slack Trigger — no middleware. Authentication supports either OAuth2 or a bot Access Token from a Slack app you create at api.slack.com. Either way you must add the right OAuth scopes (at minimum chat:write to send messages; channels:read, users:read, and others for listing and DMs), or calls fail with a missing-scope error. |
|---|---|
| Sync direction | Two-way: send and update messages, manage channels, users, and files from n8n, and start workflows from incoming Slack events via the Slack Trigger. |
| Plan required | Free on both sides. Self-hosted n8n Community Edition is free; n8n Cloud offers a 14-day free trial. A free Slack workspace can host the Slack app, though some Slack features depend on workspace plan. |
| Setup time | ~15 minutes (creating the Slack app and assigning scopes) unverified estimate |
How to connect n8n to Slack
- At api.slack.com/apps, create a new Slack app in your workspace.
- Under OAuth & Permissions, add the bot token scopes you need (e.g. chat:write to send messages, channels:read and users:read to list channels and users), then install the app to the workspace.
- In n8n, add a Slack node and create a Slack credential — choose Access Token and paste the bot token, or choose OAuth2 and authorize.
- Pick the resource and operation (e.g. Message > Send), select the channel, and write your message.
- To receive events, add the Slack Trigger, run it to generate the webhook URL, then paste that URL into your Slack app's Event Subscriptions and enable it.
Known friction points
- Connecting the Slack Trigger fails if you paste n8n's webhook URL into Slack before running the trigger — the workflow must be listening first so Slack's URL verification succeeds; run the trigger, then add the URL to Event Subscriptions. [source]
- Some users hit a scope error referencing the deprecated chat:write:bot scope even though Slack replaced it with chat:write, blocking bot-token credentials on certain node versions. [source]
FAQ
- Does n8n integrate with Slack?
- Yes. n8n has a native, built-in Slack node and Slack Trigger. Connect with OAuth2 or a bot Access Token from a Slack app, and you can send and update messages, manage channels and users, and react to Slack events — no middleware.
- Do I need a paid plan to use Slack in n8n?
- No. Self-hosted n8n Community Edition is free and n8n Cloud has a 14-day free trial. A free Slack workspace can host the app, though a few Slack capabilities depend on your Slack plan.
- Why do I get a missing-scope error with the Slack node?
- Your Slack app lacks the OAuth scope for the action. Add the needed bot token scopes (chat:write to send messages, channels:read and users:read to list channels/users, plus more for private channels or DMs) under OAuth & Permissions, then reinstall the app.
✓ Last verified: 2026-06-10 · Every claim on this page links to a primary source. If the integration changed, the page is out of date — check the sources below.
Sources
- n8n docs — Slack node (accessed 2026-06-10)
- n8n docs — Slack credentials (accessed 2026-06-10)
- n8n Community #172027 (Slack trigger webhook connection order) (accessed 2026-06-10)
- n8n GitHub Issue #29806 (Slack chat:write:bot scope error) (accessed 2026-06-10)