Get AI summaries of any video or article — Sign up free
Create Recurring Tasks in Notion 10x Faster (100% Free Automation) thumbnail

Create Recurring Tasks in Notion 10x Faster (100% Free Automation)

Red Gregory·
5 min read

Based on Red Gregory's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Notion’s native app can simulate recurring behavior with formulas, but it doesn’t automatically create new calendar entries for each occurrence.

Briefing

Notion’s native app still lacks a true “recurring tasks” feature that can automatically generate new calendar entries on a schedule. A practical workaround uses Bardeen—an automation tool—to create recurring task entries inside Notion, either as lightweight “single-event” tasks that check whether today matches a frequency, or as fully automated “multi-entry” tasks that spawn fresh database rows on specific dates.

For users who mainly want recurring behavior without calendar-populated duplicates, the transcript outlines a native approach called “single event recurring tasks.” It uses a multi-select property to store multiple frequency options and a formula that evaluates whether the current day matches the selected frequency. A separate tab then collects only the checkboxes marked true. This method works well for minimal setups, but it doesn’t solve the community’s bigger pain point: generating entirely new entries on a calendar view.

To achieve calendar-style recurrence—such as creating a new “pay rent” entry every month on the 15th—the workflow shifts to Bardeen. The setup begins by building a Notion task manager database using templates and properties like status columns (e.g., to do, ideas, done), a priority select (e.g., P1), and a due date date property. After installing the Bardeen Chrome extension and connecting Notion pages, the automation is configured through an “autobook.”

The first example creates “Sunday recurring tasks.” A scheduled trigger runs every Sunday at midnight, and two actions add new rows to the Notion “task list” database: one for “write newsletter” and another for “weekly review.” Each action maps fields from the trigger into Notion properties—setting priority (e.g., P1), status (e.g., priority inbox), due date (from the scheduled date), and the task name. Once enabled, the tasks appear in both the task list and any calendar view tied to the database.

The transcript then demonstrates the same pattern for finances. A “cash flow” database is created with a type select (income vs outgoing), an amount field, and a formula that converts outgoing values into negative numbers using unary minus (to avoid compatibility issues with negative inputs). A monthly autobook runs on the 15th, adding a “pay rent” entry to the cash flow database with the amount set and the date populated from the trigger. A grouped view sums totals by month, updating automatically as new entries arrive.

Bardeen’s appeal in this workflow is its “completely free” automation model with no monthly task cap, contrasted with other tools that restrict usage. The tradeoff is a narrower integration catalog, though the transcript highlights common options like Gmail, Google Calendar, Notion, and Twitter, plus a Bardeen automation hub for additional starting points.

Cornell Notes

Notion lacks native recurring tasks that automatically create new calendar entries on a schedule. The workaround uses Bardeen to generate fresh rows in Notion databases at set times. One approach uses Notion-only “single event recurring tasks” with formulas and multi-select frequency checks, but it won’t create new calendar entries. The stronger method uses Bardeen “autobooks” with scheduled triggers (e.g., every Sunday at midnight, or the 15th of each month) and actions that add database entries with mapped fields like due date, priority/status, and task name. The same pattern supports finance tracking by inserting monthly rent payments into a cash flow database and using a formula to represent outgoing amounts as negatives.

Why does the “single event recurring tasks” method fall short for calendar-based recurrence?

It relies on evaluating whether “today” matches a chosen frequency and then filtering/collecting items (e.g., checkboxes marked true). That creates recurring visibility, but it doesn’t generate a brand-new database entry for each occurrence. As a result, a calendar view can’t show newly created rows on dates like the 15th of every month—only whatever items are already present and currently match the formula.

How does Bardeen create true recurring tasks that appear as new calendar entries?

Bardeen uses an “autobook” with a scheduled trigger (for example, repeat weekly every Sunday at midnight). When the trigger fires, Bardeen runs actions like “add Notion page to database,” which inserts new rows into a Notion database (e.g., the “task list”). Field mapping sets properties such as due date (from the trigger date), priority (e.g., P1), status (e.g., priority inbox), and the task name (e.g., “write newsletter”).

What field-mapping details matter when adding tasks to the Notion task list?

The transcript emphasizes mapping custom properties created in Notion—especially priority, due date, and status. For each scheduled action, the due date is pulled from the trigger action’s date value (“entire value”), status is set to a specific column like “priority inbox,” and the name property is set to the task label (e.g., “weekly review”). This ensures the new rows show up correctly in both list and calendar views.

How does the cash flow example handle outgoing amounts as negative numbers?

Because Bardeen may have negative-number compatibility issues, the cash flow database includes a formula that converts outgoing values into negatives. The formula uses a conditional: if type equals “outgoing,” it applies unary minus to the amount; otherwise it returns the amount as-is. That way, “pay rent” entries can be stored with a positive amount input while still displaying totals correctly as deductions.

How can recurring finance entries be summarized automatically by month?

After the monthly autobook inserts new cash flow rows on the 15th, a grouped view can aggregate totals. The transcript suggests grouping by date by month, hiding empty groups, and then using a rollup/sum setting on the total column (e.g., sum of total). As new entries appear, the monthly totals update without manual recalculation.

Review Questions

  1. What specific limitation of the native “single event” formula approach prevents calendar-style recurring entries from being created?
  2. In the Bardeen workflow, which properties must be mapped from the scheduled trigger to ensure tasks land in the right Notion fields (due date, priority/status, and name)?
  3. Why does the cash flow setup use a formula to convert outgoing amounts to negatives, and what would break if negative numbers were entered directly?

Key Points

  1. 1

    Notion’s native app can simulate recurring behavior with formulas, but it doesn’t automatically create new calendar entries for each occurrence.

  2. 2

    Bardeen enables true recurring tasks by scheduling triggers that insert new rows into Notion databases.

  3. 3

    A weekly example can add multiple tasks per trigger (e.g., “write newsletter” and “weekly review”) by running multiple “add to database” actions.

  4. 4

    Calendar views work because the automation creates new database entries with mapped due dates and statuses.

  5. 5

    For finance tracking, a cash flow database can represent outgoing expenses as negative values using a conditional formula.

  6. 6

    Bardeen is positioned as fully free with no monthly task cap, though integration options may be more limited than paid alternatives.

Highlights

The native “single event recurring tasks” approach can filter tasks based on whether today matches a frequency, but it won’t generate new calendar rows.
Bardeen’s scheduled “autobooks” can create fresh Notion database entries on specific dates (like every Sunday at midnight) so calendar views populate automatically.
Outgoing cash flow values are handled with a formula that applies unary minus when type equals “outgoing,” avoiding negative-number compatibility issues.
A monthly rent automation inserts a new “pay rent” entry on the 15th, and a grouped monthly view can sum totals as new entries arrive.

Topics

Mentioned