Notion Sprint Standup Digest

Overview

This flow generates a daily sprint standup digest sourced from a Notion sprint/tasks database and posts it to a Microsoft Teams channel (with an optional email copy). Each morning at 8:45 it queries the database, sorts tasks into four buckets - completed since yesterday, in progress, blocked, and due today - and posts a formatted HTML digest. Blocked and due-today items are listed with their owners so the standup can focus on unblocking, not status-reading.

Why it matters: standup prep is repetitive and inconsistent. An automatic Notion-sourced digest gives the team the same shared picture every day with zero manual effort.

Ships Off (demo).

Use Case

A delivery team running sprints in Notion wants a consistent morning standup summary in Teams so the meeting focuses on blockers, not status reading. Turning it on requires only authorizing the three connections and setting four environment-variable values.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Different column names

The flow reads Notion property names from Init variables (title/status/owner/due). If your board uses Assignee or Deadline, change those values.

Different status labels

Change the Done / In Progress / Blocked init values to match your board; the status read coalesces Status and Select property types.

Per-assignee threads

DM each member their own items by looping the filtered arrays and posting to a 1:1 chat.

Weekend skip

Add a Condition after the trigger that exits on Saturday/Sunday.

True @-mentions

Build a mentions array and embed <at> tags to tag owners as real Teams mentions.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

coalesce(item()?['properties']?[variables('varStatusProperty')]?['status']?['name'], item()?['properties']?[variables('varStatusProperty')]?['select']?['name'], '')

greaterOrEquals(item()?['last_edited_time'], variables('varYesterdayStart'))

equals(formatDateTime(item()?['properties']?[variables('varDueProperty')]?['date']?['start'],'yyyy-MM-dd'), variables('varToday'))

coalesce(items('Apply_to_each_Blocked')?['properties']?[variables('varOwnerProperty')]?['people']?[0]?['name'],'Unassigned')

length(body('Filter_Blocked'))