To build a Slack bot with n8n, create and install a Slack app, grant only the bot scopes your workflow needs, copy its Bot User OAuth Token into an n8n Slack credential, and connect a Slack Trigger to a Slack node. Slack Event Subscriptions then deliver matching events to the n8n webhook URL, while the Slack node posts the bot’s response. The reliable build order is: app and permissions, credentials, trigger, event webhook, reply action, testing, and security.
Antihost offers VPS plans with one-click n8n, NVMe storage and a 14-day free trial.
What the finished Slack bot looks like
An n8n Slack bot is an event-driven workflow rather than a single switch in Slack. Slack sends an event to an n8n webhook, the Slack Trigger starts an execution, and later nodes decide whether and how to respond. A simple conversational flow is:
As an Amazon Associate I earn from qualifying purchases.
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 minute- A person mentions the bot or posts a message that matches the trigger.
- Slack sends the event payload to the app’s configured Request URL.
- n8n verifies the request when signing-secret verification is enabled, then starts the workflow.
- Logic in n8n extracts the message and produces a result.
- A Slack node posts a reply to a selected channel or thread.
That separation matters. The Slack app controls authorization and event delivery; the n8n credential stores the token and signing secret; the workflow controls filtering, processing, and replies. A bot can therefore be narrowly scoped to explicit mentions, or it can process broader channel activity when the workspace and permissions justify it.
Plan the bot before creating anything
Choose the event boundary
For a conversational bot, Bot/App Mention is usually the clearest starting point. The bot receives messages when it is explicitly addressed, which reduces accidental replies and unnecessary executions. If your automation must react to every qualifying message in a channel, choose New Message Posted to Channel instead.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
n8n also exposes triggers for App Home Opened, reactions, file events, new public channels, and new users. If the event you need is not listed in the selector, choose Any Event and configure the Slack app to send the corresponding bot event.
Decide how broad the workflow should be
A channel-specific workflow is easier to reason about than one that watches everything. The Watch Whole Workspace option causes an execution for every matching event in any channel where the bot or app is present. n8n warns that this should be used cautiously: it expands the event volume and the number of places in which the bot can act.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
List the actions and data you actually need
Write down the events the bot must receive, the Slack operation it must perform, and any message, conversation, user, or file data it must read. This list becomes the basis for least-privilege scopes. Do not begin by granting every available permission and trying to remove access later.
Create the Slack app
Start in Slack’s API Apps area
- Open Slack’s API Apps area and choose to create an app.
- Create it from a manifest or from scratch. n8n recommends using a manifest because it configures the required scopes in one step.
- Give the app a recognizable name and select the workspace in which you will test it.
The app is the identity that Slack will install and authorize. The n8n workflow does not receive a usable bot identity until this app has been installed to the intended workspace.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Use scopes that match the workflow
In the app configuration, add bot scopes for the selected events and actions. Common examples are:
| Workflow need | Typical scope or permission area | Why it may be needed |
|---|---|---|
| Post a reply | chat:write |
Allows the bot to send messages or posts as the bot. |
| Read conversations or message history | Conversation read/history scopes | Required when the workflow must inspect channel details or previous messages. |
| Read user information | User scopes | Use only when the workflow needs user identity or profile data. |
| Work with files | File scopes | Use only for workflows that receive, inspect, or otherwise handle files. |
The exact combination depends on the events and Slack operations in your workflow. The Slack Trigger needs permissions for conversations.list and users.list at minimum, with additional scopes determined by the trigger and actions you select.
Install the app and put its token in n8n
Install and authorize the app
- In Slack’s app configuration, install the app to the target workspace.
- Review the authorization screen and approve the requested bot scopes.
- After installation, open the OAuth section and copy the Bot User OAuth Access Token.
Slack states that selecting Bot Token Scopes and installing the app provides a Bot User OAuth Access Token. Calls made with that bot token post as the bot, so treat it as a secret rather than as ordinary workflow text.
Create the n8n Slack credential
- In n8n, create a Slack credential for the Slack nodes you will use.
- Paste the Bot User OAuth Token into the credential’s token field.
- Save the credential and select it on both the Slack Trigger and any Slack node that sends or reads data.
The Slack Trigger requires an API access token credential. For the Slack node, n8n recommends OAuth2. Follow the credential type shown by your n8n version and node; do not paste a token into a message field or hard-code it in an expression.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Add the signing secret
Open the app’s Basic Information page in Slack and copy the Signing Secret into the n8n Slack credential when the credential provides that field. n8n recommends enabling request signature verification for the Slack Trigger for additional security. The signing-secret verification option is available from n8n 1.106.0.
Configure the Slack Trigger in n8n
Select the trigger event
- Create a new n8n workflow and add a Slack Trigger node.
- Select the Slack credential containing the bot token and, when enabled, the signing secret.
- Choose Bot/App Mention for an explicit conversational bot, or New Message Posted to Channel for channel-message automation.
- Choose another listed event, or select Any Event when Slack must deliver an event that is not represented by a named n8n option.
Keep the event choice narrow at first. A trigger that receives more events than the workflow can safely handle will create extra executions and makes it easier to post an unintended reply.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Account for the trigger’s workspace lookups
n8n documents conversations.list and users.list as minimum permissions for the Slack Trigger. Add the corresponding access required by your Slack app, then add any further scopes needed for history, files, users, or the action node. If the trigger can list a channel or user in n8n but the eventual Slack operation cannot access it, the workflow can still fail later when it tries to read or post.
Register n8n as Slack’s event endpoint
Use the n8n Webhook URL
- Open the Slack app configuration and turn on Event Subscriptions.
- In n8n, open the Slack Trigger and copy its Webhook URL.
- Paste that URL into Slack’s Request URL field.
- Wait for Slack to verify the URL.
- After verification succeeds, add the bot events that correspond to the n8n trigger selection.
Slack’s Events API sends event data to the app’s Request URL, and the available events are governed by OAuth permission scopes. The event subscription and the n8n trigger must agree: subscribing to one event while selecting another in n8n will not produce the behavior you expect.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Respect Slack’s one-URL limit
Slack permits one Request URL per app. This affects testing and deployment. n8n provides a Test URL and a Production URL; Slack cannot simultaneously point the same app at both.
- For a short test, put n8n’s Test URL in Slack, trigger an event, and inspect the execution.
- When the workflow is ready, replace the Request URL with n8n’s Production URL and activate the workflow.
- Alternatively, use the Production URL while testing and rely on execution logging, but keep the URL choice deliberate because changing it replaces the app’s current endpoint.
Add the Slack reply node
Choose the destination explicitly
- Add a Slack node after the trigger and any processing nodes.
- Select the message or post operation appropriate to your workflow.
- Choose the destination channel or thread rather than relying on an implicit destination.
- Map the incoming trigger text or downstream result into the message field.
- Run a test event and confirm that the bot posts where intended.
Keep routing and formatting explicit. A workflow that receives several event types should filter them before the Slack node, so a reaction, file event, or unrelated message cannot accidentally become a public answer. If the bot should reply in a thread, map the thread destination supplied by the incoming event instead of always posting a new top-level message.
Prevent self-replies and broad responses
For mention-based bots, process only the intended mention event and make the response condition clear. For channel-message triggers, add a decision step that identifies the messages the bot should answer. This is especially important when the app is present in multiple channels or when the workflow uses workspace-wide watching.
Test, activate, and deploy safely
Run a controlled test
- Invite the bot to the test channel if the workflow depends on channel membership.
- Use the Slack Request URL that matches the n8n workflow mode: Test URL for a temporary test, or Production URL for an active workflow.
- Send one event that exactly matches the selected trigger, such as an explicit app mention.
- Inspect the n8n execution data to confirm that the event arrived, the expected text is available, and the destination values are correct.
- Confirm that the Slack node posts one response and that it is in the intended channel or thread.
Move from test to production
After verification, activate the workflow and change Slack’s Request URL to the n8n Production URL if you tested with the Test URL. Send another event after the change. Because Slack allows one Request URL per app, the production cutover is a replacement, not a second endpoint running in parallel.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Check the deployment boundary
- The Slack app is installed in the workspace where the event is being generated.
- The bot is present in any channel required by the selected trigger or reply.
- The event subscription remains enabled and verified.
- The subscribed bot event matches the Slack Trigger selection.
- The active Slack Request URL is the intended n8n Test or Production URL.
Security and permission decisions
Keep scopes least-privilege
Every additional scope expands what the bot can access or do. Start with chat:write for a reply-only bot, then add conversation history, user, or file access only when a workflow step requires it. A bot that only answers mentions should not receive broad history or file permissions merely because another possible workflow might need them later.
Verify Slack requests
Store the Signing Secret in the n8n Slack credential and enable request signature verification for the Slack Trigger. This lets n8n verify that incoming requests are signed for the Slack app rather than accepting an unauthenticated request that happens to reach the webhook.
Protect and rotate credentials
Keep the Bot User OAuth Token and Signing Secret inside n8n credentials. If a token suddenly stops working, check whether Slack revoked it. Slack lists uninstalling the app, removing a user’s configuration, and deactivation of the authenticating account as revocation conditions. Reinstall or reauthorize the app as appropriate, update the n8n credential with the current token, and retest the workflow.
Choose the right trigger and deployment mode
| Decision axis | Narrow option | Broad option | Operational consequence |
|---|---|---|---|
| Trigger breadth | Bot/App Mention | New Message Posted to Channel or Watch Whole Workspace | Explicit mentions reduce unintended executions; broad watching processes more activity and needs stricter filtering. |
| Scope breadth | Only scopes required for posting and the selected event | Additional history, user, or file scopes | Least privilege limits access; broader scopes support richer workflows but increase exposure. |
| Deployment stage | n8n Test URL | n8n Production URL | The Test URL is suited to a controlled test; the Production URL is the endpoint for the active workflow. |
| Security posture | Signing-secret verification enabled | Verification absent | n8n recommends verification for additional security; the signing secret must be entered for it to work. |
Troubleshoot a bot that does not respond
Slack never verifies the Request URL
- Confirm that Event Subscriptions is enabled.
- Check that the URL copied from the Slack Trigger is the correct n8n Webhook URL, without an accidental switch between Test and Production modes.
- Make sure the n8n workflow is in the mode required for that URL and can receive the verification request.
- If signing-secret verification is enabled, confirm that the Signing Secret from Slack’s Basic Information page is in the n8n credential.
The trigger receives no events
- Verify that the app is installed in the intended workspace.
- Confirm that the Slack bot event subscribed in Event Subscriptions matches the event selected in n8n.
- For channel-specific messages, invite the bot to the channel.
- Check that the app has the scopes required for the trigger, including the documented minimum access for
conversations.listandusers.list. - If using workspace-wide watching, confirm that the bot or app is present where the event occurs and remember that only matching events start executions.
The trigger runs but the Slack node fails
- Recheck that the credential contains the current Bot User OAuth Token and that the token type is appropriate for the node.
- Confirm that the app has the action’s required scope, such as
chat:writefor replies. - Check the selected channel or thread and ensure the bot can access that destination.
- If credentials worked previously and then failed, investigate Slack token revocation and reinstall or reauthorize the app when necessary.
The bot replies too often
- Replace a broad channel or workspace trigger with Bot/App Mention when explicit addressing is sufficient.
- Add a filter before the Slack node so only the intended event type and message condition can reach the reply step.
- Inspect whether the bot’s own messages are being included in the matching events and tighten the condition to prevent a reply loop.
The bot replies in the wrong place
Review the Slack node’s destination and thread mapping. Select the channel explicitly, and when a threaded response is intended, map the incoming event’s thread destination rather than creating a new top-level post for every execution.
Quick Recap
A repeatable build checklist
- Define the exact event the bot should handle and the Slack operation it should perform.
- Create a Slack app from a manifest or from scratch in Slack’s API Apps area.
- Add only the bot scopes required by that event and operation.
- Install the app to the target workspace and copy the Bot User OAuth Access Token.
- Create the n8n Slack credential and enter the token.
- Copy the Signing Secret from Basic Information and enable request signature verification when available.
- Add Slack Trigger, select the credential, and choose the matching event.
- Turn on Event Subscriptions, paste the n8n Webhook URL into Request URL, and wait for verification.
- Subscribe to the matching Slack bot events.
- Add a Slack node, choose the message or post operation, and map the channel, thread, and response text.
- Test with one controlled event and inspect the n8n execution.
- Switch Slack from the Test URL to the Production URL when deploying the active workflow.
- Recheck channel membership, scopes, token status, and signature verification after any app or workflow change.
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.
