Notion automations turn your databases from passive storage into active workflows. Instead of manually updating statuses, assigning tasks, or pinging teammates, you set up a rule once and Notion handles it every time the trigger fires.

The feature has expanded significantly. As of 2026, Notion's native automation supports triggers based on property changes, new page creation, and recurring schedules, with actions that include editing properties, sending Slack messages, creating pages, and firing webhooks to external tools.

This guide covers how Notion automations work, how to build them, what you can and can't automate natively, and how to extend them when you hit the ceiling. Whether you're managing a project database or a personal task list, there's something here you can use today.

Key Takeaways

• Notion automations run on if-this-then-that logic: a trigger fires, one or more actions execute automatically

• Full database automations require a Plus plan at $10/seat/month billed annually; Free plans support buttons only

• Native automations handle property updates, page creation, and Slack notifications well; Zapier or Make cover the rest

What Are Notion Automations?

A Notion automation is a rule attached to a database. It has two parts: a trigger (something that happens in the database) and one or more actions (things Notion does in response). When the trigger fires, the actions run automatically without anyone clicking anything.

For example: when a task's Status property changes to "Done," Notion can automatically set a Completed Date, assign a follow-up task to the reviewer, and send a Slack message to the team channel. All three actions fire from one trigger.

Automations live at the database level, not the page level. You attach them to a specific database and they apply to every item in it (or only items in the current view, if you scope them that way). To understand how automations fit into a broader Notion setup, it helps to have a solid Notion dashboard in place first.

How to Create a Notion Automation

Open any database and click the lightning bolt icon (⚡) in the top right corner. Choose "New automation." From there:

• Give the automation a clear name you'll recognize later (this list gets long)

• Set the scope: the whole database, or just the current view

• Add a trigger from the available options

• Add one or more actions to run when the trigger fires

• Toggle the automation on and test it with a real database entry

Automations are off by default when created. Toggle them on before testing. You can pause any automation without deleting it by toggling it back off.

Types of Triggers in Notion

Notion currently offers three trigger types for database automations:

• Page added:fires when a new item is created in the database. Useful for onboarding flows, auto-assigning new tasks, or stamping a creation date.

• Property edited:fires when a specific property changes. This is the most useful trigger for status-based workflows. You can filter it to fire only when the property changes to a specific value (e.g., Status changes to "In Review").

• Recurring schedule:fires at a set interval (daily, weekly, monthly). Useful for creating recurring tasks, sending weekly review reminders, or archiving old entries on a schedule.

Types of Actions in Notion

Once a trigger fires, you can chain multiple actions together. The available actions are:

• Edit property:set any property to a specific value, including formulas, dates, assignees, and select options

• Add page to database:create a new page in the same or a different database with preset properties

• Send Slack notification:post a message to any Slack channel or DM (requires Slack connection in Notion settings)

• Send Notion notification:ping a specific person inside Notion

• Send webhook:fire a payload to an external URL, which lets you trigger Zapier, Make, or any custom endpoint

Actions run in order, top to bottom. You can reorder them by dragging. If one action fails (e.g., Slack is disconnected), Notion will log the error but still attempt subsequent actions.

Useful Notion Automation Examples

The best automations solve a specific friction point rather than automating for its own sake. Here are five that consistently save time across different use cases.

Auto-stamp completion dates. When a task's Status changes to "Done," set a Completed Date property to today. This builds a searchable history of when work was actually finished without anyone manually filling in a date field.

Route new submissions to the right person. When a new page is added to a form-connected database (like a bug report or content request), use "Edit property" to auto-assign it to the right person based on a category or department property. Pair this with a Slack notification so the assignee is alerted immediately.

Generate recurring standup pages. Use a weekly recurring trigger to create a new standup page in your team's meeting database, pre-filled with a template. This replaces the manual "create today's standup" step that people skip on busy mornings.

Archive completed items. On a monthly schedule, move all items with Status "Done" (older than 30 days) to an archive database. This keeps your active view clean without deleting anything. See the Notion project management guide for how to set this up as part of a broader system.

Trigger Zapier flows from Notion. The "Send webhook" action lets Notion fire a trigger to Zapier or Make. This opens up everything those platforms connect to: Gmail, Google Calendar, Airtable, Trello, and hundreds more. The apps that work with Notion roundup has a broader list of integrations worth knowing about.

Extending Automations with Zapier and Make

Notion's native automations are intentionally scoped. For anything beyond property edits, page creation, Slack messages, and webhooks, you need an external automation platform.

Zapier and Make (formerly Integromat) both have deep Notion integrations. Where Notion's webhook action sends data out, Zapier and Make can receive it and route it to other apps. Common use cases: creating a Notion page when a Google Form is submitted, syncing Notion tasks to Google Calendar, or emailing a client when a project status changes.

For calendar sync specifically, the guide on adding Google Calendar to Notion covers the most reliable methods, including both native options and third-party sync tools.

Limitations to Know Before Building

Notion automations are good at reacting to database changes, but they have real limits worth understanding before you build a system around them.

They don't run across databases automatically. An automation in your Tasks database can create a page in your Projects database, but it can't read data from your Projects database to inform its actions. Cross-database logic still requires manual setup or an external tool.

The "Property edited" trigger doesn't distinguish between who made the change. If an automation changes a property, it can re-trigger another automation watching that property, creating loops. Plan your trigger conditions carefully to avoid chains that run indefinitely.

You also can't trigger an automation from a formula result. Formulas calculate dynamically but don't count as a "property edited" event. If you want an automation to fire based on a calculated value, you need to route that calculation through a regular property that a person or another automation actually sets.

For Notion pricing details on which plan unlocks full automations, the pricing breakdown covers each tier's limits.

Best Tool to Use Alongside Notion Automations

Notion automations are good at keeping your databases tidy. What they don't do is help you decide when to actually work on the tasks they create and assign.

Lifestack connects to Notion and reads your tasks and projects, then builds a daily schedule around your energy levels and calendar. When a Notion automation creates a new task and assigns it to you, Lifestack picks it up and suggests when to do it based on how you're feeling and what's already on your calendar. It bridges the gap between tracking work in Notion and actually getting it done.

The Notion planner guide has more on how to structure your Notion workspace so that scheduling tools like Lifestack can read it effectively. Lifestack's annual plan is $49.99/year with a 7-day free trial; monthly is $9.99/month.

FAQ

What plan do I need for Notion automations?

Full database automations require a Plus plan at $10/seat/month billed annually ($12/month if billed monthly). Free plans are limited to buttons, which let you trigger manual actions but can't fire automatically without someone clicking. Business plans ($20/seat/month annual) add AI agent automation on top of database automations.

Can Notion automations send emails?

Not natively. Notion automations can send Slack notifications and Notion in-app notifications, but email isn't a native action. To send emails from Notion, use the "Send webhook" action to trigger a Zapier or Make workflow that handles the email send.

How many automations can I create in Notion?

Notion doesn't publish a hard cap on the number of automations per database or workspace on paid plans. In practice, you can have multiple automations per database. Each automation can include multiple chained actions.

Can I use Notion automations to sync with Google Calendar?

Not directly with native automations alone. You can fire a webhook from Notion that triggers a Zapier or Make flow to create or update Google Calendar events. For a simpler setup, some third-party tools offer direct Notion-to-Google Calendar sync without needing a webhook. The guide on adding Google Calendar to Notion covers the options.

Do Notion automations run in real time?

Property-edited and page-added triggers are near real-time, typically firing within a few seconds of the change. Recurring schedule triggers run at the scheduled time but can have a small delay depending on server load. Webhook-based actions to external services depend on the receiving service's response time.

Can I build a Notion automation without a Plus plan?

On the Free plan, you can create buttons that trigger actions manually when clicked. These are useful for repetitive tasks where you want one click to set multiple properties, but they won't fire automatically. If you need automations that run without user input, you'll need at least the Plus plan.