Database automations

Notion’s database automations turn routine project-management chores—status updates, reassignment, cross-database edits, and Slack pings—into rules that run automatically whenever a database page changes. The core idea is simple: each automation pairs a trigger (a specific change to a page, like a status edit) with one or more actions (what should happen next), letting teams keep work moving without manually chasing updates.

Automations are built around two parts. A trigger fires when a page is added or when a property on a page is edited—most commonly, when a status property changes to a particular value. After that trigger occurs, the automation can perform actions such as sending a Slack notification, updating a page property, adding a page to another database, editing pages in a related database, or combining multiple actions in sequence. Notion also lets automations target either every page in a database or only pages that match a saved filtered view; importantly, changing the filters in that saved view changes which pages the automation affects.

The transcript walks through a “QA flow” example using a tasks database. The automation is configured to watch for the status property changing to “ready for QA.” Once that condition is met, the automation automatically sets the assignee property to Santiago (the QA engineer) by selecting Santiago’s name from the assignee property lookup. The same behavior applies not only when someone edits an existing page’s status, but also when a new page is added and immediately marked “ready for QA.”

A second example shows how to coordinate kickoff work across teams. A “project kickoff” automation triggers when a project status changes to “up next.” It then creates a new page in a meeting notes database, naming the page “project kickoff” and setting the meeting type accordingly. A second action sends a Slack notification to the product channel to alert others that the project is being tackled.

Two operational details matter for teams rolling this out. First, Slack actions inside automations can only be edited by the person who created the notification, while automations tied to page status can be created, edited, deleted, disabled, and enabled by anyone with full access to the relevant database. Second, automations can be paused and resumed by toggling them off and back on, keeping the workflow controllable without deleting it.

Overall, database automations are positioned as a way to reduce missed handoffs and eliminate repetitive status chasing—setting up once, then letting Notion handle the follow-through whenever the right database changes occur. Access depends on plan type, and users can check availability via the lightning bolt icon in the database interface.