Guide · Notion automations
When Notion automations are enough — and when to hand off
Stay on Notion automation if the work finishes there. Hand off when a plan gate or a silent stop gets in the way. See the workspace scorecard. The automation scorecard is the live scorecard: Totals are not published yet. Self-hosted is a separate lane. This page does not add new scores.
Stay on Notion automation, or hand off
Stay
Stay on Notion automation if…
The job finishes in the workspace: a status or property change updates another page, a button click runs a database automation, or Slack, Gmail, or an in-workspace notify is enough on the plan Notion names. A paid-plan Send webhook POST is enough — properties only, at most five. The person who created the Slack or Gmail job can still edit it.
Hand off
Hand off / don’t rely on it if…
The same event has to write several other apps, chain a step Notion will not fire, send page contents, use more than five webhook POSTs, or be edited by someone other than the Slack or Gmail creator. Free Plan can create Slack notification automations only. Restricted pages, a locked database, a view mismatch, or a failed webhook can stop the run without a clear ping. You want the Make walk-through — that is Notion automation limits — when to hand off to Make. You want the class list — When automations fail. You want a quiet miss after you hand off — When automations look fine. This page names Notion’s native limits. It does not rank products.
A stay-on-Notion-automation or hand-off check for one workspace job.
- You keep work in Notion and need when built-in automations are enough.
- You need Free/paid gates and silent stops — not a Make walk-through.
- You want the workspace scorecard — totals are not published yet.
Read more
What this page tells you. Help a small team know when Notion’s native automations are enough — what Free and paid can do, published ceilings, and silent stops — and when to hand off to Make, n8n, or Zapier. This page does not reprint the Make Watch Events walk-through, the quiet-miss checklist, the class list, or the meter. It adds no score cells. Dated list prices live on the picker after you decide to hand off.
GuideSome scores not shown yetVendor pages accessed 2026-09-17Workspace scorecard
This page is not a Make walk-through
The question here is what Notion’s own automations can finish — and which gates stop them. Notion automation limits — when to hand off to Make is the Make pattern after that call: a paid-plan Send webhook into a Custom Webhook, or Make’s Notion Watch Events then a get-item. This page does not reprint that walk-through.
When automations look fine — catch silent breakage is the quiet-miss checklist after a job is live. The class list lives on When automations fail — a practical taxonomy. How each product names success lives on Error handling across Make, n8n, and Zapier. What to count lives on How to meter automation. Who owns reconnects lives on Who should own your automations. Name one hub first — one object, one write path — on Name one system of record for small-team ops (Notion, Airtable, or Superhuman Docs (formerly Coda)). This page does not reprint those reads. It does not rank tools. It does not add new scores.
This page also skips a list-price table. The question is whether Notion’s native automations can finish the job — not which plan to buy. After you decide to hand off, dated official list prices live on the picker. This page does not claim you will save money, and it does not add a monthly dollar from a /500 score.
Stay in Notion or hand off
Stay when the work finishes in the workspace. Hand off when the same event has to run other apps, chain steps Notion will not fire, or be owned by someone other than the Slack or Gmail creator. Name the hub first: Name one system of record for small-team ops. After you hand off, pick the product on Which automation tool for small teams or open the Make-specific pattern on Notion automation limits — when to hand off to Make.
Swipe sideways on a narrow screen. Not a scored table.
| Situation | Stay in Notion | Hand off |
|---|---|---|
| A status or property change should update another page in the same workspace | Yes — Edit property, Add page to, or Edit pages in. | No, unless that write also has to hit a CRM, sheet, or helpdesk. |
| You need a Slack ping, an in-workspace notification, or a Gmail send | Yes on the plans Notion names. Free Plan can create Slack notification automations only. Slack channel sends sit on Plus, Business, and Enterprise. In-workspace notify is capped at 20 people. | Yes if the mail or chat app is not Gmail or Slack, or several apps must run in one job. |
| A person clicks a button that should run a database automation | Yes. A button click can trigger a database automation. Other automations cannot. | Not required for the click itself. |
| A paid-plan Send webhook POST is enough | Yes — properties only, at most five webhook actions, POST only. | Yes if you need page contents, more than five POSTs, another HTTP method, or a signed integration webhook plus a follow-up fetch. |
| The same Notion event must write several other apps in one run | No. Built-in actions stay in-workspace, Slack, Gmail, or a webhook POST. | Yes — Make, n8n, or Zapier owns the multi-app side. |
| You need one automation to fire another | No. Database automations cannot trigger other automations. | Yes. Make, n8n, or Zapier can branch, retry, and chain on purpose. |
| Someone other than the Slack or Gmail creator must edit the job | No for those two actions. Slack automations can be edited only by the creator. After a Gmail account is linked, only that person can edit. | Yes. Put the connection on the person who owns ops. |
Source: Notion — database automations · Notion — webhook actions · Notion — buttons · accessed 2026-09-17
What Free and paid can do
Plan gates, paraphrased from Notion help and pricing plan names, accessed 2026-09-17. This is not a score. This page does not add a list price or a run pack.
Free
Free Plan
Free Plan can create Slack notification automations only. It can use template automations without editing them. Guests cannot create database automations. Buttons exist on all plans; Send mail to and Send webhook on a button sit on paid plans.
Paid
Plus, Business, and Enterprise
Full database automations sit on paid plans. Create, edit, or delete needs a paid-plan user with full access to the database. Slack channel sends sit on Plus, Business, and Enterprise. Send webhook is a paid-plan action. Enterprise workspace owners can turn off webhook actions for the whole workspace.
Triggers
What can start a run
Three types: Page added, Property edited, and Every {frequency} (day, week, month, and so on, with a start, end, time, and timezone). One trigger or several. When any of these occur or When all of these occur. A recurring trigger cannot be paired with another type. Multiple is edited conditions that must all fire need to land inside about three seconds.
In-workspace
Edits that stay in the hub
Actions that stay local: Edit property, Add page to, and Edit pages in. Assign a person when status changes. Mark sub-items complete when a parent is complete. Recurring triggers work with every action except Edit property. Mentions and formulas sit in actions, not triggers.
Source: Notion — database automations · Notion — buttons · Notion pricing · accessed 2026-09-17
Silent gates and published ceilings
Hard ceilings and quiet stops, paraphrased from Notion help, What’s New, and pricing plan names, accessed 2026-09-17. This is not a score. Notion’s help does not publish a monthly run cap for database automations. This page does not add a monthly dollar or an extra quota.
Swipe sideways on a narrow screen.
| Topic | What Notion publishes |
|---|---|
| Plan gate | Full database automations sit on paid plans. Create, edit, or delete needs a paid-plan user with full access to the database. Guests cannot create them. Free Plan can create Slack notification automations only, and can use template automations without editing them. Slack channel sends sit on Plus, Business, and Enterprise. Send webhook is a paid-plan action. Pricing names those plans; this page does not add a list price or a run pack. |
| Triggers | Three types: Page added, Property edited, and Every {frequency}. One trigger or several. When any of these occur or When all of these occur. A recurring trigger cannot be paired with another type. Multiple is edited conditions that must all fire need to land inside about three seconds. |
| Actions | Edit property, Add page to, Edit pages in, Send notification to (up to 20 people), Send mail to (Gmail), Send webhook, Send Slack notification to (Plus, Business, and Enterprise), and Define variables. Recurring triggers work with every action except Edit property. Mentions and formulas sit in actions, not triggers. Formulas cannot be used when sending Slack notifications. |
| Webhook ceiling | At most five webhook actions per automation. POST only. Properties only, not page contents. Optional custom headers. The action does not require authentication. Not available at the workspace level. A failed webhook pauses the automation until someone resumes it. |
| Volume | Notion help does not publish a monthly database-automation run cap. What’s New, accessed 2026-09-17, also does not publish one. What the help does publish: a three-second change window; Gmail’s own recipient and daily send limits (Notion does not print those numbers); at most five webhook actions; POST only; properties only, not page contents; a failed webhook pauses the automation until someone resumes it; formula and webhook issues may not notify you. |
| Pages that will not run | Automations will not act on pages whose access is restricted. They only run if the page still matches the chosen view when the trigger occurs. Locked databases do not fire. Date calculations such as dateAdd can fail on an empty field — Notion’s own fix is a filtered view that excludes empties. |
| Who owns ops | Slack automations: creator only. Gmail-linked automations: the person who linked Gmail. Enterprise workspace owners can turn off webhook actions for the whole workspace. After an error pause, someone has to turn Active back on by hand. |
Sources under Sources. Integration webhooks (a Notion connection subscription) are a different path from Send webhook — they notify a URL when pages or databases change, then the connection still has to fetch the latest content.
Source: Notion — database automations · Notion — webhook actions · Notion — automations help · Notion — What’s New · Notion pricing · accessed 2026-09-17
Who owns the job
Native Notion automations fail quietly unless someone is named. This is ownership, not a second score. Name the person on Who should own your automations before you rely on the run. After a handoff, product-lane retries live on Error handling across Make, n8n, and Zapier — this page does not reprint that compare.
- Name one operator before you rely on the run. If a webhook or formula fails, Notion says you may not be notified. A paused automation stays paused until someone opens the database and sets it Active again.
- Notion will notify you in some cases — a missing database or property, or a Gmail or Slack connection that is no longer valid. In other cases, including formulas that do not execute and webhook issues, you may not be notified. Click the notice, fix the job, then turn
Activeback on by hand. - If the only person who can edit Slack or Gmail automations leaves, the job is stuck. That is a reason to hand off: put the connection on the person who owns ops.
- Integration webhooks (a Notion connection subscription) are a different path from Send webhook. They notify a URL when pages or databases change. The event is a signal — the connection still has to fetch the latest content. Share the database with that connection first.
- If nobody would notice a miss, do not ship yet. Pass or defer on What’s worth automating. If a job still looks on after you hand off, use When automations look fine — catch silent breakage — this page does not reprint that checklist.
Source: Notion — database automations · Notion — webhook actions · Notion — integration webhooks · accessed 2026-09-17
After you decide to hand off
After you hand off, Notion still holds the row if that is the named hub. Make, n8n, or Zapier owns the multi-app side. Cite the automation card only here: Totals are not published yet. n8n Self-host is not a fourth cloud seat. Live card: Make vs n8n vs Zapier.
Keep the object of record on Name one system of record for small-team ops — Notion, Airtable, or Superhuman Docs (formerly Coda). Name who gets reconnects and a paused job on Who should own your automations. After the job is live, a green history is not the write — When automations look fine and Error handling across Make, n8n, and Zapier.
Pattern
Notion to Make
Notion stays the system of record. Make runs the multi-app side. Two patterns: Send webhook into a Custom Webhook, or Make’s Notion Watch Events then a get-item. Full walk-through: Notion automation limits — when to hand off to Make.
Picker
Which tool
Already sure you need Make, n8n, or Zapier? Four questions — who builds, volume shape, self-host, catalog — then a pick. Which automation tool for small teams.
Primary CTA stays the live scorecard. This button is the next read after you hand off.
Scoring status
Scoring status
Workspace card: Notion vs Superhuman Docs (formerly Coda) vs Airtable. Different criteria from the automation scorecard. This page does not duplicate that sheet.
The live card is Make vs n8n vs Zapier. Totals are not published yet.
When-to-pick copy lives on Make vs n8n vs Zapier — when to pick each. Pair reads: Make vs n8n · Make vs Zapier · n8n vs Zapier. Scoring rules: Methodology.
Product links
Official
Notion
Official site: Notion · no affiliate ID · not a partner mark
n8n and Zapier are named for the hand-off call. Totals are not published yet. Official sites: n8n · Zapier · no affiliate ID.
Sources
Primary Notion help, What’s New, and the integration-webhook reference. Access date for every limit on this page: 2026-09-17. This page does not add a monthly run cap or an extra /500.
- Notion — database automations · accessed 2026-09-17
- Notion — webhook actions · accessed 2026-09-17
- Notion — buttons · accessed 2026-09-17
- Notion — automations help · accessed 2026-09-17
- Notion — What’s New · accessed 2026-09-17
- Notion — integration webhooks · accessed 2026-09-17
- Notion pricing · accessed 2026-09-17
FAQ
When are Notion’s built-in automations enough?
When the work finishes in the workspace: edit a property, add or edit pages, notify up to 20 people, send Gmail, ping Slack on a paid plan that includes it, or fire a paid-plan Send webhook with properties only. A button click can trigger a database automation. Other automations cannot.
When should a small team hand off to Make, n8n, or Zapier?
When the same Notion event has to run several other apps, needs page contents or more than five webhook POSTs, must chain steps Notion will not fire, or must be edited by someone other than the Slack or Gmail creator. Name the hub first on Name one system of record for small-team ops. Then pick the product on Which automation tool for small teams, or open the Make pattern on Notion automation limits — when to hand off to Make.
What can Free Plan create versus a paid plan?
Full database automations sit on paid plans. Create, edit, or delete needs a paid-plan user with full access to the database. Guests cannot create them. Free Plan can create Slack notification automations only, and can use template automations without editing them. Slack channel sends sit on Plus, Business, and Enterprise. Send webhook, and Send mail to on a button, sit on paid plans. This page does not add a list price.
Does Notion publish a monthly automation run cap?
No. Database-automation help and What’s New, accessed 2026-09-17, do not publish a monthly run cap. This page does not add one. What they do publish: a three-second change window, Gmail’s own send limits (Notion does not print those numbers), at most five webhook actions, POST only, properties only, and a pause after a failed webhook.
Who can create and edit Notion database automations?
Paid-plan users with full access to the database. Guests cannot create them. Free Plan can create Slack notification automations only. Slack automations can be edited only by the creator. After someone links Gmail, only they can edit that automation. Enterprise workspace owners can turn off webhook actions for the whole workspace.
What silent gates can stop a run without a clear error?
Restricted pages, a locked database, a page that no longer matches the chosen view, and a recurring template or another automation that tries to fire the next job. A failed webhook pauses the automation until someone resumes it. Formula and webhook issues may not notify you. After a pause, someone has to turn Active back on by hand. Name that person before you rely on the run. Then see Who should own your automations and When automations look fine.
Is Send webhook the same as an integration webhook?
No. Send webhook is a paid-plan automation action: POST, properties only, at most five per automation, no authentication required. Integration webhooks are a connection subscription that notifies a URL when pages or databases change — the connection still has to fetch the latest content. Share the database with that connection first.
How is this page different from the Make handoff, look-fine, and the class list?
This page names Notion’s native limits: what Free and paid can do, published ceilings, and silent gates. Notion automation limits — when to hand off to Make is the Make Watch Events and Custom Webhook walk-through. When automations look fine is the quiet-miss checklist. When automations fail is the class list. How to meter automation is the unit count. This page does not reprint those reads.
Does this page add a Notion-to-Make score?
No. Totals are not published yet. This guide adds no cells.
Affiliate disclosure
Product links on this page: Notion, n8n, and Zapier stay official-site URLs with UTM only — no invented IDs. Make Partner (pc=stackscorecard) is live elsewhere on the site and is not the primary call here. Rankings are not sold. Wordmarks are not partnership marks. Policy: Affiliate disclosure · Disclosures. Commissions do not move a score, a weight, or a pricing cell.