Integrating Slack notifications with n8n can streamline your workflow and ensure you never miss important updates. This step-by-step guide is designed for beginners looking to set up this powerful automation. Follow these instructions to connect Slack with n8n and start receiving notifications seamlessly.

Prerequisites

  • A Slack workspace with permission to create apps and webhooks
  • An n8n instance running locally or on a server
  • Basic understanding of n8n workflows

Step 1: Create a Slack App

Log in to your Slack workspace and navigate to the Slack API portal. Click on Create an App and choose From scratch. Give your app a name and select your workspace.

Configure Bot Permissions

Once your app is created, go to OAuth & Permissions. Under Scopes, add the following bot token scopes:

  • chat:write
  • channels:read
  • groups:read

After adding scopes, click Install App to Workspace and authorize the permissions. Save the Bot User OAuth Token displayed.

Step 2: Set Up n8n Workflow

Access your n8n editor. Create a new workflow to handle Slack notifications.

Add a Trigger Node

Choose a trigger node based on your use case, such as Webhook or Schedule. Configure it according to when you want notifications to be sent.

Add a Slack Node

Drag the Slack node into your workflow. Set the operation to Send Message. In the node's settings, input your Bot User OAuth Token from Slack.

Specify the channel or user to receive the message. Compose your notification message in the text field.

Step 3: Test and Activate

Save your workflow and run a test to ensure the notification is sent correctly. Adjust message content or trigger conditions as needed.

Once satisfied, activate your workflow. Your Slack notifications will now be sent automatically based on your configured triggers.

Conclusion

Connecting Slack with n8n enables efficient communication and automation within your team. By following this simple setup process, you can customize notifications to keep everyone informed and streamline your workflows effectively.