How to build automated workflows in Notion

How to Build Automated Workflows in Notion

Notion introduced native automations in 2023, expanding them significantly through 2025. As of April 2026, automations are available on Plus ($10/member/month), Business ($18/member/month), and Enterprise plans. Free plan users can view but not create automations.

Step 1: Open a Database

Notion automations are database-centric. Navigate to any database (table, board, calendar, gallery, or timeline view) and click the lightning bolt icon in the database toolbar, then select "New automation."

Step 2: Choose a Trigger

Available triggers include:

• Page added — When a new page is created in the database
• Property edited — When a specific property value changes
• Property matches condition — When a property meets a defined criteria

Triggers can be scoped with conditions. For example, "When Status property changes to Done" rather than triggering on every property edit.

Step 3: Define Actions

Available actions include:

• Edit property — Set or change a database property value
• Add page to database — Create a new page in another database
• Send Slack notification — Post a message to a Slack channel (requires Slack connection)
• Send webhook — HTTP POST to an external URL

Step 4: Chain Multiple Actions

Click "Add action" to create multi-step automations. Actions execute sequentially. Example: When a task status changes to "Complete," set the completion date to today, assign the next related task to the same person, and send a Slack notification.

Extending with External Tools

Notion's native automations cover basic workflows. For complex scenarios (conditional branching, loops, external API calls), connect Notion to Zapier, Make, or n8n:

• Zapier: 30+ Notion triggers and actions (new database item, update page, search)
• Make: Deep Notion modules with database queries, page creation, and block manipulation
• n8n: Self-hosted Notion integration with HTTP nodes for the full Notion API

Practical Example: Content Calendar Automation

1. Database: Content Calendar with Status (Draft, Review, Approved, Published)
2. Automation 1: When Status changes to "Review" → Assign "Reviewer" property to Editor
3. Automation 2: When Status changes to "Approved" → Set "Publish Date" to next Monday
4. Automation 3: When Status changes to "Published" → Send Slack message to #content-updates

This eliminates manual status-tracking updates and ensures the team stays informed without checking Notion constantly.

Current Limitations (April 2026)

• No conditional branching (if/else logic) within automations
• No time-based triggers (scheduled automations)
• No loop or batch processing
• Limited to database triggers (cannot trigger from page content changes)
• Button-triggered automations are separate from database automations