- Decisions made in chat that never reach the project page
- Linking your accounts and choosing your alerts
- Sending chat messages and tasks into a database
- Posting database changes to a team channel
- Threads, private DMs and per-person setup
- Zapier and Workflow Builder as the other routes
- My advice for a small team
- Frequently asked questions
Connect Notion to Slack natively from Settings, then Notifications, then Add new account under Slack notifications. After that you can send Slack messages to a Notion database with /notion create, file tasks with /notion task, and get Notion alerts in Slack. Zapier and similar tools still work as before.
Decisions made in chat that never reach the project page
It's the same story in most small teams. Someone agrees a change in a channel, everyone reacts with a thumbs up, and a week later nobody can find it. The native connection fixes that in both directions: messages go into your databases, and changes in your workspace show up as alerts in chat.
Here's how I'd think about it: alerts suit the person who owns the project, the commands suit everyone who talks in chat, and database automations suit a whole team that needs to see changes. One thing to know first: you can't pick and choose. Installing the integration gives you all of its features at once.
Linking your accounts and choosing your alerts
- In Notion, go to Settings in the sidebar, then Notifications.
- Find Slack notifications and click Add new account, then complete the sign-in for your Slack workspace.
- Open the dropdown next to Slack notifications, choose your workspace, and toggle Activity in your workspace on, or leave it off for mentions only.
Mentions only is the quiet option. All activity adds comments on pages you own, changed database properties, page invites and access requests. Start with mentions and add more if you're missing things.
Connecting is personal. When one person connects, everyone else in the workspace sees link previews for shared pages, but each user has to connect individually to use the commands.
Sending chat messages and tasks into a database
Type /notion create in a channel, or use the Send to Notion option on a message's menu, pick the target database, add a title and properties, then Save. That turns a chat message into a database page.
For action items, /notion task (or Create task in Notion) files a task with a name, assignee, status, due date and description. If you're new to how these tables work, my guide to Notion databases explains the properties you'll be filling in.
Posting database changes to a team channel
Open a database, select the three-dot menu, choose Automations, add a trigger such as Page added, then add the Send Slack notification action and pick a channel. You'll need Full Access to the database to set this up.
Automation actions (a button, a database button or a database automation) can post rich text, links, mentions and variables such as @now and @trigger.person. The help page says this feature is limited to certain plans, so check yours before you plan a process around it.
If you don't have Full Access, ask the database owner to set it up, or to give you that access for the job. There's no central list of these notification workflows. Each one lives in its own database, so keep a note of where you've set them up.
Threads, private DMs and per-person setup
The Notion Help Center page on integrating Slack is clear on three limits. The slash commands don't work inside threads, only at channel level. Automations can't send alerts to private DMs. And setup is per person, so one admin connecting doesn't give the whole team the commands. If your team lives in threads, that first limit will be the one you feel most.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Zapier and Workflow Builder as the other routes
Notion says third-party integrations such as Zapier continue to work as before. Zapier pairs the two apps with a trigger, such as a new comment, that starts the automation.
Slack Workflow Builder can add connector steps that carry out an action in a third-party service, which suits you if your process already starts in chat. If you're weighing connector tools, my look at how n8n and Zapier compare is a good starting point.
My advice for a small team
Connect it, set alerts to mentions only, and teach everyone one habit: when a decision lands in a channel, /notion task it there and then, at channel level rather than in the thread. Add a database automation for your busiest project only once the team trusts the basics. Reach for a connector when you need custom logic, not before.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Does Notion connect to Slack natively?
Yes, through Settings, Notifications, Slack notifications, Add new account.
Can I send a Slack message to a Notion database?
Yes, with /notion create or Send to Notion on a message, at channel level.
Can it post to a private DM?
Not from automations. The help page says you can't select private DMs.
Do I still need Zapier?
Only for custom logic. Third-party integrations continue to work as before.
Who can set up database notifications?
Someone with Full Access to the database.
