n8n Slack Automation: Build Bots, Notifications, and Smart Workflows
Slack is the heartbeat of most teams I work with. Every conversation, every update, every decision flows through those channels. But here is the problem — the more your team relies on Slack, the more noise builds up, and the more time you spend on repetitive messaging tasks that could easily be automated.
I am Javier, a startup consultant in Chile, and I have spent the last few years helping teams automate their Slack workflows with n8n. From simple notification bots to complex message routing systems, I have built dozens of Slack automations that save my clients hours every week.
In this guide, I will show you exactly how to set up n8n Slack automation, walk you through several practical workflows, and build a complete RSS-to-Slack pipeline that keeps your team informed without anyone lifting a finger.
Why Automate Slack with n8n?
Slack has its own Workflow Builder, but it is limited. You can do basic things like sending a form or posting a scheduled message, but anything beyond that requires custom development or expensive third-party tools.
n8n changes the game because it lets you:
– Connect Slack with any other tool — CRMs, databases, APIs, email, and hundreds more
– Build complex logic — conditional routing, data transformation, loops, and error handling
– React to events outside Slack — trigger Slack messages from website events, database changes, or monitoring alerts
– Create interactive bots — respond to slash commands, button clicks, and message reactions
– Scale without per-message pricing — n8n does not charge based on how many messages you send
If you want to see how n8n compares to other automation platforms for Slack integration, check out my n8n vs Zapier breakdown.
Getting Started: Connecting n8n to Slack
Before building any workflows, you need to connect n8n to your Slack workspace. There are two approaches, and I recommend the second one for maximum flexibility.
If you do not have n8n running yet, the fastest way to start is with n8n cloud. You will have a working instance in minutes, ready to connect with Slack.
Option 1: OAuth2 (Quickest Setup)
1. In n8n, add a Slack node to a new workflow
2. Click Credentials > Create New
3. Select Slack OAuth2 API
4. Click Sign in with Slack — this opens the Slack authorization page
5. Select your workspace and click Allow
6. Done — n8n now has access to your Slack workspace
[SCREENSHOT: n8n Slack OAuth2 credential setup dialog with the “Sign in with Slack” button]
This method is quick but uses limited permissions. For full control, use Option 2.
Option 2: Custom Slack App (Recommended)
Creating a custom Slack app gives you granular control over permissions and enables advanced features like slash commands and interactive messages.
1. Go to api.slack.com/apps and click Create New App
2. Choose From scratch and name your app (I call mine “n8n Bot”)
3. Select your workspace
Now configure the permissions:
4. Go to OAuth & Permissions
5. Under Scopes > Bot Token Scopes, add:
– chat:write — send messages
– chat:write.public — send to channels the bot is not in
– channels:read — list channels
– channels:history — read channel messages
– users:read — list users
– reactions:write — add emoji reactions
– files:write — upload files
6. Click Install to Workspace and authorize
7. Copy the Bot User OAuth Token (starts with xoxb-)
[SCREENSHOT: Slack API dashboard showing the Bot User OAuth Token after installation]
Now in n8n:
8. Add a Slack node and create a new credential
9. Select Slack API
10. Paste the Bot User OAuth Token
11. Test the connection
Inviting the Bot to Channels
Your Slack bot needs to be in a channel before it can post messages there. Either:
– Type /invite @your-bot-name in the channel
– Or use the chat:write.public scope to post to any public channel without being invited
I always add the chat:write.public scope because it eliminates the need to manually invite the bot to every channel.
Workflow 1: RSS Feed to Slack Channel
Let us build the main workflow for this tutorial — an automated pipeline that monitors RSS feeds, filters for relevant content, formats a clean message, and posts it to a Slack channel.
This is one of the first Slack automations I built, and I still use it daily. It keeps my team updated on industry news, competitor blog posts, and product updates without anyone having to manually share links.
The Architecture
Schedule Trigger --> RSS Feed Read --> Filter --> Set (Format) --> Slack (Post Message)
Step 1: Schedule Trigger
We want this workflow to check for new RSS items regularly.
1. Add a Schedule Trigger node
2. Set it to run every 30 minutes (adjust based on how frequently the feed updates)
3. This ensures you catch new articles without spamming the channel
[SCREENSHOT: Schedule Trigger node configured for 30-minute intervals]
Step 2: Read the RSS Feed
1. Add an RSS Feed Read node
2. Enter the RSS feed URL (for example, https://techcrunch.com/feed/)
3. n8n will fetch all current items from the feed
[SCREENSHOT: RSS Feed Read node with a feed URL entered and showing fetched items in the output panel]
The node returns items with fields like title, link, description, pubDate, and creator.
Step 3: Filter for New and Relevant Items
We only want to post new items, not the entire feed history. Add an IF node:
1. Condition: pubDate is after {{ $now.minus(30, 'minutes').toISO() }}
2. This ensures we only process items published since the last check
You can add more conditions to filter by keyword:
- Title contains "AI" OR "automation" OR "startup"
- Description does not contain "sponsored"
[SCREENSHOT: IF node with date and keyword filter conditions configured]
Step 4: Format the Message
Raw RSS data looks messy in Slack. Add a Set node to create a clean, formatted message:
Slack Message:
:newspaper: *{{ $json.title }}*
{{ $json.description.replace(/<[^>]*>/g, '').substring(0, 200) }}...
:link: <{{ $json.link }}|Read full article>
:bust_in_silhouette: By {{ $json.creator || 'Unknown' }}
:calendar: {{ $json.pubDate }}
This creates a message with:
- A newspaper emoji and bold title
- A clean description (HTML tags stripped, truncated to 200 characters)
- A clickable link
- Author and date information
[SCREENSHOT: Set node showing the Slack message template with expressions]
Step 5: Post to Slack
1. Add a Slack node
2. Set Resource to "Message"
3. Set Operation to "Send"
4. Select the target Channel (e.g., #industry-news)
5. Set Text to the formatted message from the Set node
6. Enable Unfurl Links if you want Slack to show link previews
[SCREENSHOT: Complete workflow in n8n showing all five nodes connected with the Slack node configuration visible]
Testing and Activation
1. Click Execute Workflow to test with current feed data
2. Check your Slack channel for the formatted messages
3. If everything looks good, toggle the workflow to Active
The workflow will now run every 30 minutes, automatically posting new articles to your Slack channel.
Workflow 2: Daily Standup Bot
One of the most requested Slack automations I build for clients is a daily standup bot. Here is how it works:
1. Schedule Trigger fires at 9:00 AM every weekday
2. Slack node posts a standup prompt to the team channel
3. Team members reply in a thread
4. At 10:00 AM, another Slack node posts a summary reminder
The Standup Message
I format the standup prompt like this:
:wave: Good morning team! Time for standup.
Please reply in this thread with:
:white_check_mark: What did you accomplish yesterday?
:dart: What are you working on today?
:rotating_light: Any blockers?
[SCREENSHOT: Slack channel showing the standup bot message with team member replies in a thread]
Advanced: Collecting Responses
For teams that want standup responses collected and stored, I add:
1. A Slack Trigger node that listens for thread replies
2. A Google Sheets node that logs each response with the date and person
3. A weekly Schedule Trigger that generates a summary report
This creates an automatic record of standups that managers can review without scrolling through Slack history.
Workflow 3: Alert and Notification System
This is the bread and butter of Slack automation -- sending notifications from other systems to Slack. Here are the patterns I use most:
Server Monitoring Alerts
Webhook (from monitoring tool) --> IF (severity check) --> Slack (post to #alerts)
I route alerts based on severity:
- Critical: Post to #alerts-critical with @channel mention
- Warning: Post to #alerts-warning without mention
- Info: Post to #alerts-info (low-traffic channel)
CRM Lead Notifications
CRM Webhook --> Set (format lead info) --> Slack (post to #new-leads)
Every time a new lead comes in, the sales team sees it instantly in Slack with key details: name, company, source, and a link to the CRM record.
Deployment Notifications
GitHub Webhook --> IF (branch = main) --> Slack (post to #deployments)
When code is merged to the main branch, the engineering channel gets a notification with the commit message, author, and a link to the pull request.
Workflow 4: Message Routing and Triage
For teams that receive support requests or inquiries through a shared Slack channel, message routing is essential.
The Setup
1. Slack Trigger listens for new messages in #support-inbox
2. Switch node categorizes the message based on keywords:
- Contains "billing" or "invoice" --> route to #billing-team
- Contains "bug" or "error" --> route to #engineering
- Contains "feature" or "request" --> route to #product
- Default --> route to #general-support
3. Slack node forwards the message to the appropriate channel with context
[SCREENSHOT: Switch node showing keyword-based routing conditions for different support categories]
I add a reaction to the original message (like a checkmark emoji) so the person knows their message was received and routed. This is done with a separate Slack node set to "Add Reaction".
Channel Management Automation
Auto-Archive Inactive Channels
Slack workspaces accumulate channels that nobody uses. Here is a workflow to clean them up:
1. Schedule Trigger runs weekly
2. Slack node lists all channels
3. Code node checks the last message date for each channel
4. IF node filters channels with no activity in 90 days
5. Slack node posts a warning to the channel
6. After another 30 days, Slack node archives the channel
New Employee Welcome
When someone joins the workspace:
1. Slack Trigger detects the team_join event
2. Slack node sends a welcome DM with onboarding links
3. Slack node adds the user to standard channels (#general, #announcements, #team-socials)
4. Slack node posts a welcome message to #general
Best Practices for Slack Automation
Do Not Over-Notify
The biggest mistake I see teams make is sending too many automated messages. Each notification should be actionable and relevant. Before building a Slack automation, ask: "Will someone actually act on this message?"
Use Threading
When a workflow posts a message and then needs to add follow-up information, use threading instead of separate messages. Set the "Reply to Message" option in the Slack node and reference the original message timestamp.
Format Messages Properly
Slack supports rich formatting. Use it:
- Bold for titles and key information
- Code blocks for technical data
- Bullet points for lists
- Emojis for visual categorization (but do not overdo it)
Handle Errors Gracefully
If a workflow fails to post to Slack, you need a fallback. I always set up an error workflow that sends a notification via email. That way, even if Slack is down, I know something went wrong.
Rate Limits
Slack has API rate limits (roughly 1 message per second per channel). If your workflow sends many messages at once, add a Wait node with a 1-second delay between sends to avoid hitting the limit.
Interactive Messages and Slash Commands
For more advanced use cases, n8n can handle interactive Slack messages with buttons and menus.
Button-Based Approvals
1. Post a message with buttons using the Slack Block Kit format
2. Set up a Webhook node to receive the button click
3. Process the approval and update the original message
Here is the Block Kit JSON for an approval message:
{
"blocks": [
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "*New Expense Request*\nAmount: $250\nCategory: Travel\nSubmitted by: Maria"
}
},
{
"type": "actions",
"elements": [
{
"type": "button",
"text": { "type": "plain_text", "text": "Approve" },
"style": "primary",
"action_id": "approve_expense"
},
{
"type": "button",
"text": { "type": "plain_text", "text": "Reject" },
"style": "danger",
"action_id": "reject_expense"
}
]
}
]
}
[SCREENSHOT: Slack message showing approval buttons rendered from the Block Kit JSON above]
This creates a professional approval flow entirely within Slack, with n8n handling all the backend logic.
FAQ
Can n8n send Slack messages to private channels and DMs?
Yes. With the right bot token scopes, n8n can send messages to public channels, private channels (the bot must be invited first), and direct messages. For DMs, use the user's Slack ID instead of a channel name. You can find user IDs by using the Slack node's "Get User" operation or by checking the user's Slack profile. Private channels require the bot to be explicitly invited with the /invite @botname command.
How do I avoid hitting Slack API rate limits with n8n?
Slack allows roughly one message per second per method. If your workflow sends multiple messages in a loop, add a Wait node with a 1 to 2 second delay between each Slack node execution. For batch operations like posting to multiple channels, use the SplitInBatches node to process items in groups with pauses between batches. Also, avoid running high-frequency workflows (less than 1 minute intervals) that post to Slack, as this quickly exhausts your rate limit quota.
Can I trigger an n8n workflow from a Slack slash command?
Yes. First, create a slash command in your Slack app settings that points to your n8n webhook URL. In n8n, use a Webhook node to receive the slash command payload, which includes the command text, user ID, and channel ID. Process the request in your workflow and send a response back within 3 seconds (Slack requires a timely response). For longer operations, send an immediate acknowledgment and then use a separate Slack node to post the full result when processing is complete.
Conclusion
Slack automation with n8n is one of the highest-impact improvements you can make to your team's workflow. The RSS-to-Slack pipeline we built is just the beginning -- once you have the connection set up, you can automate notifications, approvals, standups, and channel management in ways that Slack's built-in tools simply cannot match.
I have been running these automations for my own consulting practice and my clients for years, and the time savings compound quickly. A standup bot alone saves each team member 5 minutes a day. Multiply that across a 10-person team over a year, and you are looking at over 200 hours saved -- from a single workflow.
If you are ready to start automating Slack, sign up for n8n and try building the RSS feed workflow first. It is a quick win that demonstrates the power of automation and gives you a foundation to build on.
For more n8n tutorials and workflows, check out my full n8n review and my beginner guide if you are just starting out.
Happy automating.