How to Connect Slack to n8n (Step-by-Step Guide for Cloud & Self-Hosted)
Struggling to bridge the gap between Slack and your n8n workflows? Whether you're using cloud or self-hosted n8n, this guide walks you through every step - from API setup to webhook configuration. Plus, we'll show you how to add an AI assistant to your Slack workspace without writing a single line of code.
Why Connect Slack to n8n?
Most teams use Slack as their primary communication hub, but manually handling messages and notifications wastes valuable time. The real power comes when you connect Slack to automation tools like n8n. This integration lets you automatically process messages, trigger workflows from conversations, and even add AI capabilities to your Slack workspace.
Without automation, teams spend hours each week on repetitive Slack tasks - forwarding messages, responding to common questions, or manually updating other systems based on conversations. The n8n integration solves this by turning Slack into an intelligent automation hub.
Key benefit: Connecting Slack to n8n can save teams 5-10 hours per week by automating message handling, notifications, and data routing between Slack and other business systems.
Slack App Setup & API Configuration
The first step is creating a Slack app to handle the API connection. This gives n8n permission to interact with your Slack workspace. Start by navigating to api.slack.com/apps and clicking "Create New App".
You'll need to:
- Name your app (e.g., "n8n Integration")
- Select your workspace
- Click "Create App"
Once created, navigate to the "Basic Information" tab and copy your Signing Secret - you'll need this later. Then go to the "OAuth & Permissions" tab to configure what your app can do.
Required scopes: For basic message handling, add these OAuth scopes: channels:read, groups:read, im:read, and chat:write.
After adding scopes, scroll up and click "Install to Workspace". This generates your Bot User OAuth Token - copy this as well. These credentials (Signing Secret and OAuth Token) are what n8n will use to connect to Slack.
Connecting n8n to Slack
With your Slack app configured, switch to n8n. Create a new workflow or open an existing one. Add a Slack trigger node (like "New Message") or action node (like "Send Message"), depending on what you want to automate.
When configuring the Slack node, you'll see options to create new credentials. Click this and paste in:
- The OAuth Token from Slack's "OAuth & Permissions" tab
- The Signing Secret from Slack's "Basic Information" tab
After saving, test the connection. If successful, you should see your Slack channels appear in the dropdown menu. This confirms n8n can now access your Slack workspace.
Pro tip: Create separate credential sets for different Slack workspaces or permission levels. This keeps your automations organized and secure.
Webhook Configuration
For real-time message handling, you need to set up webhooks so Slack can notify n8n about new messages. Return to your Slack app dashboard and navigate to "Event Subscriptions". Toggle "Enable Events" to on.
Here's where things differ between cloud and self-hosted n8n:
For Cloud n8n:
- Copy the webhook URL from your n8n trigger node
- Paste it into Slack's "Request URL" field
- Slack will verify the URL automatically
For Self-Hosted n8n:
Since your local n8n instance isn't publicly accessible, you need to:
- Set up a tunneling service like ngrok or Cloudflare Tunnel
- Create a public URL that points to your local n8n
- Use this public URL in Slack's Request URL field
After verification, scroll down to "Subscribe to Bot Events" and add message.channels (for public channels) and/or message.groups (for private channels). Click "Save Changes".
Special Considerations for Self-Hosted n8n
Self-hosting n8n gives you more control but adds complexity to Slack integration. The main challenge is that Slack needs a public URL to send webhook notifications, while your local n8n instance isn't internet-accessible by default.
Solutions include:
- ngrok: Creates secure tunnels to localhost. Free for basic use but limited in the free tier.
- Cloudflare Tunnel: More robust solution that doesn't expose your local network.
- Reverse proxy: Advanced option if you have a domain and server.
Remember that tunneling services may:
- Change URLs periodically (free ngrok does this)
- Have rate limits
- Require authentication for security
Enterprise tip: For production use, consider deploying n8n on a cloud server with a static IP and domain. This provides reliability without tunneling.
Testing Your Slack-n8n Workflow
With everything connected, it's time to test. Create a simple workflow with:
- A Slack trigger node set to listen to a specific channel
- A debug node to log incoming messages
Activate the workflow and send a test message in Slack. Within seconds, you should see the message appear in n8n's execution log. If not:
- Check that your bot is added to the channel
- Verify webhook configuration in Slack
- Confirm your tunneling service is running (for self-hosted)
Once basic messaging works, you can expand to more complex automations like:
- Auto-responding to keywords
- Routing messages to other apps
- Creating tickets from Slack conversations
Adding an AI Assistant to Your Slack
One powerful application is adding AI to your Slack through n8n. After setting up the basic Slack connection:
- Add an "AI Agent" node after your Slack trigger
- Connect it to an AI provider (like OpenAI or Anthropic)
- Configure the system prompt to define your assistant's personality
- Add a Slack "Send Message" node to reply to the channel
At 4:32 in the video tutorial, we demonstrate how to:
- Remove the n8n watermark from messages
- Maintain conversation context
- Route different queries to specialized AI models
Creative use case: One client used this setup to create a Slack assistant that answers employee HR questions by pulling from their handbook and policies, reducing HR ticket volume by 30%.
Watch the Full Tutorial
For a complete walkthrough with live demonstrations of each step, watch the video tutorial. At 2:15, we show the exact Slack API settings needed, and at 5:48, you'll see how to test the AI assistant integration.
Key Takeaways
Connecting Slack to n8n unlocks powerful automation possibilities, from simple message routing to AI-powered assistants. While the setup involves several steps, each one is straightforward when followed carefully.
In summary: 1) Create a Slack app with proper permissions 2) Connect credentials in n8n 3) Configure webhooks (with tunneling for self-hosted) 4) Test basic message flow 5) Expand to advanced use cases like AI integration.
Frequently Asked Questions
Common questions about this topic
Connecting Slack to n8n allows you to automate message handling, create AI-powered assistants, and integrate Slack with hundreds of other apps. You can automatically respond to messages, route notifications, and trigger workflows from Slack conversations.
This integration turns Slack from a simple messaging tool into a powerful automation hub. Teams report saving 5-10 hours per week by eliminating manual message handling and creating intelligent workflows that respond to Slack activity.
- Automate responses to common questions
- Create tickets or tasks from Slack messages
- Connect Slack to your CRM, project tools, and databases
No coding is required for basic integration. The setup involves configuring API permissions in Slack and connecting credentials in n8n through visual interfaces. The most technical part is setting up webhooks, which we provide step-by-step instructions for.
Even the AI assistant integration can be done through n8n's visual workflow builder. The only exception might be if you need custom functionality beyond what the nodes provide, but most common use cases don't require any programming.
- All configuration done through web interfaces
- Visual workflow builder in n8n
- Pre-built nodes handle the technical details
The main difference is in webhook configuration. Cloud-hosted n8n provides public URLs automatically, while self-hosted instances require tunneling for Slack to reach your local server. Self-hosting gives you more control over security and data but needs additional setup.
Self-hosted n8n is ideal if you need to keep data on-premises or have strict compliance requirements. Cloud n8n is simpler to set up but may have limitations based on your subscription tier. Performance is generally similar once configured.
- Cloud: Easier setup, managed service
- Self-hosted: More control, needs tunneling
- Same functionality once connected
Yes, the guide includes steps to add an AI model as a Slack assistant. You can connect various AI providers through n8n to process messages and generate intelligent responses. The AI can maintain conversation context and answer questions naturally.
Advanced implementations can route different types of queries to specialized models - for example, technical questions to one model and HR questions to another. The AI can also trigger other automations based on the conversation content.
- Use any major AI provider (OpenAI, Anthropic, etc.)
- Maintain conversation history
- Route to different models based on query type
In the Slack Send Message node configuration, find the "Options" section and toggle off "Include link to workflow". This removes the default "Sent via n8n" attribution from messages while keeping all functionality intact.
At 5:12 in the video tutorial, we demonstrate exactly where to find this setting. Remember that removing the attribution means users won't know an automation sent the message, so consider your use case carefully.
- Toggle off in Send Message node options
- No effect on functionality
- Consider transparency with your team
The Slack app needs permissions to read messages, post messages, and access channel information. Specifically: chat:write (to send messages), channels:read (for public channels), groups:read (for private channels), and im:read (for direct messages).
Additional permissions might be needed for advanced use cases. For example, adding reactions requires reactions:write. The exact permissions depend on what your automation needs to do. Start with the basics and add more as needed.
- Minimum: chat:write, channels:read
- For DMs: im:read, im:write
- For private channels: groups:read
Yes, the same principles apply to Enterprise Grid, though admin approval may be required for app installation. Enterprise Grid may have additional security policies that affect how external apps can access channels across your organization.
The main differences are in the approval process and potential restrictions on which channels the app can access. Some organizations restrict bots from certain channels or require additional security reviews for integrations.
- Same technical setup
- May need admin approval
- Possible channel restrictions
GrowwStacks specializes in building custom Slack automations with n8n. We can configure the integration, set up AI assistants, and create workflows tailored to your business processes. Our team handles everything from initial setup to ongoing maintenance.
We've helped businesses automate customer support, internal processes, and team collaboration through Slack-n8n integrations. Whether you need a simple notification system or a complex AI assistant, we can design a solution that fits your needs.
- Custom Slack automation design
- AI assistant implementation
- Ongoing support and maintenance
Ready to Transform Your Slack into an Automation Powerhouse?
Manual Slack management wastes time and creates bottlenecks. Let GrowwStacks build custom n8n workflows that connect Slack to your entire business - typically deployed in under 2 weeks.