To trigger a Notion automation when a form is submitted, open the form builder, select ••• → Automations, and use the Page added trigger. Each form response becomes a new page in the database, so that trigger fires once per submission. Then add actions such as Edit property, Send notification to or Send webhook. Most of this needs a paid Notion plan.
How a Notion form automation actually fires
A Notion form automation fires because every response is saved as a new database page. Notion has no trigger called “form submitted.” Instead, the database automations help lists three trigger types: Page added, Property edited and Every {frequency}.
Use Page added. Notion says it fires “when a new page is added to your database,” and a form response is a new page.
The forms help says actions can run “when you get a new response or when a question is answered a certain way.” The second case maps to the Property edited trigger, or to a condition on the answer’s property.
No form yet? Start with how to create a form in Notion.
Steps to set up the automation
You can build the automation from the form builder or from the database itself. Both paths create the same database automation.
- Open your form builder.
- Select ••• at the top, then Automations. From the database view, click ⚡ at the top, then New automation.
- Name the automation so teammates know what it does.
- Add a trigger and choose Page added.
- Add one or more actions.
- Select Create.
- Submit a test response from a private browser window and check that each action ran.
Don’t skip step 7. Notion warns that automations “may fail if they’re applied to a database view that filters out relevant entries.” Run one on a filtered view, send a response the filter hides, and nothing happens.
Which actions can run after a response?
Notion offers eight actions you can chain after the trigger.
| Action | What it does with a new response |
|---|---|
| Edit property | Sets a status, assignee or date on the response page |
| Add page to | Creates a page in another database |
| Edit pages in | Changes pages in another database |
| Send notification to | Alerts up to 20 workspace members, or people in a People property |
| Send mail to | Emails anyone from a linked Gmail account |
| Send webhook | POSTs selected properties to a URL |
| Send Slack notification to | Posts to a Slack channel |
| Define variables | Stores values to reuse in later actions |
Take a small design studio with a client intake form. On Page added, its automation sets Status to “New lead,” puts the founder in the Owner person property, and posts to #sales in Slack.
Email alerts get their own guide: Notion form email notifications.
Run actions only for certain answers
You can make an automation react to a specific answer instead of every response. Notion’s forms page says actions can run “when a question is answered a certain way.”
Add a Property edited trigger on the property behind that question. For select, number, text, person and relation properties, you pick which kinds of edits count. A support form could alert the on-call person only when Priority becomes “Urgent.”
Combining triggers with When all of these occur is fragile. Notion says those edits “need to happen within a small window of about three seconds.”
Showing or hiding questions inside the form is a different feature, limited to Business and Enterprise plans. The conditional logic guide covers it.
Send form responses to other apps with a webhook
The Send webhook action is how a Notion form automation reaches tools that Notion doesn’t connect to directly. The webhook actions help says it sends an HTTP POST request to the URL you enter, with the page properties you pick.
Its limits:
- POST only. “Webhooks only support POST request types.”
- Five per automation. “You can set up a maximum of five webhook actions per automation.”
- Properties only. Page contents can’t be sent.
- Preview elsewhere. Notion has no payload preview and suggests a site like webhook.site.
- Authentication is optional. The action doesn’t require it, though you can add custom headers.
- A failure pauses it. The automation stays paused until you resume it.
The pause is the dangerous one. For some errors, including webhook issues, Notion says “you may not be notified.” A broken endpoint can quietly stop every action in that automation.
Plan limits and other catches
Database automations need a paid Notion plan: “Database automations are available on paid plans on all platforms.”
The Free plan gets one exception. “Free Plan users can create Slack notification automations, but no other kinds of automations.” Free users can run automations that come inside templates, but can’t edit them.
Other rules from Notion’s docs:
- Guests can’t create database automations.
- Automations won’t act on pages with restricted access.
- Automations “can’t be triggered by other automations.” A page created in your database by another database automation won’t fire Page added.
- A user clicking a button that creates a page will fire it.
- A locked database stops automations.
My take: on a paid plan, keep the logic inside Notion. One trigger and a few actions are easier to debug than a chain of outside tools. Use a webhook only when the next step lives in another app, and check the automation’s status weekly, because a failed webhook pauses it without telling you.
What about forms that aren’t native Notion forms?
An outside form builder that writes each response into Notion through an integration still creates new pages, so hang follow-up actions on the same Page added automation.
nDBForms works this way: it creates a new row in your Notion database for each submission, and it can email you on every response. The catch, which applies to nDBForms too, is that Notion’s docs don’t say whether pages written through the API fire Page added in every case. Test with one real submission before you rely on it. If rows don’t show up at all, work through why a form isn’t syncing to Notion first.
Choosing between native forms and an outside builder? Read the limits of Notion forms.
FAQ
Is there a form submitted trigger in Notion?
Not by that name. Every Notion form response is a new page in the form’s database, so the Page added trigger is the one that fires on each submission.
Can I use Notion form automations on the Free plan?
Only partly. Notion says Free Plan users can create Slack notification automations but no other kinds. Database automations in general need a paid plan.
Can a Notion automation run only when a question has a certain answer?
Yes. Notion’s forms help says actions can run when you get a new response or when a question is answered a certain way. Add a Property edited trigger or a condition on the answer’s property.
Can a Notion form automation send data to another app?
Yes, with the Send webhook action on a paid plan. It sends an HTTP POST with the page properties you pick, up to five webhook actions per automation.
Why didn’t my Notion form automation fire?
Common causes are a view filter that hides the new response, restricted page access, a locked database, or the page being created by another automation, which never triggers a database automation.