n8n + Slack: what you can automate

Start with one flow: approvals in Slack

Here is the workflow I point most teams to first, because it removes a bottleneck everyone recognises: a request sits in someone’s inbox for two days waiting for a yes. With n8n, the request goes to the approver in Slack with buttons, and the workflow carries on the moment they click.

1. Webhook (or n8n Form Trigger) receives a purchase, discount or time-off request with the requester, amount and reason.
2. IF checks the amount. Small requests skip straight to the log; anything over your limit goes to a person.
3. Slack, Message > Send and Wait for Response, with the response type Approval and the approval type Approve and Disapprove. It posts the request to the approver or a channel and pauses the workflow. Set Limit Wait Time so a request does not wait forever.
4. IF reads the response and splits approved from declined.
5. Google Sheets, Append Row, records the decision and who made it. A second Slack node, Message > Send, tells the requester the outcome.

If you need more than yes or no, the same operation supports Free Text and Custom Form response types, so the approver can add a note or adjust the amount before the workflow continues.

Who this is for

Slack is where many teams already make decisions, so it is the natural place for workflows to report in and ask for input. This page is for operations, sales and support leads who want fewer “did anyone see this?” messages and fewer things lost between apps. The business case is response time and attention: the right person hears about the right event once, in the place they already look, with enough context to act.

Four more Slack automations

• Alert a channel about hot leads. A form webhook or your CRM’s trigger starts the flow, an AI or IF step decides if the lead is hot, and Slack Message > Send posts it to the sales channel with a link. Fast follow-up is where deals are won, which is the idea behind the speed-to-lead agent lesson.
• Post a daily metrics summary. A Schedule Trigger pulls yesterday’s numbers from a sheet or database, a Summarize node totals them, and Slack posts a short message with Blocks formatting. One message replaces several dashboards nobody opens.
• Turn Slack messages into tasks or tickets. The Slack Trigger with the Bot / App Mention event fires when someone tags your bot (“@ops add this”). The workflow creates a task in Asana, ClickUp or Jira with the message text, then Reaction > Add puts a checkmark on the original message so people know it was captured.
• Send workflow errors to an ops channel. An Error Trigger node in a separate error workflow, set as the Error Workflow in each workflow’s settings, posts the failed workflow’s name, the error and a link to the execution. You find out about failures from Slack, not from a customer.

Slack API details that trip people up

• One request URL per app. The Slack Trigger receives events through your Slack app’s event subscription, and Slack only sends to one URL per app. That means test and production webhook URLs cannot both be live. To test a published workflow you switch the URL in Slack, then switch it back. The test vs production URL glossary entry explains the difference.
• Leave token rotation off. n8n’s docs warn that rotation makes tokens expire after 12 hours, which breaks the credential, and it cannot be turned off again on that app.
• The bot only sees channels it is in. Events like New Message Posted to Channel and Reaction Added only fire for channels your app has joined, and posting to a private channel needs the bot invited first.
• Slack retries slow responses. Slack expects a 2xx response within three seconds and retries a failed delivery up to three times. If your n8n instance is slow or restarting, the same event can arrive more than once, so dedupe on the event or message ID with the Remove Duplicates node when the action matters.
• Posting has a pace limit. Slack’s docs say chat.postMessage generally allows about one message per second to a given channel. If a workflow posts a message per row, batch them into one summary instead.
• Scopes come first. Each operation maps to a Slack API method with its own scopes. Add them in the Slack app before testing, and reinstall the app after changing them. Message > Search in current node versions needs a user token, not a bot token.

DIY or hire help

Outgoing alerts are the easiest place to start with n8n: the Slack node, a bot token and a channel are all you need. The Slack Trigger and approval flows take more care, because they involve a Slack app, event subscriptions and webhook URLs. Hire help when Slack becomes the front door for real decisions (approvals that release money, tickets for customers) or when several teams share one Slack app. You can see the operations work I do on the operations automation page.