To build a Slack bot with n8n, create and install a Slack app, grant only the bot scopes your workflow needs, save its Bot User OAuth Token in an n8n Slack credential, and connect a Slack Trigger to a Slack node. The trigger receives events through Slack’s Events API; the Slack node posts the reply. You must also enable Event Subscriptions, verify the n8n webhook URL, subscribe to matching bot events, and enable signing-secret verification when the endpoint is ready for real use.
Antihost offers VPS plans with one-click n8n, NVMe storage and a 14-day free trial.
What the finished Slack bot looks like
A practical n8n Slack bot has four parts:
- Slack app: the app registration that owns the bot identity, permissions, event subscriptions and signing secret.
- n8n Slack credential: stores the bot token used when n8n calls Slack. Slack calls made with that bot token appear as the bot.
- Slack Trigger: receives an inbound event, such as an app mention or a new message in a channel.
- Slack node: sends a message or other supported Slack action after the workflow has processed the event.
The normal path is:
- A person mentions the bot or posts an event that matches your subscription.
- Slack sends the event payload to the n8n webhook URL.
- The Slack Trigger starts the workflow.
- Optional n8n steps classify the request, look up information or call another service.
- A Slack node posts the result to the selected channel or thread.
This separation is useful when debugging: a failure before the trigger points to Slack’s subscription or endpoint, while a failure after the trigger usually concerns credentials, workflow logic or the destination message.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
Decide the bot’s behavior before creating it
Choose the narrowest event and action that satisfy the use case. A conversational assistant generally works best with an explicit app mention. A moderation or routing workflow may need every new message in selected channels, but that broader trigger creates more executions and requires more careful filtering.
Choose an inbound event
| Slack Trigger choice | Use it when | Important consequence |
|---|---|---|
| Bot/App Mention | The bot should answer when someone explicitly addresses it. | A good default for a conversational bot; unrelated channel traffic does not start the workflow. |
| New Message Posted to Channel | The workflow should inspect ordinary messages in a channel. | The bot must be present in the channel, and the workflow can execute much more often. |
| Watch Whole Workspace | You intentionally need matching events across every channel where the bot or app is present. | n8n warns to use this cautiously because every matching event can create an execution. |
| Any Event | The required Slack event is not available as a named option in the n8n selector. | Add the corresponding bot event in Slack and let the trigger receive the event without relying on a predefined choice. |
The Slack Trigger also exposes choices for App Home Opened, reactions, file events, new public channels and new users. Select only the event that the workflow actually handles.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Choose the outbound action
Decide whether the answer belongs in the channel, in the originating thread or in another destination. In the Slack node, select the relevant message or post operation, then map the destination and the workflow’s result into the message. Making the destination explicit prevents a bot that was meant for one channel from replying everywhere.
Prerequisites and permissions
- A Slack workspace in which you are allowed to create and install apps.
- An n8n instance that can receive the webhook URL Slack will call. For production events, Slack must be able to reach that URL over the network.
- An n8n workflow with access to Slack Trigger and Slack nodes.
- A decision about which events the bot handles and which Slack action it performs.
Plan scopes from the workflow backward. The app needs the ability to perform each action and to receive the selected events, but adding unrelated scopes increases what the bot can access. Common examples are:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →| Capability | Typical scope or permission area | When to add it |
|---|---|---|
| Post a reply | chat:write |
Whenever the workflow sends a message as the bot. |
| Read conversations or history | Conversation read/history scopes | When the workflow must inspect channel details, prior messages or conversation history. |
| Read users | User-related scopes | Only when the workflow needs user information beyond the event payload. |
| Work with files | File-related scopes | Only for workflows that inspect or handle Slack files. |
The Slack Trigger needs the permissions required for conversations.list and users.list at minimum. Its final requirements depend on the selected events and the Slack operations used later in the workflow.
Create and install the Slack app
1. Open Slack’s API Apps area
In Slack, open the API Apps area and create a new app. Slack lets you start from a manifest or configure the app from scratch. n8n recommends using a manifest because it can configure the required scopes in one step. A scratch setup is still valid when you need to review every setting manually.
2. Add bot scopes with least privilege
In the app configuration, add the bot scopes required by the trigger and the actions you selected. For a simple mention-and-reply bot, that normally means the permission to post messages plus the conversation and user permissions needed by the trigger. Do not add file, history or user scopes merely because they are available; add them when a workflow step needs them.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
If you change the event or add an n8n operation later, return to the app’s OAuth settings and review the scopes again. A workflow can appear correctly configured while still failing because the token predates a newly added scope.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →3. Install the app to the intended workspace
Install the app, review the authorization screen and approve it for the target workspace. Slack states that selecting Bot Token Scopes and installing the app provides a Bot User OAuth Access Token. Copy that bot token immediately and store it in the n8n credential rather than placing it in a workflow text field.
Installation is workspace-specific. A token from one workspace does not make the app available in another, and the bot still needs to be invited to a channel before it can operate there.
Put the bot token and signing secret in n8n
Create the Slack credential
- In n8n, open the credential selector for a Slack Trigger or Slack node and create a Slack credential.
- Paste the Slack Bot User OAuth Token into the token field. Preserve the complete value and do not add quotation marks or whitespace.
- Save the credential and select it on every Slack Trigger and Slack node that should use this bot identity.
The Slack Trigger requires an API access token credential. For the Slack node, n8n recommends OAuth2; follow the credential type exposed by your n8n version and the node you are configuring rather than reusing a token in a plain text field when an OAuth2 credential is available.
Add signature verification
Copy the app’s Signing Secret from Slack’s Basic Information page into the n8n Slack credential. n8n recommends enabling request signature verification for the Slack Trigger for additional security. The signing secret lets n8n verify that incoming requests were signed by Slack instead of accepting arbitrary requests sent to the webhook.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Signing-secret verification is available from n8n 1.106.0. If your n8n installation is older and the setting is absent, upgrade n8n before treating an unauthenticated endpoint as a production bot. Keep the secret private just like the bot token.
Configure the Slack Trigger
Select the event in n8n
- Create a new workflow and add Slack Trigger.
- Select Bot/App Mention for an explicit conversational bot, or select New Message Posted to Channel for channel-wide message handling.
- Choose the Slack credential containing the bot token and, if enabled, the signing secret.
- Save the workflow so n8n generates the webhook URLs for testing and production.
Use Any Event when the Slack bot event you need is not one of the named choices. You still have to add that event in Slack’s Event Subscriptions settings; Any Event does not grant permissions or create a Slack subscription by itself.
Understand channel scope and execution volume
For a channel-message trigger, invite the bot to every channel in which it should work. A bot that is not present in a channel cannot reliably process that channel’s messages. If you choose Watch Whole Workspace, every matching event in any channel where the bot or app is present can create an n8n execution. Restrict the workflow with an explicit event, channel check or mention rule when the bot does not need workspace-wide coverage.
Register n8n as Slack’s event endpoint
Use the test URL first
- Open the Slack Trigger in n8n and start a test listening session so n8n exposes its Test URL.
- In Slack’s app configuration, open Event Subscriptions and turn the feature on.
- Paste the n8n Test URL into Slack’s Request URL field.
- Wait for Slack to verify the URL. Slack sends a verification request; the URL must be reachable and n8n must be listening for the verification to succeed.
- After verification, add the bot events that correspond exactly to the Slack Trigger selection.
Slack’s Events API is governed by OAuth permission scopes and sends event data to the app’s Request URL. Selecting an event in n8n without subscribing to the same event in Slack produces no trigger executions.
Switch to production deliberately
Slack permits one Request URL per app. During development, the Test URL is convenient because you can watch a single execution. When the workflow is ready, replace that URL with n8n’s Production URL and activate the workflow. Alternatively, use the production URL from the beginning and inspect n8n’s execution logging while testing.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Do not leave Slack pointing at a temporary test endpoint after you finish. If you change the URL, repeat Slack’s verification and confirm that the event subscription still lists the intended bot events.
Add the reply with a Slack node
- Connect a Slack node after the Slack Trigger.
- Select the message or post operation appropriate to your workflow.
- Select the destination channel, or map the channel supplied by the triggering event when the bot should answer where it was called.
- Choose whether the response is a new message or a reply in the originating thread.
- Map the trigger text or the result of downstream nodes into the message field using n8n’s expression picker.
- Run a test with a harmless message, then confirm in Slack that the author is the installed bot and that the reply landed in the intended channel or thread.
Keep routing explicit. A bot that listens to all new messages and then posts to the same channel can create an unintended feedback loop if its own message is received as another matching event. For mention-based bots, require the mention before processing; for broad channel triggers, add a condition that ignores messages authored by the bot or otherwise excludes events that are outputs of the workflow.
Test the complete path before activation
- Confirm that the app is installed in the intended workspace and that the bot has been invited to the test channel.
- Confirm that the n8n credential saves successfully and contains the current Bot User OAuth Token.
- Start the Slack Trigger’s test listener if you are using the Test URL.
- Send exactly the event you selected: mention the bot for Bot/App Mention or post a message in the subscribed channel for New Message Posted to Channel.
- Inspect the trigger execution and verify that the event payload contains the channel and text you expect.
- Run the Slack node and verify the response destination, formatting and thread behavior.
- Test an event that should be ignored, such as an unrelated message when the bot is mention-only.
- Replace the Test URL with the Production URL, activate the workflow and repeat one controlled test.
Testing both a positive and a negative case matters. It demonstrates not only that Slack can reach n8n, but also that the workflow does not answer every event unintentionally.
Security and maintenance practices
Keep permissions narrow
Start with the bot scopes required for posting and triggering, then add conversation history, user or file permissions only when a later step demonstrably needs them. Narrow scopes reduce the impact of a leaked token and make authorization reviews easier.
Protect both secrets
Store the Bot User OAuth Token and Signing Secret in n8n credentials. Do not put either value in a message, a note node, a public workflow export or an environment intended for untrusted users. If either value is exposed, rotate it in Slack and update n8n.
Use request verification in production
Enable signing-secret verification on the Slack Trigger once the secret is stored. This checks the authenticity of incoming requests in addition to relying on an obscure webhook URL. Keep the workflow’s production URL private and expose only the endpoint Slack needs.
Review event breadth as usage grows
A mention trigger usually scales more predictably than whole-workspace listening because people must address the bot. If a business requirement forces broader listening, add filtering and monitor n8n executions so a burst of channel activity does not start unnecessary runs.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteTroubleshoot a bot that does not respond
| Symptom | Likely cause | What to check |
|---|---|---|
| Slack cannot verify the Request URL. | n8n is not listening, the URL is wrong or Slack cannot reach the endpoint. | Start the Test URL listener, copy the current URL exactly, ensure Event Subscriptions is enabled and confirm the n8n instance is reachable. |
| The URL verifies, but no execution starts. | The Slack event subscription and n8n trigger selection do not match. | Compare the selected Bot/App Mention, New Message Posted to Channel or Any Event setting with the bot events listed in Slack. |
| The trigger reports an authorization or API error. | The token type is wrong, the app is not installed in this workspace or required scopes are missing. | Use the Bot User OAuth Token from the current installation, confirm the workspace, and review Bot Token Scopes. The Slack Trigger needs an API access token credential. |
| The bot does not see a channel message. | The bot is not a member of that channel, or the workflow is listening for a different event. | Invite the bot to the channel and verify that New Message Posted to Channel is subscribed in Slack. |
| The bot receives events but cannot post. | The app lacks the posting permission or the destination is invalid. | Check for chat:write, select the correct Slack credential on the Slack node and verify the destination channel or thread mapping. |
| Signature verification fails. | The Signing Secret is missing or belongs to another Slack app. | Copy the secret from the app’s Basic Information page, update the n8n credential and ensure verification is enabled only with the matching secret. |
| A previously working credential suddenly fails. | Slack may have revoked the token. | Slack lists app uninstall, removal of a user’s configuration and deactivation of the authenticating account as revocation conditions. Reinstall or reauthorize the app as appropriate, then replace the token in n8n. |
| The workflow responds repeatedly. | The bot’s own output is being received as another matching event, or the trigger is broader than intended. | Ignore bot-authored events, require an app mention, narrow the channel scope or replace Watch Whole Workspace with a more targeted trigger. |
A repeatable build checklist
- Slack app created in the correct workspace.
- Bot scopes limited to the selected trigger and Slack actions.
- App installed and current Bot User OAuth Token copied.
- n8n Slack credential saved with the token.
- Signing Secret copied from Basic Information.
- Request signature verification enabled when supported by the n8n version; the feature is available from n8n 1.106.0.
- Slack Trigger event matches the subscribed bot event.
- Required
conversations.listandusers.listpermissions are present, with any additional scopes required by the workflow. - Bot invited to every channel it must read or answer.
- Test URL verified during development, then replaced by the Production URL for the activated workflow.
- Slack node destination and thread mapping tested with a controlled message.
- Negative test confirms the bot ignores events outside its intended scope.
Choosing the right implementation for your use case
Use app mentions for an assistant
Choose Bot/App Mention when people should explicitly ask the bot for help. It keeps the conversational boundary clear and avoids starting an execution for every ordinary channel message. Add a downstream condition if the workflow should respond only to particular commands or prefixes.
Use channel messages for monitoring or routing
Choose New Message Posted to Channel when the workflow must classify, route or record ordinary messages. Limit the bot to the channels that need it, invite it there, and account for the higher execution volume.
Use Any Event for an event-driven integration
Choose Any Event only when the Slack event you need is not represented by a named n8n option. You remain responsible for adding the exact bot event in Slack, granting its scopes and handling the payload in n8n.
Separate development from production
The Test URL is useful for observing one workflow run while configuring Slack. The Production URL is the stable endpoint for an active workflow. Because Slack allows one Request URL per app, coordinate the switch rather than expecting both endpoints to receive events simultaneously.
Once the app, credential, event subscription and reply node are aligned, n8n provides a visual path from Slack event to automated response without requiring a separate web server. The reliability of that path depends on matching scopes and events, keeping the bot in the right channels, using the correct token, verifying requests and deliberately moving from the test endpoint to the production endpoint.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
