What we do
Tools
Industries
Department
How we workLet's talk →
Home/Notion
Notion

Notion Automation: What Runs Inside Notion, and What Has to Reach In From Outside

Notion can now automate a fair amount by itself. A database can set properties, add pages, notify people, post to Slack, send Gmail and fire a webhook when something changes. What it can't do is notice a change in your CRM, billing tool or ops system. Below: where each built-in tool lives, which one fits which job, why an automation sometimes doesn't fire, and the point where you need a real connection.

Where Notion stops

It holds the team's knowledge until nobody updates it, and then pages go stale.

Stuck on Notion? Let's solve it →
Where Notion automation lives

Database automations: open the database, click the lightning icon at the top, then New automation. Pick a trigger (a page is added, a property is edited, or a schedule) and one or more actions.

Database ⚡ New automation

Buttons: a button on a page or in a database row runs a set of steps when someone clicks it. Use these when a person should decide the moment, not a property change.

Custom Agents: Notion's AI agents can run on a schedule, on Notion events or on Slack messages, where your plan includes them. Good for summaries and triage, not for exact data copying.

Anything outside Notion: the Notion API or a connector. Notion's own automations can send things out, but nothing inside Notion watches your other systems.

Pick the tool by the job

Most teams reach for Zapier first. Check the first three rows before you do, because Notion covers them on a paid plan.

What you want to happen Use this Where it stops
Status set to Done stamps a date and tells the owner A database automation: Property edited trigger, Edit property and Send notification to actions. Nowhere, for this job. The full set of triggers and actions is on our Notion automations page.
A new project creates its task pages in another database Add page to in an automation, or a database template that brings its own sub-pages. See Notion templates. Values that live elsewhere, such as the client's contract amount, still get typed in.
A weekly reminder to review open items An automation on the Every {frequency} trigger, sending a notification or a Slack message. Recurring triggers can't use Edit property, and can't be combined with other trigger types.
Tell another system when a Notion row changes The Send webhook action, which POSTs the page's data to a URL you set. Something has to be listening at that URL, and Notion doesn't always tell you when a webhook call fails.
Numbers from the CRM or billing tool shown on a Notion page A sync built on the Notion API, running on a schedule or on the other system's events. This is the gap. No built-in Notion action can go and fetch data from another system.
A Notion database used as a light CRM, kept in step both ways A two-way sync with matching rules, built on the API. Start with how your Notion databases are related. Duplicates and edit conflicts. Two-way is a design job, not a toggle.

When a Notion automation doesn't fire

These come straight from how Notion runs automations, and they explain most "it worked yesterday" reports.

One automation was supposed to set off another

How you'll know: The first one runs and changes a property, and the second, which watches that property, never moves.

Fix: Automations don't trigger other automations. Combine the steps into one automation, or use a button, since button actions can trigger automations.

The page dropped out of the view's filter

How you'll know: It runs for some rows and not others, and the ones that miss look identical.

Fix: Automations built on a filtered view only act on pages that still match the filter after the edit. Widen the filter or build the automation on an unfiltered view.

It paused itself

How you'll know: Nothing runs at all after someone renamed a property, deleted a linked database or disconnected Slack or Gmail.

Fix: Open the lightning menu, find the automation, and fix the missing property or connection. It stays paused until you do.

Some pages are private or the database is locked

How you'll know: The automation skips certain pages, or stops on the whole database.

Fix: Automations don't act on pages with restricted access and won't run on a locked database. Guests also can't create automations, even with full access.

The Send webhook action, or a sync someone runs

The webhook action is how Notion reaches out. Whether that's enough depends on what's at the other end.

Send webhook action

Notion pushes, once

  • Fires on a page add, a property edit or a schedule.
  • Sends a POST to one URL with the data you pick.
  • Fine when the receiver is a tool that already accepts webhooks and you can live with the odd miss.
  • Nothing comes back into Notion from it.
A built sync

Both sides kept honest

  • Reads from the CRM, billing or ops system and writes into Notion, so the numbers are current.
  • Matches rows to existing records instead of creating duplicates.
  • Logs each run and retries what failed, so a missed change shows up somewhere.
  • Can write status changes made in Notion back out to the system that has to act on them.

If the data only ever leaves Notion and a missed event is harmless, the webhook action is enough. If anything has to arrive in Notion from elsewhere, you need the right column.

The Notion page that goes stale first

The most common complaint behind this search is a dashboard. Someone built a lovely Notion page with weekly sales, open tickets and project status, and it only stays current while one person copies numbers in every Friday. By Monday it's already old. No Notion automation fixes that, because the numbers start life in another system. A scheduled sync on the API does.

The second is onboarding. A deal closes in the CRM or a hire is signed, and someone duplicates a template and types in the client name, contract value and start date. A template gets you the shape of the page; a connection from the CRM gets you the page already filled in. Some teams also keep an intake log or light CRM as a Notion database and want form leads to land in it, and status changes made there to flow back out.

n-frames builds those connections on the Notion API and keeps them running: Notion stays the place people read and work, and the source systems stay the record. If you're still choosing tools, Notion vs ClickUp covers the trade-off, and Notion formulas and Notion integrations cover the in-between options.

Questions people ask

What is Notion?

Notion is a workspace app built from pages, notes and databases you design yourself. Teams use it as a wiki, a project tracker, a content calendar or a light CRM, shaped to how they already work.

Is Notion free to use?

There's a free plan that suits individuals and small teams. Paid plans add things like more file uploads, longer page history and admin controls. For automation the plan matters: creating and editing database automations needs a paid plan, and the free plan is limited to a small subset.

Is there a Notion desktop app?

Yes. Notion has desktop apps for Mac and Windows, mobile apps for iOS and Android, and the browser version, all working on the same workspace. Automations run on Notion's side, so they don't need anyone's app open.

Is Notion good enough to run as a CRM or ops system?

For a small team with a simple pipeline, often yes, and built-in automations now handle the status updates and reminders. It strains when records must match your accounting system exactly, when you report across thousands of rows, or when events in other tools should change Notion. At that point connect Notion to the system of record rather than stretching it.

Can a Notion automation send email or post to Slack?

Yes. A database automation can send mail from a linked Gmail account and post to a Slack channel. Only the person who connected Gmail or created the Slack automation can edit it, which catches teams out when that person leaves.

Do I still need Zapier or Make for Notion automation?

Not for anything that starts and ends inside Notion. You may for triggers that start somewhere else, since Notion can't watch other systems. When the volume is high or the matching is fiddly, a direct API connection is usually steadier than a chain of zaps.

Who builds Notion automations that reach other systems?

n-frames does. We set up the native automations where they're enough, and build and run the API connections that bring CRM, billing and ops data into Notion and send Notion changes back out.

Keep reading

Notion Automations How to build Notion automations step by step: triggers, actions, variables, buttons versus database automations, and what the Send webhook action sends.Notion API Make your first Notion API call, fix object_not_found and version errors, understand data sources, and know what Notion webhooks actually send you.Notion Database How to create a Notion database, add views, link two databases with a relation and roll up totals, plus how to bring in data that lives outside Notion.Notion Template Guide Where to find a Notion template, how to build your own as a database template, and how to stop refilling the same template by hand for every client.Notion Formula Examples for Formulas 2.0 How Notion formulas work: prop(), if, ifs, dateBetween, lists through relations, examples you can paste, and why a formula errors or comes back blank.Notion HubSpot Integration HubSpot now builds a Notion data sync. What it carries, when a partner app or Zapier fits better, and the other Notion integrations worth knowing.Notion vs ClickUp Notion vs ClickUp, decided by whether your work starts as a page or a task. Which teams lean where, what to check before moving, and running both.When Airtable Automations Hit Their Limits Why an Airtable automation fails or stops: monthly run allowances, Run a script limits, which trigger fits each job, and what belongs outside the base.Zapier Webhook Setup How to catch a webhook in Zapier, send POST, GET or custom requests out, which plans include Webhooks by Zapier, and why hooks fail without warning.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.