The Easiest Way to Create Recurring Tasks in Notion (2024)
Based on Thomas Frank Explains's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Use Notion’s repeating templates only if “due date = today” behavior is acceptable; it limits calendar lookahead because future tasks aren’t reliably visible before creation.
Briefing
Recurring tasks in Notion are easy to set up—until you need real scheduling, planning, and “check off and roll forward” behavior. The core fix is to move beyond Notion’s built-in repeating templates (which can only use dynamic due dates like “today”) and instead use a recurring-task system that stores a “next due” date and advances tasks automatically. That shift matters because it enables accurate lookahead planning, supports complex recurrence rules, and makes recurring work behave like a traditional task manager.
At the simplest level, Notion’s native database template feature can create repeating pages on a schedule. The workflow is straightforward: build a task template with default properties (like status = “Not started” and due date = “today”), then enable a repeat setting (daily, weekly, monthly, yearly). For example, a “clear inbox” template can be set to repeat weekly on selected weekdays, creating new task pages automatically. The catch is significant: the due date can only be set using dynamic date options such as “now” or “today.” Because the task page is created only when the schedule fires, there’s no reliable way to preview future occurrences ahead of time. If that limitation is acceptable, the native approach works; if not, a more robust system is needed.
Level two introduces a custom recurring-task setup used in “Ultimate Brain,” built around two key ideas: a stored recurrence definition and a “next due” field. Instead of relying on a repeating template to create new pages, each recurring task carries recurrence rules (recur interval plus recur unit and day selections). When it’s time to complete a task, the user moves the task’s due date to the current “next due” date—instantly rolling it forward so the task shows the next occurrence (skipping weekends when configured). This design also unlocks richer recurrence options than Notion’s repeating templates: beyond days/weeks/months, it supports patterns like “first weekday of the month,” “last weekday of the month,” “last day,” and yearly recurrences. The system relies on large Notion formulas (credited to Martin on the team) that compute the next occurrence based on the recurrence settings.
Level three automates the manual “move due date forward” step using Pipe Dream. A scheduled trigger runs daily at 11:57 p.m. in the user’s time zone, finds recurring tasks marked as done (whether via checkbox or status properties), then resets them back to Todo and updates the due date to the computed next due date. The setup also supports different property types—Notion status properties can be mapped to “Todo” and “done” options, not just checkboxes. After processing, the workflow can generate a report and send it to Slack, including links to the tasks that were advanced. The result is a recurring-task loop that behaves like a conventional app: complete tasks, roll them forward, and receive daily visibility—without manual maintenance.
Cornell Notes
Notion’s built-in repeating templates can create recurring task pages on a schedule, but they rely on dynamic due dates like “today,” which prevents reliable lookahead planning. A stronger approach stores recurrence rules on each task and computes a “next due” date, then advances tasks by moving the due date to the next occurrence. This enables complex recurrence patterns (e.g., first/last weekday of the month, last day, yearly) and supports skipping specific days like weekends. The final step automates the “advance” action with Pipe Dream: a daily scheduled workflow finds tasks marked done, resets them to Todo, updates due dates to the next due value, and can post a daily Slack report with links to processed tasks.
Why do Notion’s repeating templates struggle for recurring tasks that need planning ahead?
How does the Level 2 system make recurring tasks behave more like a traditional task manager?
What recurrence rules become possible in Level 2 that are not available in Level 1’s repeating templates?
What does the Level 3 automation do, and how does it decide which tasks to process?
How can the workflow send a daily report to Slack with links to the tasks processed?
Review Questions
- What limitation of dynamic due dates (“today”/“now”) makes Notion repeating templates less suitable for lookahead planning?
- In the Level 2 approach, what field is used to roll a completed recurring task forward, and what user action triggers the roll-forward?
- How does the Pipe Dream workflow determine which recurring tasks are “completed” and ready to be advanced?
Key Points
- 1
Use Notion’s repeating templates only if “due date = today” behavior is acceptable; it limits calendar lookahead because future tasks aren’t reliably visible before creation.
- 2
For robust recurring tasks, store recurrence rules on each task and compute a “next due” date so tasks can be planned in advance.
- 3
Advance a recurring task by moving its due date to the current “next due” value; this recalculates the next occurrence automatically.
- 4
Level 2 supports advanced recurrence units such as first/last weekday of the month, last day, and yearly patterns, plus day-of-week selections for day-based recurrences.
- 5
Automate the roll-forward step with Pipe Dream by running a daily scheduled trigger that finds tasks marked done and resets them to Todo with updated due dates.
- 6
Map both checkbox-based completion and status-property completion in the automation so different task schemas still work.
- 7
Extend the workflow by posting a daily Slack report that includes links to the tasks that were processed and their next due dates.