Notion database automations stop for boring reasons: the page no longer matches the view the automation watches, someone lost Full access, a Slack/Gmail connection expired, or you are on Free trying to edit a non-Slack automation. Notion will not always toast an error.
I re-checked Notion’s database automations help on October 13, 2026. Paid plan users with Full access create/edit/delete automations. Free users can create Slack notification automations only, and can use (not edit) automations that arrive via templates. Slack channel notifications on edit require Plus+. Plus is $10/user/month; Business $20 (pricing).
Critical platform rules (read once)
- Automations do not trigger other automations (no chains).
- Button actions can trigger a database automation.
- Recurring template inserts do not trigger database automations.
- Pages outside the automation’s view filter never fire it.
- Restricted pages the automation cannot access are skipped.
- Multi-trigger “all must happen” windows are about three seconds — prefer one precise trigger.
Symptom: never fires
- View filter — open the automation; confirm the view. A status the filter excludes will never match.
- Permissions — builder needs Full access; destination pages/databases must be reachable.
- Wrong trigger — property renamed/deleted; recurring trigger paired incorrectly.
- Free plan — you cannot maintain non-Slack automations; upgrade or recreate on a paid seat.
Symptom: fires but nothing changes
- Slack/Gmail token — reconnect; Slack edits are creator-only.
- Action formula/variable failed — simplify the action.
- Webhook endpoint changed or rate-limited.
- Trying to chain automations — use a button or a single multi-action automation instead.
Symptom: died after a database change
- Trigger property renamed — reopen and rebind.
- You expected a formula/rollup change to trigger — use a writable property as the trigger.
- Database moved to a teamspace with tighter permissions.
Symptom: Slack quiet
- Only the original creator can edit Slack automations — that person must fix it.
- Private channels / DM targets the bot cannot see.
- Creator lost Full access to the database.
- Plan: Slack channel notification actions need Plus+.
Prevention
- Name automations with the outcome and owner (
Notify CS on Escalated — Maya). - Prefer Status equals X triggers over vague “any property edit.”
- Keep a cheap “heartbeat” row in a staging database when you change schema.
- Document who owns Slack-connected automations before that person leaves.
- For deeper database design, see the Notion database guide and Notion pricing.
Common questions
Can Free Notion users build automations?
Only Slack notification automations (create). Other types need a paid plan. Template automations can run but Free users cannot edit them.
Why didn’t creating a page from another automation fire mine?
Notion blocks automation-to-automation triggers. Use a button or have a human/API create the page.
Who can edit a Slack automation?
The creator. If they left, recreate the automation with a shared owner account.
Do button properties help?
Yes — buttons can run actions and can trigger database automations when they create/edit pages in ways Notion allows.
Verified against notion.so/help/database-automations and notion.so/pricing on October 13, 2026.
Sponsored
