Stamp the finish date
Trigger: Status is set to Done. Actions: Edit property, Completed on set with the formula now(), then Send notification to the person in Requested by.
You've found the lightning icon. This page is the build itself: every trigger and action option, how to make an automation reach the related pages instead of only the one that changed, five recipes you can copy, and when a button beats an automation. If you want the overview first, our Notion automation page maps what runs inside Notion and what doesn't.
Creating and editing these needs a paid plan and full access to the database.
The automation runs against the view you're on. Pick an unfiltered view unless you want the filter to act as a condition, then give the automation a name you'll recognise in six months.
Page added fires on every new row. Property edited fires when one chosen property changes, and for select, person, number, text, name and relation properties you can narrow it to a kind of edit, such as Status is set to Done. Every {frequency} runs on a schedule you set with a time, start and end date, and timezone.
Watch for: with several triggers you choose any of these or all of these. All-of edits have to land within about three seconds of each other, so two people editing at different moments won't count. Use one specific trigger instead.
Stack as many as the job needs: Edit property on this database, Add page to or Edit pages in another database, Send notification to up to 20 people, Send mail to from a linked Gmail account, Send Slack notification to, Send webhook, and Define variables.
Watch for: a scheduled trigger can't use Edit property. If the weekly job has to change rows, have it notify someone or send a webhook instead.
Inside an action, type @ to insert a property, date, person or page, or use the ∑ button for a formula. Trigger page is the row that fired the automation, so Trigger page.Owner means that row's owner. These work in actions only, not in triggers, and formulas aren't allowed in Slack messages.
Click Create. From the same menu you can Edit, Pause or Delete it later. If it paused itself after an error, fix the cause, then switch Active back on.
Each one uses only built-in triggers and actions. Swap in your own property names.
Trigger: Status is set to Done. Actions: Edit property, Completed on set with the formula now(), then Send notification to the person in Requested by.
Trigger: the parent's Status is set to Done. Actions: Define variables with Trigger page.Sub-item, then Edit pages in the same database, limited to pages in that variable, setting Status to Done.
Trigger: Page added. Actions: Edit property, Assignee = the on-duty person, Status = New, and Send Slack notification to the team channel with the request title mentioned in the message.
Trigger: Stage is set to Won in a Deals database. Action: Add page to Projects, with the client name and owner filled from the trigger page using @ mentions.
Trigger: Every week, Monday 8am, on a view filtered to overdue items. Action: Send mail to the team lead, with a link to the overdue view mentioned in the message.
Both run the same kind of steps. The difference is what starts them.
Use a button when judgment is part of the step, like "approve and send to the client". Use an automation when the rule is mechanical and nobody should have to remember it.
This is the action that takes Notion outside Notion. It's simple on the Notion side and has a few hard edges.
Notion doesn't sign the request. A header key and value that your receiver checks is the only way to tell Notion's call from anyone else's.
In a database automation you pick which page properties go in the body. Page content isn't sent at all, and a database button can't choose properties.
There's no payload preview in Notion. Point it at a test URL, fire it once, and read the JSON before you build the receiver around it.
If the call fails, the automation shows an exclamation mark and pauses until someone resumes it. Changes made in the meantime don't fire, so the receiver can't assume it saw everything.
That's the cap, and every call is a POST. If one change has to reach more systems, send it once to a receiver that fans it out.
On Enterprise, workspace owners can switch webhooks in automations off for everyone under Settings, Connections.
Every trigger on this page watches a Notion database. That covers a lot of internal process, but the events that start most real work happen elsewhere: an invoice paid in the accounting system, a form filled on the website, a ticket escalated in the help desk. For those, something outside Notion has to watch the other system and write into Notion through the Notion API, and the automations here then take it from there.
That split is a good design. Let the native automations do the in-Notion steps they're good at, and keep the outside connection small: create or update the right page, then let Notion's own rules fan out. If the receiving side of a webhook or the matching of rows across Notion databases is where it gets fiddly, that's the part n-frames builds and runs, with a log of every call so a paused automation or a failed request gets noticed. For cases where a formula is enough, see Notion formulas.
Yes. Database automations watch a database for a new page, a property edit or a schedule and run one or more actions: editing properties, adding or editing pages in other databases, notifying people, sending Gmail, posting to Slack or sending a webhook. Buttons run the same kind of steps when someone clicks them.
A block (or a database property) that runs a fixed set of steps when clicked: insert blocks, add or edit pages, notify people, send mail or a webhook, show a confirmation, or open a page. It's manual by design, which suits steps where a person should decide the moment.
Partly. The Send webhook action can POST a page's properties to another app, and Gmail and Slack actions are built in. What Notion can't do is react to something that happens in another app, or read data back from it. That needs the Notion API or a connector.
No. Notion's automations come with a paid Notion plan and cost nothing per run, but they can only start from a change or a schedule in a Notion database. Zapier is a separate subscription priced by task volume, and its value is triggers that start in other apps. If the starting event is in Notion, use the native automation and save the tasks; if it starts in another app, you need Zapier, Make or a direct API connection.
Use Define variables with a mention of the trigger page's relation property, for example Trigger page.Sub-item, then an Edit pages in action limited to the pages in that variable. That's how a finished parent closes its sub-items.
Yes, with the Every {frequency} trigger: daily, weekly, monthly and so on, at a set time and timezone. It can notify, send mail, post to Slack, add pages or send a webhook, but it can't use Edit property, and it can't be combined with other triggers.
n-frames builds those. We write the API connection that turns the outside event into a Notion page or property change, set up the native automations that take over from there, and keep a log so a missed event is caught.