Notion Automations: The Complete 2026 Guide to Database Automations

Notion database automations are the "if this, then that" layer baked into your databases. Mark a task as done, auto-set the completed date. Move a deal to "Proposal", notify Slack. Since their launch, Notion has kept adding to them: automations can now run on a schedule, send emails from your Gmail, and fire webhooks at other apps.

This guide covers every trigger and action available in 2026, which plans include them, how to build your first one, 15 recipes from four template patterns you can lift, and the places Notion's built-in automations still fall short (with the workarounds that close the gap). For automations that need data Notion can't provide on its own (formulas, stock prices, live data from external systems, cross-database aggregation), Sync2Sheets gives you real-time 2-way sync to Google Sheets, with a per-column direction picker.

The basics

Database automations are "if… then" rules attached to a database. You pick a trigger (something happens in Notion, like a page being added or a property being changed) and an action (what Notion does in response, like sending a notification or editing another property).

As a simple example, imagine you have a Notion workspace with a few team members and a project manager. You want the project manager to receive a notification whenever someone sets the status of a project to "Ready for QA".

Database automations make this easy, as we'll see in the next section. All you have to do is define a trigger (the change in project status) and an action (in this case, sending a notification to the project manager).

How Do Notion Automations Work?

Each Notion automation consists of two main parts: the trigger and the action. Let's explore each in detail before examining how they work together.

Notion Automation Triggers

The trigger is the thing (or things) that need to happen for an automation to occur. Example triggers include:

• Assigning a task to a person
• Editing an entry in a CRM
• Creating a new task list

All triggers fall into three general categories:

1. Page added
2. Property edited
3. Every… (a recurring schedule)

The first category is self-explanatory: your automation will trigger when a page is added to a specified database. For example, you could set up an automation that notifies you whenever someone creates a new task list in a project.

The second category is more complicated. Your automation will trigger whenever a specified property (or properties) is edited within your database. For instance, you could automatically assign a team member to a new project when they mark an existing one as completed.

In most cases, the "Property edited" trigger is a binary condition. That is, the automation will occur if any edits to the property take place. But for the following properties, you can specify what kind of edit will trigger the automation:

• Name (of the property)
• Person
• Number
• Text
• Select
• Relation

This is useful because it lets you create automations based on specific values. For instance, if you have a database of customer emails, you could make a trigger to automatically set the Company Name to "Notion" for emails containing the text "@notion.so".

The third category, "Every…", is the newest and the one most guides still miss: a recurring trigger that fires on a schedule you define. Every day at 9 am, every Sunday at 18:00, every first of the month. You pick the frequency, the time, the timezone, and optional start and end dates. This is how you get a fresh standup page in your tasks database each morning, or a weekly review page that appears every Sunday evening, without touching anything.

Two things to know about scheduled triggers. They can't be combined with other trigger types in the same automation (a rule fires on a schedule or on an event, not both). And for anything event-based, the old rule still holds: "Page added" and "Property edited" rely on something changing inside the database, so you can't trigger off a condition like "the current time is past the due date". For that, schedule a daily automation that edits pages matching a filter.

Finally, note that you can set multiple event triggers and decide if all (or just some) must be true for your automation to occur. For example, you could automatically notify someone in Slack when a task becomes overdue AND a team member leaves a comment on it. One quirk worth knowing: when several "is edited" triggers must all occur, Notion expects them to happen within about 3 seconds of each other.

Notion Automation Actions

Now that we understand Notion automation triggers, let's turn our attention to actions.

The action is the thing (or things) you want to occur based on the trigger(s) you set. Notion automations currently offer eight action types:

1. Edit property
2. Add page to
3. Edit pages in
4. Send notification to
5. Send mail to
6. Send Slack notification to
7. Send webhook
8. Define variables

"Edit property" lets you edit properties of the current database. For multi-select, people, and relation properties you can add or remove individual values instead of overwriting the whole thing.

"Add page to", meanwhile, adds a page to the database of your choice. You can also specify what properties the page should have. This action is great for automatically creating new tasks or projects with just the click of a button.

"Edit pages in" edits pages and properties in a database you select. You can also specify a filter, such as text that the page name must contain. For instance, you could update the "Person" property for all pages whose names contain the text "Google Sheets".

"Send notification to" sends a notification within Notion to the people you specify. You can notify up to 20 people in your workspace at once, or people linked in a person property, and customize the message that accompanies the notification.

"Send mail to" sends an email from your own Gmail account, including to addresses outside your workspace. You connect Gmail once, and only the person who linked the account can edit that automation. Delivery can take a couple of minutes, so don't use it for anything time-critical.

"Send Slack notification to" posts a message to a Slack channel you pick, and unlike the early version of this action, the message is now fully customizable.

"Send webhook" fires an HTTP POST request at a URL you choose, with custom headers if you need them. This is the door out of Notion: point it at Zapier, Make, n8n, or your own endpoint and let anything downstream react to changes in your database. It sends page properties (not page contents), and you can stack up to five webhook actions in one automation.

"Define variables" creates named values from mentions and formulas that your other actions can reference. It's what makes the difference between a static message and one that says which page changed, who changed it, and what the new value is.

As with triggers, you can specify multiple actions to occur at once. For example, clicking a button could trigger both the creation of a new page AND an edit to an existing page.

Which Notion Plans Include Database Automations?

The short version: automations are a paid feature, with one carve-out.

• Paid plans (Plus, Business, Enterprise) can create, edit, and delete every automation type, including scheduled triggers, email, and webhooks.
• Free plan users can create automations that send Slack notifications, and they can use templates that ship with automations built in. What they can't do is edit those rules or create any other automation type.
• Notion Workers (more on those below) need the Business plan or above.

Two ownership quirks apply on any plan. Slack automations can only be edited by whoever created them, and email automations can only be edited by the person whose Gmail account is connected. If a teammate leaves, plan to rebuild those.

If you're comparing tiers anyway, our Notion pricing guide covers what each plan actually gets you beyond automations.

What's New in Notion Automations (2026)

Notion shipped meaningful automation upgrades over the past year, and most older guides haven't caught up:

• Webhook actions in automations (January 2026). Buttons and database automations can now send HTTP POST requests to any URL. Before this, getting data out of Notion on a trigger meant polling the API or paying for a middleman.
• Webhook support in the REST API (March 2026). The API side expanded too, so external tools can subscribe to workspace events instead of polling for changes.
• Notion Workers (announced at Notion Dev Day 2026). Workers are small pieces of code that run on Notion's servers and go beyond what point-and-click automations can do: searching across databases, calling external APIs, running real logic. They deploy through the Notion CLI, require the Business plan, and can run as agent tools, webhook handlers, or scheduled syncs that pull external data into a dedicated database on an interval.

In practice this means plain database automations now handle scheduling and outbound webhooks on their own, and when you genuinely need code, Notion has a first-party answer before you reach for a third-party platform.

How to Create Your First Notion Automation

Now that you understand the basics of triggers and actions, let's create our first automation!

First, choose the database you want to work with.

Next, click the "lightning" icon at the top of the database, then select "New automation".

Now, choose a name for your automation. From there, define your triggers and actions.

Finally, click "Create". You can also edit, pause, or delete the action at any time.

4 Ways to Use Notion Automations

We've talked a lot about how Notion automations work in theory, so now let's examine ways you can use them in your work.

Here are four Notion templates that showcase the power of database automations:

1. Reading List

Building a reading list (or studying an existing template) is a great way to get the hang of Notion automations.

This reading list template from the folks at Notion uses automations in a few ways, as the template notes discuss:

• When a book is marked as Complete → Set the Date finished property to the current date.
• When a book is marked as Started reading → Set the Date started property to the current date.
• When a book is marked as Started reading → Set the Current page to 0.
• When a new book is added to the reading list → Set the Rating property to Not yet rated

2. Project Management

Most project management overhead is clerical: changing statuses, notifying people, updating dates. Automations eat that work. Notion's Projects & Tasks template shows a few good patterns:

Here are a few ways the template uses automations:

• When a task's Due Date is edited, send an update to a specified Slack channel.
• When a task is tagged Video Production, replace the Assignee with the Video Lead person.
• When a new project is added, notify a specified Slack channel.

For more tips on using Notion for project management, check out this guide.

3. Job Applicant Tracker

Full-fledged applicant tracking systems are expensive and often overkill for smaller companies.

As an alternative, consider using this Job Applicant Tracker template, which leverages database automations in the following interesting ways:

• When an offer is made → Update Offer made date to the current date.
• When a new applicant is added → Update Stage to Lead.
• When a new engineering applicant is added → Set the eng team lead as the Interviewer.
• When applicant status is updated to Offer → Assign legal hiring POC as Legal POC.

4. Sales Pipeline

The goal of a CRM is to close more deals, not spend forever updating database entries. The Sales Pipeline template puts this idea into practice, using database automations to save you time:

• When a deal is marked as Closed → Set the Date closed property to the current date.
• When a deal is marked Lead → Set Account Owner to AE.
• When a deal is marked Proposal → Set Legal POC to a team member.
• When a deal is marked as Closed → Send a notification to the #sales-wins in Slack.

To explore more Notion CRM templates, read this next.

Notion Database Automations FAQ

To close out this guide, let's answer some common questions about Notion automations.

How much do Notion database automations cost?

To create and edit Notion database automations, you need a paid plan (Plus or higher).

The Free plan gets two exceptions: you can create automations that send Slack notifications, and you can use Notion templates that include automations. You just can't edit the rules inside them. The full breakdown is in the plans section above.

Do I need Notion database automations?

Not necessarily.

If you're using prebuilt templates or mostly use Notion for writing and note-taking, then it's probably overkill.

But if you're into building custom workflows or using Notion for project management, automations are a very useful feature.

Can actions triggered by automations trigger other automations?

No, they cannot. This is generally a good thing, as it protects you from creating automations that destroy data or are difficult to debug.

Can I use automations to sync data between Notion and Google Sheets?

Notion's built-in automations don't do this directly. But Sync2Sheets does it in real time, in both directions. Pick the sync direction per column: Notion to Sheets, Sheets to Notion, or Both ways. Sheets formulas can drive Notion properties; new Sheets rows can create Notion pages; cells in Sheets can update Notion blocks. See the complete 2-way sync guide for the full picture.

Notion Automation Limits to Know

Before you architect your whole workspace around automations, a few hard limits worth knowing up front:

• Automations can't trigger other automations. An "Edit pages in" action that changes a property will not fire the automation watching that property. Annoying when you want chains, but it also protects you from infinite loops.
• Scheduled triggers travel alone. An automation fires on a schedule or on events, never both.
• Restricted pages are skipped. Automations won't touch pages the automation creator can't access.
• Webhooks are POST-only and property-only. No other HTTP methods, no page contents in the payload, five webhook actions per automation.
• Email is slow-ish. Gmail sends can take up to 2 minutes to deliver.
• No native "move page" action. The common workaround for moving a page to another database is an "Add page to" action that recreates it in the target database, paired with a status change on the original. True moves became possible through the API in 2026, so a webhook action pointed at a small script (or a Notion Worker) can do it properly.

Where Notion automations fall short (and what to use instead)

Notion's built-in automations are great for in-Notion logic (update property A when B changes, notify Slack when a deal closes). They hit walls in a few specific places:

• External data. You can't trigger an automation off a stock price, an exchange rate, an API response, or a row appearing in another tool's database. Sheets can fetch any of those (=GOOGLEFINANCE, =IMPORTXML, connectors for HubSpot/Stripe/Salesforce), and Sync2Sheets can push the result into Notion via a Sheets-to-Notion column.
• Complex math. Notion's formula property is single-page-scoped with ~60 functions. Anything involving aggregation, pivots, regression, or weighted scoring lives in Sheets. Compute in Sheets, write back to Notion.
• Bulk creation. Notion has no native bulk-import workflow. Sync2Sheets' page creation feature turns new rows in Sheets into Notion pages, hundreds at a time.
• Cross-database logic. Notion automations are scoped to one database. Sheets can pull data from multiple Notion databases (via separate syncs), combine them with QUERY or VLOOKUP, and feed results back.
• Cells linked to Notion blocks. Want a Notion heading or callout to display a Sheets cell value? That's what block updates do.

These aren't replacements for Notion's automations. They're complements. Most teams use both: Notion automations for in-workspace logic, Sync2Sheets for anything that touches external data or needs spreadsheet-level computation.

The fastest way to learn database automations

Don't build automations from scratch. Copy a template that already uses them (the four above are a good start), poke at the rules, break them, rebuild them. You'll pick up the patterns faster than any guide can teach.

And when you hit Notion's automation limits, Sync2Sheets is the bridge to spreadsheet-level computation. Install the add-on for the 7-day free trial.