Skip to content
Tutorials Center
My learning

Topics

Lesson 22 of 36 ยท Templates and Automations

Automation Patterns and Limits

Practical Notion automation patterns for task handoffs, approvals and reminders, plus what automations cannot do and when to use the API or other tools.

You know the pieces: templates, buttons, recurrence, triggers and actions. This lesson puts them together into patterns you can reuse, then looks honestly at what Notion's built-in automation does not do, so you know when to reach for something else.

Notion cannot run on this site. The recipes are described as menu steps, and the JavaScript is a labelled stand-in that checks the thinking behind each recipe.

Pattern 1: stamp and notify

Goal: when a task finishes, record when, and tell the person who asked for it.

  • Trigger: Status edited to Done.
  • Actions: set Completed on to the current date; send a notification to the Requester (a Person property).

Why it works: the Status property is a reliable signal and the date is set once, by the system, not by hand.

Pattern 2: handoff to another database

Goal: a signed-off design becomes an engineering task.

  • Trigger: Stage edited to Approved in the Designs database.
  • Action: Add page to the Engineering database with a title copied from the design and a relation back to it.

Keep the relation so you can always find the source. Without it, the new task floats free.

Pattern 3: scheduled review

Goal: every Friday, collect last week's open items.

  • Trigger: recurring, Friday 15:00.
  • Actions: add a page from a "Weekly review" template, or send a notification pointing at a view that is filtered to Status is not Done.

Pair this with a database view that does the filtering. Automations are good at starting work; views are good at showing it.

Pattern 4: approval gate

Goal: nothing is published until a reviewer approves.

  • Property: Review (Select: Pending, Approved, Changes needed).
  • Trigger: Review edited to Changes needed.
  • Actions: set Status back to Draft and notify the author.

Publishing is then a view or button that only appears for rows where Review is Approved.

Stand-in: simulate a pipeline

This JavaScript is not Notion. It runs a list of rules over a sequence of edits and prints what each did, so you can reason about order and side effects before building the real thing.

JS Stand-in: approval gate rules

Press Run (or Ctrl + Enter) to see the console output here.

No output.

What built-in automations cannot do

Be realistic about the limits. These depend on your plan and on the current product, so verify in your workspace:

  • No complex logic. There is no full "if this and that, else..." programming. You get conditions and actions, not loops or variables across pages.
  • Mostly one database at a time. Rules react to changes in their own database. Reaching into another is limited to the actions provided.
  • Limited bulk work. Editing thousands of pages, or reshaping data heavily, is better done with an import, an API script, or a connector.
  • Rate and plan limits. Some actions (webhooks, Slack) need paid plans, and heavy workflows can hit throttling.
  • No time travel. An automation reacts to a change from now on. It does not rewrite history unless you run a one-off update.

When you need more, there are two routes:

  1. Notion's API with your own script. You get full programming power and control. The next chapter (Notion API Basics) introduces it.
  2. Connector tools such as Zapier, Make or n8n that watch your database and run multi-step flows across many apps.

Stand-in: a safe estimator for bulk edits

Before running an automation across a big database, estimate how much work it will create. This stand-in counts matching rows so you can sanity-check the size.

JS Stand-in: how many pages will a rule touch

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Testing checklist

  • Try the rule on a duplicate of the database first.
  • Change one row, watch the result, then change ten.
  • Read the automation's name and description out loud: could a teammate understand it?
  • Note who owns it. Rules owned by a person who leaves can break when their access is removed.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. Which pattern sends a task onward to another database?

    A handoff creates a new page in a second database, ideally with a relation back to the source.
  2. 2. When is the API or a connector tool a better choice than built-in automations?

    Complex logic, cross-app flows and bulk jobs go beyond the built-in rules.
  3. 3. Why test automations on a duplicate database first?

    A mistaken rule can change a lot of data, so test where mistakes are cheap.

Summary

  • Reusable patterns: stamp and notify, handoff, scheduled review, approval gate.
  • Triggers on a Status or select property are the most reliable.
  • Built-in rules are not a programming language; plan limits may also apply.
  • For heavier needs, use the API or a connector, and test on a copy first.

Next: Workspaces, Members and Roles