Automate daily standups using Slack, Notion, and Redis — Flujo de trabajo n8n

Alta complejidad Programado45 nodos🏷️ Project Management👁 14 vistaspor BytezTech

Descripción general

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

Nodos utilizados

RedisSlackNotionCode

Vista previa del flujo de trabajo

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

Cómo funciona

  1. 1

    Disparador

    El flujo de trabajo comienza con un disparador programado, ejecutándose según un horario definido.

  2. 2

    Procesamiento

    Los datos fluyen a través de 45 nodos, connecting code, if, merge.

  3. 3

    Salida

    El flujo de trabajo completa su automatización y entrega el resultado al destino configurado.

Detalles de nodos (45)

RE

Redis

redis

#1
SL

Slack

slack

#2
NO

Notion

notion

#3
CO

Code

code

#4

Cómo importar este flujo de trabajo

  1. 1Haz clic en el botón Descargar JSON a la derecha para guardar el archivo del flujo de trabajo.
  2. 2Abre tu instancia de n8n. Ve a Flujos de trabajo → Nuevo → Importar desde archivo.
  3. 3Selecciona el archivo automate-daily-standups-using-slack-notion-and-redis descargado y haz clic en Importar.
  4. 4Configura las credenciales para cada nodo de servicio (claves API, OAuth, etc.).
  5. 5Haz clic en Probar flujo de trabajo para verificar que todo funcione, luego actívalo.

O pega directamente en n8n → Importar desde JSON:

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

Integraciones

codeifmergenotionredisscheduletriggerslacksplitinbatches

Obtener este flujo de trabajo

Descarga e importa con un solo clic

Descargar JSONVer en n8n.io
Nodos45
Complejidadhigh
Disparadorscheduled
Vistas14

Creado por

BytezTech

BytezTech

@chintan

Etiquetas

codeifmergenotionredisscheduletriggerslacksplitinbatches

¿Nuevo en n8n?

n8n es una herramienta de automatización de flujos de trabajo gratuita y de código abierto. Alójala tú mismo o usa la versión en la nube.

Obtener n8n gratis →