Notion meets Slack for daily task DMs that land
Tasks live in Notion. Work happens in Slack. And somehow you’re still the one chasing updates, re-pinging people, and digging through databases to find what’s due.
This Notion Slack reminders setup hits project managers hardest, but team leads and small agency owners feel it too. You get daily, automated DMs that tell each person what’s open and when it’s due, so fewer things slip quietly past deadline.
Below, you’ll see exactly how this workflow pulls incomplete Notion tasks, matches assignees to Slack users, and sends a clean morning message at 9:00 AM on weekdays.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Notion meets Slack for daily task DMs that land
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Filter incomplete tasks only", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Get All Slack Users (Darryn)"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/notion.dark.svg' width='40' height='40' /></div><br/>Get To Dos from Tasks Database"]
n3@{ icon: "mdi:cog", form: "rounded", label: "Schedule Mon - Friday @ 09:0..", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Notion User Emails", pos: "b", h: 48 }
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Slack User Full Name", pos: "b", h: 48 }
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Send a Direct Message to Use.."]
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Send a Direct Message to Use.."]
n8@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Switch for Notion Users Emails", pos: "b", h: 48 }
n9@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Filter Slack User 1 Full Name", pos: "b", h: 48 }
n10@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Filter Slack User 2 Full Name", pos: "b", h: 48 }
n4 --> n5
n5 --> n2
n0 --> n1
n1 --> n8
n9 --> n6
n10 --> n7
n2 --> n0
n8 --> n9
n8 --> n10
n3 --> n4
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0,n8,n9,n10 decision
class n2 database
classDef customIcon fill:none,stroke:none
class n1,n2,n6,n7 customIcon
The Challenge: Keeping Notion tasks from going stale
If your tasks are stored in Notion but your day runs through Slack, reminders tend to fall into a weird gap. People don’t open the database first thing. They skim messages. So tasks sit “in progress” for days, due dates creep up, and you end up doing the unglamorous work of follow-up. Honestly, it’s not just the time. It’s the constant mental load of remembering who owes what and when, then wording yet another nudge so it doesn’t sound passive-aggressive.
It adds up fast. Here’s where it breaks down in real teams.
- You spend about 10 minutes each morning checking Notion and writing reminders in Slack.
- Assignees miss tasks because the “source of truth” isn’t where they live all day.
- Manual pings are inconsistent, which means some work gets chased while other work quietly stalls.
- When due dates are buried, you discover problems late, usually in a meeting.
The Fix: Daily Slack DMs pulled straight from Notion
This workflow turns your Notion database into a daily, personalized Slack reminder system. Every weekday morning at 9:00 AM, it pulls your tasks from Notion, filters out anything already marked “Done,” and then figures out who owns what. Next, it looks up your Slack user directory, matches the Notion assignee to the right Slack account (using email/name mapping you control), and sends each person a direct message with their open tasks and due dates. The result is simple: people start the day seeing what they need to move forward, without you acting as the human router.
The workflow starts on a schedule (weekday mornings). Then Notion tasks are retrieved and filtered. Finally, Slack user matching routes tasks to the correct person, and each owner gets a DM that feels personal because it is.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say you have a 6-person team and each person carries about 5 open tasks in Notion. Manually, a lead might spend 10 minutes pulling tasks plus another 5 minutes writing pings, so roughly 15 minutes per weekday (about an hour a week). With this workflow, the “work” is basically zero after setup: it triggers at 9:00 AM, pulls tasks, and sends the DMs automatically. People get the list before standup, and you stop playing reminder-whack-a-mole.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Notion for the tasks database and assignees.
- Slack to deliver DMs to each task owner.
- Notion + Slack credentials (create/connect inside n8n credential settings)
Skill level: Beginner. You’ll mostly be connecting accounts and updating a few fields for user mapping.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
Weekday morning schedule trigger. A Cron node runs the automation at 9:00 AM, Monday through Friday, so reminders arrive at a predictable time.
User mapping is defined upfront. The workflow sets known Notion user emails and the Slack naming you want to match against, which keeps routing reliable when people have nicknames or display-name quirks.
Notion tasks are retrieved and cleaned. It pulls tasks from your chosen Notion database, then filters out anything already marked “Done” so people only see what still needs attention.
Slack users are fetched, then each task gets routed. The workflow grabs the Slack directory, checks who the Notion assignee is, matches that person to the right Slack user, and sends a DM with task details and due dates.
You can easily modify the schedule time or the message format based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Cron Trigger
Set the schedule that kicks off the workflow each weekday morning.
- Add or open the Weekday Morning Trigger node.
- Set Trigger Times → cronExpression to
0 9 * * 1,2,3,4,5. - Confirm the trigger connects to Define Notion User Emails as the first step in the flow.
Tip: The schedule runs at 9:00 AM Monday–Friday in your n8n instance time zone. Adjust the cron expression if your team is in a different time zone.
Step 2: Connect Notion
Define Notion user emails and connect to the task database.
- Open Define Notion User Emails and set User 1 Notion Email to
[YOUR_EMAIL]. - Set User 2 Notion Email to
[YOUR_EMAIL]in the same node. - Open Retrieve Tasks from Notion and set Resource to
databasePageand Operation togetAll. - Set Database ID to your tasks database (currently
[YOUR_ID]). - Credential Required: Connect your notionApi credentials in Retrieve Tasks from Notion.
⚠️ Common Pitfall: If the Notion database lacks a Status field or an assignee field labeled Notion User, the filtering and routing will fail.
Step 3: Set Up Processing and Routing
Map Slack names, filter completed tasks, and route tasks to the right assignee.
- Open Map Slack User Names and set User 1 Slack Full Name to
User Aand User 2 Slack Full Name toUser B. - In Exclude Completed Tasks, keep the filter condition: Value 1 to
{{ $json.Status }}, Operation tonotEqual, and Value 2 toDone. - In Route by Notion Assignee, verify the rules use these expressions:
{{ $('Exclude Completed Tasks').item.json['Notion User'].toString() }}compared against{{ $('Define Notion User Emails').item.json['User 1 Notion Email'] }}and{{ $('Define Notion User Emails').item.json['User 2 Notion Email'] }}. - Confirm Route by Notion Assignee outputs to both Match Slack User A and Match Slack User B in parallel.
Step 4: Configure Slack Outputs
Fetch Slack users, match assignees, and send direct messages.
- Open Fetch Slack User Directory and set Resource to
user, Operation togetAll, and Authentication tooAuth2. - Credential Required: Connect your slackOAuth2Api credentials in Fetch Slack User Directory.
- In Match Slack User A, set the comparison to
{{ $json.profile.real_name }}equals{{ $('Map Slack User Names').item.json['User 1 Slack Full Name'] }}. - In Match Slack User B, set the comparison to
{{ $json.profile.real_name }}equals{{ $('Map Slack User Names').item.json['User 2 Slack Full Name'] }}. - Open Send DM to User A and set Channel to
{{ $json.id }}and Text to# TO DO. - Set the attachment title to
=☑️ {{ $('Exclude Completed Tasks').item.json.Task }} (Due: {{ $('Exclude Completed Tasks').item.json.Due.start }})and keep mrkdwn enabled. - Credential Required: Connect your slackOAuth2Api credentials in Send DM to User A and Send DM to User B.
- Mirror the same configuration in Send DM to User B with Channel set to
{{ $json.id }}and the same attachment expression.
Tip: If Slack display names don’t match exactly, update the full name strings in Map Slack User Names to prevent the filters from excluding users.
Step 5: Test and Activate Your Workflow
Run a manual test, verify Slack messages, and activate the workflow for daily use.
- Click Execute Workflow to run the flow from Weekday Morning Trigger.
- Verify Retrieve Tasks from Notion returns tasks and Exclude Completed Tasks filters out those with
Statusequal toDone. - Confirm that Send DM to User A and Send DM to User B post messages to the correct Slack users with the task title and due date.
- When results look correct, toggle the workflow to Active for scheduled weekday runs.
Watch Out For
- Notion credentials can expire or need specific permissions. If things break, check your Notion integration access and the selected database sharing settings first.
- Slack DMs can fail if the app is missing scopes like reading users or posting messages. If you see user-matching issues, re-check the Slack OAuth scopes and refresh the connection in n8n.
- The workflow routes by mapped users (it currently supports two). If you add more teammates but don’t expand the “Route by Notion Assignee” logic, some tasks will never get a DM.
Common Questions
About 30 minutes if your Notion database and Slack workspace are ready.
Yes. There’s no coding, but you will need to connect Notion and Slack and confirm how assignees map to Slack users.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Notion and Slack being free/paid depending on your team plan.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
You can change the Notion database in the “Retrieve Tasks from Notion” node, then tweak filtering rules in “Exclude Completed Tasks” to match your statuses. If you have more than two assignees, expand the routing in “Route by Notion Assignee” (or replace it with a more general mapping approach based on email). Many teams also customize the DM text so it includes priority, a direct Notion link, or a “due today” callout.
Most of the time it’s an expired OAuth connection or missing Slack scopes for reading users and posting messages. Reconnect Slack in n8n, then confirm the workflow is allowed to fetch the user directory. If user matching is off, check display names versus full names and adjust the “Map Slack User Names” values so they match what Slack returns.
For most small teams, it’s plenty.
Often, yes, if you care about routing logic and keeping costs predictable. This workflow relies on pulling a directory of Slack users, filtering tasks, and routing by assignee, and n8n handles that kind of branching without turning it into a giant pile of paid “tasks.” Self-hosting is also a big deal if you want unlimited runs. Zapier or Make can be simpler for very basic two-step reminders, but matching people reliably (especially at scale) tends to get fiddly. Talk to an automation expert if you want a quick recommendation based on your team.
Once this is running, your mornings get quieter. The workflow handles the repetitive follow-up so your team can start work instead of starting a thread.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
