Send notifications
Format with Block Kit
blocks in trigger overrides when you call the API. See Format messages with Block Kit for examples, including _passthrough for raw Slack API fields.Configure a Slack app
Before integrating Slack chat with Novu, you must create and configure a Slack app. The Slack app manages the OAuth permissions, bot token scopes, and redirect URLs needed for Novu to connect to your users’ workspaces securely.Create a Slack app
First, you need to create a Slack app. This provides you with the credential you need to create a Slack integration in Novu.Open the Slack API dashboard
Create an app
Select From scratch
Enter app name and workspace

Create the app
- App ID
- Client ID
- Client Secret

Configure scopes (Permissions)
Your app needs permission to perform actions like sending messages or reading channel lists.Open OAuth & Permissions
Open Scopes
Add an OAuth Scope

Add recommended scopes
chat:writechat:write.publicchannels:readgroups:readusers:readusers:read.email- (optional)
incoming-webhookif you want Slack’s built-in channel picker.
Set the redirect URL
This tells Slack where to send the user after they successfully authorize your app.Open OAuth & Permissions
Open Redirect URLs
Add a redirect URL

Paste the Novu callback URL
Save the URLs
Configure Slack integration in Novu
Once your Slack app is set up, the next step is to configure the Slack Chat integration inside Novu.Log in to the Novu dashboard
Open Integrations Store
Connect a provider
Select Slack
Fill in credentials
- Application Id: Paste your Slack app App ID.
- Client ID: Paste your Slack App Client ID.
- Client Secret: Paste your Slack App Client Secret.
- Redirect URL (Optional): Enter the URL where you want users to be redirected to after they successfully connect their workspace. If there is no redirect URL, then Novu closes the tab immediately after the OAuth flow completes.

Create the integration
- Generate OAuth (Connect Slack) URLs for your users
- Receive Slack’s OAuth callback.
- Store workspace tokens as connections.
Let users connect their Slack workspace
To send messages to Slack, your users must first authorize Novu to access one of their Slack workspaces. This authorization happens through Slack’s OAuth flow, which Novu generates and manages for you.Generate the OAuth URL
When a user clicks Connect Slack in your application, your backend should request a unique authorization URL from Novu.- Node.js
- Python
- Go
- PHP
- .NET
- Java
- cURL
Redirect the user
Once your backend returns theoauthUrl, open it in a new tab or window.
Review permissions
Approve authorization
Redirect to Novu
Novu exchanges the code
Novu creates a connection
connectionIdentifier when creating endpoints.You can also provider a custom connectionIdentifier to the generateChatOAuthUrl() and then connection with such identifier will be created instead of randomly generated one.generateChatOAuthUrl(), you can run the Slack OAuth flow with your own app, use the access token with Slack’s APIs directly, then register the workspace with Novu via channelConnections.create (or POST /v1/channel-connections):Choose delivery destinations
After a workspace is connected, you or users decide where in Slack to send the messages. This can either be a Slack channel, to a user or an incoming webhook URLs. After the delivery location has been selected, a Slack endpoint is then created for that location.- Slack channel
- Slack user
- Incoming webhook
Get the channel ID
Create the endpoint
- Node.js
- Python
- Go
- PHP
- .NET
- Java
- cURL
Send notifications
Once you have at least one Slack connection, and one or more Slack endpoints. You can trigger the workflow:- Node.js
- Python
- Go
- PHP
- .NET
- Java
- cURL
Find Slack endpoints
Use the workspace connection
Deliver messages
body. For rich Slack messages (sections, buttons, context blocks), use trigger overrides at send time or Framework provider overrides in code-first workflows. Digest summaries in the dashboard work as plain text using digest variables.Format messages with Block Kit
The Chat step in the Novu dashboard sends a plain text message body to Slack. There is no Block Kit editor in the workflow UI today. You still have a few ways to send richer Slack messages:Plain text and digest summaries
For digest workflows built in the dashboard, use digest variables in the Chat step body to build a text summary. For example:Send Block Kit with trigger overrides
To send Slack Block Kit messages from a dashboard workflow, passblocks in the overrides object when you trigger the workflow. The Chat step body from your template is still sent as the fallback text field unless you override it.
Copy the step identifier from your workflow in the dashboard and use it under overrides.steps.
- Node.js
- Python
- Go
- PHP
- .NET
- Java
- cURL
slack-chat-step with the step identifier from your workflow. Step-level overrides take priority over workflow-level overrides.
Workflow-level overrides
If your workflow has a single Slack Chat step, you can apply Block Kit to all Slack steps in that workflow without targeting a step ID:Send extra Slack fields with _passthrough
Use _passthrough when you need raw Slack chat.postMessage fields that are not exposed in the dashboard. Values in _passthrough.body are merged last and take priority over other override fields.
- Node.js
- Python
- Go
- PHP
- .NET
- Java
- cURL
Block Kit with digest workflows
Trigger overrides are set when you call the trigger API. They work well when each trigger carries the data you need to build the message. For digest workflows, Novu batches multiple triggers into one notification. The Chat step body can use digest variables to summarize batched events, butoverrides are not re-evaluated with that aggregated data. To build Block Kit dynamically from a digest batch, use Framework provider overrides in a code-first workflow.
Using Slack with agents
Slack is a supported agent provider. Connect your Slack app to an agent so users can message in channels or DMs and get replies in the same thread, without building Slack event handling yourself.Build agents on Slack
What you get
When Slack is connected to an agent:- Users message your app in Slack and your agent responds in the same thread
- Conversations appear in the dashboard under Agent Conversations
- Supported content includes text, markdown, files, interactive cards, reactions, and typing indicators
Agent conversations vs. workflow notifications
Related
Trigger overrides
blocks and _passthrough fields when triggering a workflow from your application.