Skip to content
Tutorials Center
My learning

Topics

Lesson 21 of 36 ยท Templates and Automations

Automations - Triggers and Actions

Understand Notion database automations: triggers such as page added or property edited, actions such as edit property or send notification, and how to design them.

Buttons run when you click them. Database automations run on their own. You describe a rule such as "when Status changes to Done, set Completed on to today and notify the owner", and Notion applies it every time the condition is met, no matter who made the change.

Automations are available on paid plans and some options differ by plan, so check your workspace if a menu item is missing. The product cannot run on this site, so the real features are explained in words and the logic is demonstrated with JavaScript stand-ins, clearly labelled.

The shape of an automation

Every automation has the same three parts:

  1. Trigger: what starts the rule.
  2. Conditions (optional): extra filters that must be true.
  3. Actions: what Notion does, in order.

You create one from a database's ... menu, then Automations, then New automation (database settings in some versions).

Triggers

Trigger Fires when
Page added A new page appears in the database
Property edited A chosen property changes, optionally to a specific value
Recurring (schedule) A set time arrives, for example every Monday at 9:00

A "property edited" trigger can be narrowed: for example Status is set to Done. Without that narrowing it would fire on every edit.

Actions

Typical actions mirror buttons:

  • Edit property on the page that triggered the rule (set a date to now, set a Status, clear a field).
  • Add page to another database, for example create a follow-up task.
  • Send notification to a person, a person property or a group.
  • Send to Slack or send webhook to reach tools outside Notion.

Actions run top to bottom, and you can chain several in one rule.

Stand-in: a tiny rules engine

The code below is a plain JavaScript model, not Notion. It shows how a rule with a trigger, a condition and actions is evaluated against a change.

JS Stand-in: a Done rule

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

No output.

The second call prints an empty list: the title changed, not the status, so the rule did not fire.

Designing automations that behave

  • Narrow triggers. "Status is Done" instead of "any edit". Broad rules are noisy and slow to debug.
  • Make actions idempotent. Setting a property to a fixed value is safe to repeat. Creating a new page every time may duplicate work.
  • Avoid loops. If rule A edits a property that triggers rule B, which edits the property that triggers A, you have a loop. Keep chains short and test them on a copy.
  • Name rules clearly. "When Done: stamp date and notify" explains itself months later.
  • Prefer a property over text parsing. A Status or checkbox is a reliable trigger; searching a title for a word is not.

Stand-in: spotting a rule loop

A real workspace can contain rules that trigger each other. This stand-in walks a "who triggers whom" graph and reports cycles.

JS Stand-in: detect a loop

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

No output.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. Which are the three parts of a database automation?

    An automation starts from a trigger, may check conditions, then runs actions.
  2. 2. Why should you narrow a "property edited" trigger to a specific value?

    A broad trigger fires for every change; narrowing it keeps the rule precise and quiet.
  3. 3. Rule A edits a property that triggers rule B, and rule B edits the property that triggers A. What is this?

    Rules that trigger each other in a cycle can fire repeatedly. Keep chains short and test them.

Summary

  • An automation = trigger + optional conditions + ordered actions.
  • Triggers: page added, property edited (optionally to a value), or a schedule.
  • Actions: edit property, add page, notify, Slack or webhook.
  • Keep triggers narrow, actions safe to repeat, and avoid rule loops.

Next: Automation Patterns and Limits