Guide · Notion and Make
Notion automation limits — when to hand off to Make
Notion on the workspace scorecard. Totals are not published yet. Self-hosted is a separate lane on the automation scorecard. n8n Self-host is a separate lane. Not a second ranking.
- You keep Notion as the system of record and need when native automations are enough.
- You need when Make — or another iPaaS — should own the multi-app run, and when not.
- You will not mix this workspace card with the automation scorecard — separate criteria sheets.
Read more
What this page tells you. When to keep work in Notion vs hand off to Make — and when not. Notion keeps the system of record. Make owns multi-app workflows. Native Notion database automations cover in-workspace edits, Slack, mail, and webhooks on paid plans. Hand off to Make for deep multi-app runs or instant Watch Events beyond Notion’s built-in actions. It adds no score cells.
Workspace scores publishedVendor pages accessed 2026-09-16Workspace scorecard
Stay in Notion or hand off to Make
Use Notion when the work stays in the workspace. Use Make when the same change has to run other apps Notion cannot finish on its own. Name the hub first: Name one system of record for small-team ops. Stay-or-hand-off for any iPaaS: When Notion automations are enough — and when to hand off. This page is the Make pattern after that call.
Stay
Stay in Notion
- A status or property change should update another page or database in the same workspace.
- You need a Slack ping, an in-workspace notification, or a Gmail send from a database event.
- A button should run a database automation. Buttons can trigger those automations; other automations cannot.
- On a paid plan, a Send webhook POST is enough — properties only, no page body.
Hand off
Hand off to Make
- The same Notion event has to write a CRM, sheet, helpdesk, or several other apps in one run.
- You need instant page or database events via Make’s Notion Watch Events (connection webhooks), beyond Notion’s built-in actions.
- You need more than five webhook POSTs, page contents, or a follow-up fetch Make can map downstream.
Source: Notion — database automations · Notion — webhook actions · Make — Notion app · accessed 2026-09-16
What Notion automations do well
Notion’s database automations are built for work that finishes in the workspace. That is the keep lane. Paraphrased from Notion help, accessed 2026-09-16. This is not a score.
In-workspace
Edits that stay in the hub
Triggers Notion names: Page added, Property edited, and a recurring Every {frequency}. 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.
Notify
Slack, mail, and in-workspace notify
Send notification to reaches up to 20 people in the workspace. Send mail to sends from a linked Gmail account. Send Slack notification to sits on Plus, Business, and Enterprise. Free Plan can create Slack notification automations only. If the chat or mail app is not Gmail or Slack, that is already a handoff.
Click
A person clicks a button
A button click can trigger a database automation. Other automations cannot. Use a button when a person should start the run on purpose. Do not expect a recurring template, or an automation that creates a page in another database, to fire the next automation.
Signal
A paid-plan webhook POST is enough
Send webhook on paid plans POSTs properties to a URL you name. That is enough when the receiver only needs those properties — a Custom Webhook in Make, or any URL that can accept a POST. It is not enough when you need page contents, another HTTP method, or more than five POSTs.
Source: Notion — database automations · Notion — webhook actions · Notion — buttons · accessed 2026-09-16
Hard limits and failure modes
Paraphrased from Notion’s help pages, accessed 2026-09-16. Full database automations sit on paid plans. Notion’s help does not publish a monthly run cap for database automations. This page invents no monthly dollar. This is not a score.
Swipe sideways on a narrow screen.
| Topic | What Notion publishes |
|---|---|
| Who can create them | Full database automations on paid plans. Free Plan can create Slack notification automations only, and can use automations that came with a template without editing them. Guests cannot create database automations. |
| Who can edit them | Paid-plan users with full access to the database. Slack automations can be edited only by the person who created them. After someone links Gmail, only they can edit that automation. |
| What they cover | In-workspace edits (properties, add or edit pages), in-workspace notifications, Gmail send, Slack notifications, and Send webhook on paid plans. |
| Automation chaining | Automations cannot trigger other automations. A button click can. A recurring template, or an automation that creates a page in another database, will not. |
| Webhook method | POST only. Available on paid plans in buttons, database buttons, and database automations. |
| Webhook count | At most five webhook actions per automation. |
| Webhook payload | Database page properties only — not page contents. Optional custom headers. The action does not require authentication. |
| Failure modes | A failed webhook pauses the automation until someone resumes it. Formula and webhook issues may not notify you. Multiple is edited conditions that must all fire need to land inside about three seconds. Automations will not act on restricted pages, locked databases, or a page that no longer matches the chosen view. |
Sources under Sources. Workspace owners on Enterprise can turn off webhook actions for the whole workspace. 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 — integration webhooks · accessed 2026-09-16
When Make — or another iPaaS — owns the run
After you hand off, Notion still holds the row. Make, n8n, or Zapier owns the multi-app side. That is not a reason to pick it for every job. When the job is visual scenarios without a box, open When Make is the right pick. Four questions: Which automation tool for small teams.
Make owns
Make owns this run
- The same Notion event must write several other apps in one scenario.
- You need instant page or database events via Watch Events. Make delivers those only for pages connected to that connection.
- You need page contents or a follow-up fetch — Get a Data Source Item, then map downstream.
- You need more than five webhook POSTs, another HTTP method, or a signed connection webhook.
- You need branch, retry, or a chain Notion will not fire.
Not Make
Do not hand this to Make
- The work finishes in Notion. Keep it there.
- The connector you need is listed on Zapier and missing on Make. The catalog is the job-fit.
- You want the n8n editor hosted.
- You will own the box. It is not a fourth cloud seat.
Billing units for Make, n8n, and Zapier stay on Tasks vs credits vs executions. Do not invent a monthly dollar from a /500 score.
Source: Make — Notion app · Make — webhooks · accessed 2026-09-16
Two handoff patterns
Both keep Notion as the system of record. Make runs the multi-app side. Share the database with the Notion connection first.
Pattern A
Send webhook → Custom Webhook
A Notion database automation or button uses Send webhook when a status or property changes. Make starts on a Custom Webhook and maps the properties Notion posted. Make’s webhook help: custom webhooks create a URL you can call from an external app; they usually act as instant triggers.
Best when you already know the trigger (“Status is set to Done”) and the payload is properties only.
Pattern B
Watch Events, then get the item
Make’s Notion Watch Events uses connection webhooks. Instant page and database events fire for pages and databases shared with that connection. Then Get a Data Source Item and map the result downstream.
Need a polling fallback? Use Watch Data Source Items instead of instant events. Make: if an app does not provide webhooks, use a polling trigger.
Source: Notion — webhook actions · Make — Notion app · Make — webhooks · accessed 2026-09-16
Ownership after the handoff
A green Notion lightning bolt and a green Make history are not the write. Name the person who gets reconnects, a paused automation, and a disabled schedule before you turn the job on. Who should own your automations · When automations look fine.
- Share the database with the Notion connection or integration Make uses. Unshared pages do not appear in Make searches, and Watch Events only cover pages tied to that connection. Make: events are delivered only for pages connected to your connection.
- Automations will not act on pages whose access is restricted. Check share settings on the page.
- Guests cannot create database automations, even with full access to the database.
- Creating a Notion API connection is a workspace-owner step. After that, members still have to share each database with the connection. Make’s Notion app: an internal connection needs an internal integration token; a public connection asks you to select pages.
- If a Notion 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.
- In Make,
AccountValidationErrorhappens during initialization and cannot be swallowed by an error handler. When a scenario finishes with an error for the number of consecutive errors in a row, Make disables scheduling. That is a named person, not a second score.
Source: Notion — API connections · Make — Notion app · Make — fix errors and warnings · accessed 2026-09-16
Scoring status
Scoring status
Totals are not published yet. Live card: Make vs n8n vs Zapier. When-to-pick: Make vs n8n vs Zapier — when to pick each.
Workspace card. Live card: Notion vs Superhuman Docs (formerly Coda) vs Airtable. Different criteria.
This page does not cite a total. It adds no score cells and no Notion-to-Make ranking. Billing units for Make, n8n, and Zapier stay on Tasks vs credits vs executions. Scoring rules: Methodology.
Product links
Affiliate
Make
Partner signup. We may earn a commission. Rankings are not sold.
Try Make Affiliate. We may earn a commission. Affiliate disclosure
Official
Notion
Official site: Notion · no affiliate ID · not a partner mark
n8n and Zapier are named for the hand-off. Totals are not published yet. Official sites: n8n · Zapier · no affiliate ID.
We may earn a commission on Make links. Rankings are not sold. Affiliate disclosure · Disclosures · editor@stackscorecard.com
Sources
Primary vendor pages. Access date for every limit and module name on this page: 2026-09-16. This page invents no monthly run cap and no extra /500.
- Notion — database automations · accessed 2026-09-16
- Notion — webhook actions · accessed 2026-09-16
- Notion — API connections · accessed 2026-09-16
- Notion — buttons · accessed 2026-09-16
- Notion — integration webhooks · accessed 2026-09-16
- Notion pricing · accessed 2026-09-16
- Make — Notion app · accessed 2026-09-16
- Make — webhooks · accessed 2026-09-16
- Make — fix errors and warnings · accessed 2026-09-16
FAQ
Should I stay in Notion or hand the job to Make?
Stay in Notion when the change finishes in the workspace: edit a property, add or edit pages, notify Slack or in-workspace people, send Gmail, or fire a paid-plan Send webhook with properties only. Hand off to Make when the same status or page event has to run a deep multi-app workflow, needs page contents, more than five webhook POSTs, or instant Watch Events beyond Notion’s built-in actions.
When should I not hand off to Make?
Do not hand off when the work finishes in Notion. After you do need an iPaaS, Make is not automatic: pick Zapier when the catalog is the job, n8n Cloud when you want that editor hosted, or n8n self-host when you will own the box. It is not a fourth cloud seat. See When Make is the right pick. Name one system of record first.
What can a Free Notion plan automate?
Full database automations are on paid plans. A Free Plan can create Slack notification automations only. Free Plan users can also use automations that came with a template, but they cannot edit them.
Can one Notion automation trigger another?
No. Database automations cannot trigger other automations. A button click can trigger a database automation. A recurring template, or an automation that creates a page in another database, will not.
What does Notion’s Send webhook action actually send?
On paid plans it POSTs only. You can add up to five webhook actions per automation, optional custom headers, and database page properties — not page contents. The action does not require authentication. A failed webhook pauses the automation until someone resumes it.
Do I have to share the Notion database with Make?
Yes. Share the database with the Notion connection or integration Make uses. Make’s Watch Events only fire for pages connected to that connection. Unshared pages do not appear in Make searches. Guests cannot create database automations.
Who owns the job after a Notion to Make handoff?
Name the person who gets reconnects, a paused Notion automation, and a disabled Make schedule. Make’s AccountValidationError happens during initialization and cannot be swallowed by an error handler. Consecutive module errors can disable scheduling. Notion may not notify you when a formula or webhook fails. See Who should own your automations and When automations look fine.
Does Notion publish a monthly automation run cap?
No. Database-automation help, accessed 2026-09-16, does not publish a monthly run cap. What it does 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. This page invents no monthly dollar.
Does this page add a Notion-to-Make score?
No. This guide adds no cells.
Affiliate disclosure
Product links on this page: Make is a live partner signup (pc=stackscorecard) and is marked affiliate. Notion, n8n, and Zapier stay official-site URLs with UTM only — no invented IDs. We may earn a commission on Make. Rankings are not sold. Wordmarks are not partnership marks. Policy: Affiliate disclosure · Disclosures. Contact editor@stackscorecard.com. Commissions do not move a score, a weight, or a pricing cell.