Block 1 - Start thread
- Type / Role
- n8n-nodes-base.slack - slack
- Config choices
- Version 2
This workflow is provided as-is. Please review and test before using in production.
Use case Slackbots are super powerful. At n8n, we have been using them to get a lot done.. But it can become hard to manage and maintain many different operations that a workflow can do. This is th...
n8n-nodes-base.slack, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.stickynote, n8n-nodes-base.set, n8n-nodes-base.executeworkflow, n8n-nodes-base.merge, n8n-nodes-base.switch
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mutasem.
Original n8n.io sourceSlackbots are super powerful. At n8n, we have been using them to get a lot done.. But it can become hard to manage and maintain many different operations that a workflow can do.
This is the base workflow we use for our most powerful internal Slackbots. They handle a lot from running e2e tests for Github branch to deleting a user. By splitting the workflow into many subworkflows, we are able to handle each command seperately, making it easier to debug as well as support new usecases.
In this template, you can find eveything to setup your own Slackbot (and I made it simple, there's only one node to configure 😉). After that, you need to build your commands directly.
This bot can create a new thread on an alerts channel and respond there.
Or reply directly to the user.
It responds for help request to return a help page.
It automatically handles unknown commands.
It also supports flags and environment variables. For example /cloudbot-test info mutasem --full-info -e env=prod would give you the following info, when calling subworkflow.
alerts_channel with alerts channel to start threads oninstance_url with this instance url to make it easy to debugslack_token with slack bot token to validate requestslack_secret_signature with slack secret signature to validate requesthelp_docs_url with help url to help users understand the commandscommands in Set Config. Each command must be mapped to a workflow id with an Execute Workflow Trigger nodeThis catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 34 workflow blocks. Download the JSON for the full node graph.
| Workflow | 🤖 Advanced Slackbot with n8n |
|---|---|
| Complexity | advanced |
| Nodes | 34 |
| Categories | DevOps |
| Author | Mutasem |
| Published | 01 Mar 2024 |
Use the JSON export at /data/workflows/2157/2157.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Use case Slackbots are super powerful. At n8n, we have been using them to get a lot done.. But it can become hard to manage and maintain many different operations that a workflow can do. This is th...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.