Automate daily standups using Slack, Notion, and Redis β€” n8n Workflow

High complexity⏰ Scheduled45 nodes🏷️ Project ManagementπŸ‘ 14 viewsby BytezTech

Overview

Run automated daily standups using Slack, Notion, and Redis

πŸ“Œ Overview

This workflow fully automates your team's daily standup process using Slack for communication, Notion for structured data storage, and Redis for real-time session management.

It automatically sends standup questions to active team members, collects and stores their responses, manages conversation sessions, and generates structured summary reports for managers.

Morning and evening standups run on schedule without manual in

Nodes used

RedisSlackNotionCode

Workflow Preview

Automated daily standup system with Slack, No
How it works
This workflow automates daily standups for your team ac
πŸŒ™ Evening Standup Summary
How it works
1. Triggers Mon–Sat at 6:30 PM IST
2. Fetches active members from `Team_Members` Notion DB
3. Fetches today's evening standups from `Daily_Standup
⏰ Trigger
Fires Mon–Sat at 6:30 PM IST (`30 18 * * 1-6`). Kicks o
πŸ“‹ Fetch Data
Fetches active members (`Team_Members`) and today's res
πŸ”€ Merge & Build
Merges both datasets, calculates response rate, missing
πŸ“€ Send to Slack
Posts the formatted evening summary to the admin Slack
πŸŒ… Morning Standup Summary
How it works
1. Triggers Mon–Sat at 10:10 AM IST
2. Fetches active members from `Team_Members` Notion DB
3. Fetches today's responded standups from `Daily_Stand
⏰ Trigger
Fires Mon–Sat at 10:10 AM IST (`10 10 * * 1-6`). Kicks
πŸ“‹ Fetch Data
Fetches active members (`Team_Members`) and today's res
πŸ”€ Merge & Build
Merges both datasets. Code node normalizes fields, calc
πŸ“€ Send to Slack
Posts the formatted morning standup summary to the admi
πŸŒ… Morning Standup Initiator
How it works
1. Triggers Mon–Sat at 9:40 AM IST
2. Fetches active members from `Team_Members` Notion DB
3. Loops through each developer one at a time
4. Validates mem
πŸ“‹ Fetch & Gate
Fetches active members from `Team_Members` Notion DB. I
πŸ” Developer Loop
`splitInBatches` iterates one member at a time. All pat
βœ… Validate Member
Code node normalizes Notion fields and checks required
πŸ”΄ Redis Session Check
GETs existing session key `morning:standup:session:{sla
πŸ“ Create Session
Creates a `Conversation_State` record in Notion (questi
πŸ”΄ Save & Send
IF `can_write_redis` is true: SETs session in Redis (86
⏰ Trigger
Fires Mon–Sat at 9:40 AM IST (`0 40 9 * * 1-6`). Kicks
πŸŒ™ Evening Standup Initiator
How it works
Fires Mon–Sat at 6 PM IST. Fetches all active developer
⏰ Trigger, Fetch & Gate
Schedule fires Mon–Sat 6 PM IST. Fetches active members
πŸ” Developer Loop & Validation
Iterates through each member one at a time. Validates r
πŸ”΄ Redis Session Check
GETs `standup:evening:{slack_user_id}`. If a session ex
πŸ“ Session Creation & Storage
Creates a Notion record in `Conversation_State_Afternoo
πŸ’¬ Send, Log & Loop Back
Sends Question 1 of 3 via Slack DM (`chat:write`). Logs
Fetch Active Members
M
Merge Data
Fetch Evening Standups
⚑
E
Evening schedule trigger
Build evening summary me…
Send to Admin Channel Ev…
Send to Admin Channel
⚑
M
Morning schedule trigger
Fetch team members (morn…
Fetch today's morning st…
M
Merge morning data
Build morning summary me…
⚑
M
Morning standup initiato…
Get active team members
C
Check if members found
D
Developer loop
Extract and validate mem…
I
Is valid member
Check existing Redis ses…
Parse session state
N
Needs new session
Create Notion session
Prepare session data
S
Session data ready
Save session to Redis
Send standup message
Update Slack channel ID …
C
Continue to next (morning)
⚑
E
Evening standup initiato…
Get active team members …
C
Check developers found
No developers found
P
Process each developer
Validate and prepare mem…
C
Check if valid member (e…
Check evening Redis sess…
Check evening session st…
S
Should proceed with even…
Create evening Notion se…
Build evening session data
E
Evening session ready
Store evening session in…
Send evening standup mes…
Log final result
C
Continue to next (evening)
45 nodes51 edges

How it Works

  1. 1

    Trigger

    The workflow starts with a scheduled trigger, running on a defined schedule.

  2. 2

    Process

    Data flows through 45 nodes, connecting code, if, merge.

  3. 3

    Output

    The workflow completes its automation and delivers the result to the configured destination.

Node Details (45)

RE

Redis

redis

#1
SL

Slack

slack

#2
NO

Notion

notion

#3
CO

Code

code

#4

How to Import This Workflow

  1. 1Click Download JSON button on the right to save the workflow file.
  2. 2Open your n8n instance. Go to Workflows β†’ New β†’ Import from file.
  3. 3Select the downloaded automate-daily-standups-using-slack-notion-and-redis file and click Import.
  4. 4Set up credentials for each service node (API keys, OAuth, etc.).
  5. 5Click Test Workflow to verify everything works, then activate it.

Or paste directly in n8n β†’ Import from JSON:

{ "name": "Automate daily standups using Slack, Notion, and Redis", "nodes": [...], ...}

Integrations

codeifmergenotionredisscheduletriggerslacksplitinbatches

Get This Workflow

Download and import in one click

Download JSONView on n8n.io
Nodes45
Complexityhigh
Triggerscheduled
Views14
CategoryProject Management

Created by

BytezTech

BytezTech

@chintan

Tags

codeifmergenotionredisscheduletriggerslacksplitinbatches
⚑

New to n8n?

n8n is a free, open-source workflow automation tool. Self-host it or use the cloud version.

Get n8n Free β†’