Notion Automations Not Working: Fix by Symptom (2026)

Notion automations usually break for one of three reasons: the page fell outside the view the automation watches, the person who built it lost edit access to something it touches, or a connected app like Slack quietly revoked its token. Notion rarely tells you which one happened — it just stops running. Match your symptom below rather than re-checking trigger logic from scratch.

I get pulled into this every few weeks: a status-update automation worked fine for two months, then silently stopped, and nobody noticed for ten days. Notion’s automation engine holds up well once you know its edges — but those edges aren’t documented in the builder. This is organized by what you’re seeing, not by feature: find your symptom, work the causes in order of likelihood, then check the prevention section.

The automation never fires at all

You added a page or edited the trigger property, and nothing happened. This has a short list of real causes.

1. The page doesn’t match the view the automation is scoped to

Every database automation runs against the whole database or one specific view. If it’s scoped to a view — filtered to Status: Active, say — a page must match that filter when the trigger fires, not just at some point in its life. Notion’s docs are explicit: automations only run if the page still matches the view at that moment.

1. Click the lightning bolt automations icon and check which view the automation is bound to.
2. Switch to that view and confirm the page in question is actually visible there.
3. If it isn’t, rebuild against All (unfiltered) and add the condition as a trigger rule. You can’t change an existing automation’s view scope afterward.

2. The page, or something it touches, is restricted

Automations won’t act on a page whose access is restricted — a platform rule, not a bug. If the action writes to a page marked Private or limited-Shared, or the creator lacks edit rights on a database it touches, it fails silently in most cases.

1. Open the Share menu on every page and database involved and confirm access isn’t restricted.
2. Check the creator’s current access level, not what they had when they built it — teamspace moves and departures quietly break this.
3. If the creator lost access, delete the automation and rebuild it under an account with full access to everything involved.

3. A guest built it, or nobody has full database access

Guests can never create database automations, even with full access to that database. Only paid-plan users with full database access can create, edit, or delete one — Free plan workspaces can build Slack notification automations and nothing else.

It fires, but the action does nothing

1. A third-party connection expired

If the action is Send Slack notification, Send mail to, or a webhook, the cause is often outside Notion. OAuth tokens for Slack and Gmail expire, get revoked on a password change, or get pulled by IT cleaning up approved apps — and Notion rarely flags it until the automation has failed repeatedly.

1. Go to Settings -> Connections and look for any integration flagged for reconnection.
2. Disconnect and fully reauthorize — a plain reconnect can leave stale token state behind.
3. Reopen the automation and re-select the target Slack channel or Gmail sender; it can still reference a stale connection object after the workspace fix.
4. On Google Workspace or Slack Enterprise, confirm with an admin that Notion’s OAuth app is still approved.

2. The formula in the action step failed silently

Notion says it plainly: a formula that doesn’t execute properly, or a failing webhook, may not notify you — unlike a missing database or expired connection, which usually pauses the automation and alerts you.

1. Check every step using a formula (the sigma icon) — a Define variables action or a formula inside a message field.
2. Test it against a page with a known expected output, watching for blank or malformed results.
3. A frequent culprit: dateAdd or similar date math run against an empty property, which Notion’s docs flag specifically. Build a filtered view that excludes empty-date pages and scope the automation to it.

3. The webhook hit its limit, or the endpoint changed

Per Notion’s webhook actions documentation, webhooks cap at five actions per automation, support POST only, and send database page properties, not page content. If a webhook step fails, Notion adds a visible exclamation mark and auto-pauses the automation until you manually resume it — one of the more visible failures here.

1. Check for the exclamation-mark indicator next to the automation.
2. Test the destination URL independently before assuming Notion is at fault.
3. On Enterprise plans, check whether an admin toggled off Allow webhooks in automations under Settings -> Connections — that kills every webhook action workspace-wide at once.

It worked fine, then stopped after a database change

1. The trigger property was renamed or deleted

An automation trigger binds to a specific property. Rename “Status” to “Stage,” or delete the select option it checks for, and the reference breaks — sometimes visibly in the panel, sometimes it just stops matching anything.

1. Open the automations panel and look for a broken or missing property reference.
2. Cross-check every property the automation depends on against the current schema.
3. Rebuild the trigger against the renamed property, or restore the deleted option.

2. A formula or rollup changed, and you expected that to trigger it

This trips up experienced builders more than beginners. Notion’s documented trigger types are Page added, Property edited, and a recurring Every {frequency} schedule — the full list. Formula and rollup properties aren’t on it, because they’re computed values, not properties a person edits directly. If your trigger is “when Priority Score is edited” and that score is a formula recalculating because a related task changed, that recalculation isn’t a manual edit, and it won’t fire.

1. Find the actual property being edited that causes the formula or rollup to update — usually a status or date field on a related page.
2. Move the trigger there instead of onto the computed property.

3. The database moved into a teamspace with different permissions

Same root cause as the permissions issue above, worth flagging separately because it’s a “stopped after a change” pattern: teams restructure databases into dedicated teamspaces constantly, and the creator often doesn’t carry the same access into the new location.

Slack notifications aren’t arriving

1. Only the original creator can edit it

Notion’s Slack documentation is explicit: once someone connects a Slack automation, only that person can edit it afterward. Everyone else with database access can see it exists but can’t modify it — if that person left, the automation is frozen until someone with full access rebuilds it.

1. Confirm who originally set up the Slack automation — the creator, not just who currently has database access.
2. If unavailable, delete the Slack action and recreate it under an active, fully-permissioned account.

2. It’s targeting a private DM

Slack automation notifications can only go to channels — private direct messages aren’t selectable as a target. If someone configured this expecting a DM, that’s why it never arrives.

3. The account lacks Full Access to the database

Setting up a database-level Slack notification requires Full Access to that database. View or Edit access lets someone see that a notification exists, not create or modify one.

It fires twice, or seems to loop

1. You’re relying on automations chaining, and they don’t

Database automations cannot trigger other database automations — a hard platform rule. If Automation A edits a property and Automation B triggers on that same edit, B will not fire from A’s action. What looks like duplicate or inconsistent firing is often “B never fires from A, but does fire when a human edits the same property,” producing confusing patterns across different pages. The one exception: a button action can trigger a database automation, though a recurring template or an automation creating a page cannot.

1. Map which automations write to properties that also serve as trigger conditions elsewhere.
2. Consolidate chained logic into one automation with multiple action steps.
3. For genuine multi-step conditional chaining, use Zapier or Make — that’s a real limit of the native builder.

2. Multiple “is edited” triggers in one automation

When an automation requires several is edited conditions to all be true, Notion’s docs confirm those edits must land within roughly a three-second window — the automation evaluates a burst of change events, not a final state. Edit Status, wait thirty seconds, edit Priority, and it won’t register.

1. Replace compound is edited conditions with one trigger property plus only when conditions checking the other fields’ current values.
2. Or use a more specific trigger than is edited, like is set to or contains — Notion’s own docs recommend this for exactly this case.

How to structure automations so they don’t break later

• Build from a service-style account with permanent full access. Ownership can’t be transferred — you’ll rebuild, not fix, if the creator leaves.
• Create a dedicated trigger property — a checkbox or select field like “Ready to Process” — for anything with more than one condition, instead of stacking is edited triggers.
• Scope automations to the unfiltered view unless the filter is genuinely part of the logic — filter-based scope is one of the least visible failure points.
• Never trigger off a formula or rollup property. Trigger on the underlying editable property that feeds it.
• Re-authenticate Slack and Gmail connections quarterly rather than waiting for silence to be noticed. Nothing in Notion proactively flags an expired token.
• Log what each automation does — a simple Notion page listing the property it watches and who built it saves hours when something breaks.

For the database mechanics behind all of this, see our Notion database guide covering views, relations, and rollups. If a formula-driven trigger is the root cause, our Notion Formulas 2.0 guide covers why formula properties behave differently from properties people edit directly. Setting automations up fresh instead of debugging? Start with our complete guide to Notion in 2026.

FAQ

Why does my automation fire for some pages but not others in the same database?

Almost always a view-scope mismatch: the automation is bound to a filtered view, and only pages matching that filter at the trigger moment can set it off. Rebuild against the unfiltered view, or add the condition as an explicit trigger rule.

Can a Notion automation trigger another automation?

No. Database automations cannot trigger other database automations — a recurring template, or one automation creating a page, will not set off a second automation watching that event. A person clicking a button is the one exception.

Do automations work on the Free plan?

Free plan users can create Slack notification automations only. Every other type — editing properties, adding pages, webhooks, email — requires a paid plan, and even then only users with full database access can create or edit them. Guests can never create one, on any plan.

Why didn’t Notion warn me my automation stopped working?

It depends on the failure. Notion generally notifies you when a referenced database or property goes missing, or a Slack/Gmail connection needs reauthentication. It often stays silent when a formula fails to execute or a webhook has an issue, sometimes for weeks, unless you check manually.