Notion Automations: Buttons, Database Automations and Integrations

Notion automations come in four layers. Buttons run a set of actions when someone clicks them, and work on every plan, though some actions need a paid plan. Database automations run on their own when a page is added, a property changes or a schedule comes round, and are a paid-plan feature. Webhook actions, on paid plans, let either one send data to another app. Past that you leave Notion: Zapier and similar tools connect it to other apps, Custom Agents on Business and Enterprise run AI work in the background, and an AI assistant you already use can reach Notion over MCP. Pick the lowest layer that does the job.

This guide follows Notion’s help center as of October 1, 2026. Plans are named, not priced: Free, Plus, Business and Enterprise.

Buttons: automation you click

A button is the simplest way to automate Notion, because a person decides when it runs. According to Notion’s buttons guide↗ (opens in a new tab), buttons are available on all plans, but certain actions are only available on paid plans. Anyone with Full access or Can edit on the page can create, edit and click them. The actions:

• Insert blocks: drop a block of text, a checklist or a toggle onto the page. A button that inserts a dated agenda is the classic use; the team meeting agenda template is a good thing to put behind one.
• Add page to, and Edit pages in: create a page in a database with properties already set, or change properties on pages in a database.
• Send notification to: notify up to 20 workspace members, or the people in a person property.
• Send mail to: send an email from your Gmail account. Paid plans only.
• Send webhook: send an HTTP POST to a URL. Paid plans only.
• Send Slack notification to: post to a Slack channel. Plus, Business and Enterprise only.
• Show confirmation, Open page or URL, and Define variables, for warnings, navigation and values the later steps can reuse.

Databases also have a button property, so each row can carry its own button, such as Mark done, which sets the status and stamps today’s date in one click. Notion calls these database buttons and, like page buttons, they are on all plans with some actions paid only.

Database automations: rules that run on their own

A database automation is a rule attached to a database: when this happens, do that. Notion’s database automations guide↗ (opens in a new tab) lists three kinds of trigger, and you can combine several with and or or:

• A page is added to the database.
• A property is edited, with conditions, such as Status changes to Done.
• A recurring schedule: every day, week, month and so on.

The actions mirror the button actions: edit properties, add a page to a database, edit pages in another database, send a notification, send Gmail, send a webhook, send a Slack notification and define variables. Three examples that earn their place on a task list:

Trigger: Status is set to Done
Action:  Edit property Completed on -> today

Trigger: Status is set to Ready for review
Action:  Edit property Assignee -> Dana
         Send notification to -> Dana

Trigger: Every Monday at 9:00 AM
Action:  Add page to Tasks: "Weekly review", Status To do

Plans and limits to know

• Plans: database automations are available on paid plans, and are created, edited or deleted by paid-plan users with full access to the database. Guests cannot create them.
• The Free plan: the same help page says Free plan users can create Slack notification automations but no other kind, and can use automations that come in templates without editing them. It also lists the Send Slack notification action as Plus, Business and Enterprise only. The Free-plan exception appears to mean Notion’s older Slack notifications, so check in your own workspace before planning on it.
• No chains: database automations cannot be triggered by other automations. A person clicking a button that creates a page does trigger them.
• Restricted pages: automations will not act on pages whose access is restricted.
• Breakage: an automation stops when a property it edits is deleted or a Gmail or Slack connection needs signing in again. Fix it from the automation itself.

Webhooks: sending Notion data elsewhere

The Send webhook action is the bridge from Notion’s built-in automation to anything with a URL. Notion’s webhook actions guide↗ (opens in a new tab) sets the limits: paid plans only, available in buttons, database buttons and database automations, up to five webhook actions per automation, POST requests only, custom headers allowed, and only database page properties, not page contents, in the payload. If the receiving system needs the body of the page, it has to fetch it through the API.

Do not confuse these with the API’s own integration webhooks↗ (opens in a new tab), which a developer sets up on a Notion connection. Those send events such as page.created, page.content_updated and comment.created, carry IDs and metadata rather than content, and need an endpoint that passes a verification step. They suit a developer building an integration; webhook actions suit someone wiring a button to a workflow tool.

Integrations: Zapier and other workflow tools

When the job runs across apps, a workflow tool is usually simpler than webhooks. Zapier’s Notion integration↗ (opens in a new tab) offers triggers such as New Data Source Item, Updated Properties in Data Source Item and New Comment, and actions such as Create Data Source Item and Update Data Source Item. Notion’s API calls the table behind a database a data source, which is why the names read that way. Typical uses: a form submission becomes a task, a new support ticket becomes a row, a task marked Done posts to a channel. Make and n8n do the same with more control; workflow automation tools compares the three.

AI: Notion’s agents and assistants over MCP

Rules do the same thing every time. When the steps depend on reading something, such as triaging a request or writing a weekly summary, an AI agent fits better, and Notion offers two of its own. Notion Agent is the assistant you work with inside Notion; Notion says it can create and edit pages and databases with the same permissions you have. Custom Agents↗ (opens in a new tab) run in the background without anyone opening a chat: Notion describes them as following instructions you define, reading from pages, databases and certain connected apps, and running on a recurring schedule, on Notion events such as a page being created or a property updated, or on Slack events. They need a Business or Enterprise plan, and Notion’s help center says premium AI models spend Notion credits that an admin has to turn on.

The other route runs the opposite way: an assistant you already use, such as Claude, ChatGPT or Cursor, connects to Notion MCP and works your workspace from its own window, with your Notion permissions. That suits work you start by asking, not work that should fire on its own. Each piece has its own post here, so one line each:

• Setting it up in Claude Code: Notion MCP with Claude Code.
• The tools it gives an assistant, and what it cannot do: what can Notion MCP do.
• When an integration on the API is the better route: Notion MCP vs the Notion API.

Choosing the layer

1. A person decides when it runs: a button.
2. It should happen every time something changes in one database: a database automation.
3. It has to reach another app: a webhook action if the app takes a POST, otherwise Zapier, Make or n8n.
4. It needs judgment, not a fixed path, and should run unattended: a Custom Agent, on Business or Enterprise.
5. You want to ask for it in the AI tool you already use: that assistant over Notion MCP.

Write each automation down where the team can see it, with its trigger and what it changes. An automation nobody remembers is the first suspect when a property changes and nobody knows why.

Where the work lands

Automations produce work: a bug to look at, a request to answer, a failed job to rerun. If that work lives on a fenbs board rather than in Notion, the same tools reach it. Zapier, Make, n8n or an agent can connect over MCP at https://fenbs.ai/api/mcp with a token issued by hand under Settings, with a name, only the scopes it needs and an optional expiry, and revoking it stops the workflow without touching anyone’s sign-in. Every change is recorded in History with who made it, so the team can tell which tasks a workflow filed. fenbs has no built-in automation rules, due dates or recurring tasks, so it is not a replacement for any of the layers above, only a board for what they produce. If you are still building your list, Notion to-do list covers the three setups first.