Notion Recurring Task Generator

Overview

This flow automates recurring-task creation in Notion. On a daily schedule it reads a recurrence-template database (daily / weekly / monthly definitions with owner and cadence rules), evaluates which templates are due today, generates a task instance for each into a Notion tasks database with the right owner and due date, and posts a digest of the day's generated tasks to a Teams channel and an Outlook email recipient.

Why it matters: Notion databases do not natively generate recurring tasks. This fills the gap, so routine work (reports, reviews, maintenance) appears automatically on the correct cadence instead of relying on memory.

Ships Off (Stopped).

Use Case

An Operations or Project Management team tracks work in Notion and has recurring obligations (weekly status reports, monthly access reviews, daily standup prep). They want those tasks created automatically on the right cadence with the right owner, plus a daily summary of what was generated.

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.

Cadence rules

The due-today condition supports Daily, Weekly (DayOfWeek match), and Monthly (DayOfMonth match). Add patterns like bi-weekly or quarterly by extending the or expression and adding template properties.

Task properties

Edit the Properties JSON in Create Task Instance to match your tasks database column names exactly.

Owner as a Notion person

This build writes Owner as rich_text. To assign a real Notion user, change the property to people and supply Notion user IDs.

Dedup

Query the tasks DB by name + due date before creating, and gate creation on an empty result, to skip a template whose instance already exists for today.

Notification channels

The Teams post and Outlook email are independent; remove either if only one channel is needed.

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.

formatDateTime(utcNow(), 'yyyy-MM-dd')

dayOfWeek(utcNow())

int(formatDateTime(utcNow(), 'dd'))

or(equals(Frequency,'Daily'), and(equals(Frequency,'Weekly'), equals(DayOfWeek, Current_DayOfWeek)), and(equals(Frequency,'Monthly'), equals(DayOfMonth, Current_DayOfMonth)))