Add every inbound enquiry to your Notion leads database
Every business enquiry lands in your Notion Leads database as a page tagged New, with the company and inquiry type already filled in.
New submission on your "Contact us" form
Create a page in your Leads database with Name, Email and Company properties, and set Status to "New"
One-directional. A submission triggers the action — nothing is written back into your form.
An enquiry that sits in a shared inbox is not in the pipeline yet. This flow puts it there: the moment someone sends the form on your contact page, a page appears in your Notion Leads database with the company name already filled in and Status set to New.
Founders doing their own inbound sales reach for it first. Notion is already where the pipeline board lives, so a lead that arrives as a page can be dragged between stages, commented on, and linked to an account page without anyone retyping an email address.
Setting it up
- 1
Publish the business inquiry form and make Work Email and Company Name required. A lead page with an empty Company property is hard to prioritise later.
- 2
In Notion, open your Leads database and confirm it has a Name title, an Email property, a Company text property, and a Status select whose options include "New".
- 3
Add an Inquiry Type select to the Leads database with one option per answer in the form's "Type of Inquiry" question, spelled exactly as the answers are spelled.
- 4
In Zapier, choose formformform as the trigger app, pick New Submission, and select your business inquiry form. Send one real test enquiry so Zapier has sample data to map.
- 5
Add the Notion "Create Database Item" action and point it at the Leads database.
- 6
Map Full Name to the title property, Work Email to Email, and Company Name to Company.
- 7
Type "New" into the Status field as a fixed value rather than mapping it from the form. Every enquiry starts at the same stage.
- 8
Turn the Zap on, send a second enquiry from the live form, and check the new page opens in the right database view.
What maps where
Using the Business Inquiry Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Notion |
|---|---|
| Full Name | Name title of the new page in the Leads database |
| Work Email | Email property |
| Company Name | Company text property |
| Type of Inquiry | Inquiry Type select |
| Tell Us More | Page body, so the full message is readable inside the lead |
Variations worth knowing
The Type of Inquiry answer can drive a Zapier filter. Add a filter step that only continues when the answer is Partnership, then send those submissions to a Partners database instead. Everything else falls through to the Leads database as normal.
Map Company Size to a select property and Timeline to a second one. A sales view sorted by those two columns puts the large, urgent enquiries at the top of the board before a person has opened a single page.
If something isn't arriving
Status is not coming from the form, so it has to be typed into the Zap as a fixed value. Enter New in the Status field of the Create Database Item step, spelled and capitalised exactly as the option in Notion, then replay the failed task from Zapier's history.
The field was optional when that submission came in. Mark Company Name required in the form editor so the value is always present, and set a fallback such as Not given in the Zap so an older blank submission still creates a usable page.
Frequently asked questions
Can I keep editing the lead page in Notion without the form overwriting it?
Yes. The Zap only ever creates a page. Once it exists, Notion is the only thing writing to it, so notes, stage changes and assignees you add by hand stay put. Nothing travels back to the form either.
What happens to enquiries submitted while the Zap is switched off?
They are still stored in formformform and can be read or exported from the responses view, but Zapier will not create pages for them retroactively. Turn the Zap on before you publicise the form, and add any earlier enquiries to Notion by hand.
Do I need a separate Zap for each contact form?
One Zap watches one form. If you run a sales enquiry form and a support form, build two Zaps pointing at two different Notion databases. That keeps the Leads database free of questions that really belong with support.
Related automations
- Build your Notion guest list from event RSVPs
Every registration adds a guest to your Notion attendees database, with ticket type, party size and dietary notes attached.
- File survey feedback in your Notion research database
Each survey response becomes a tagged entry in your Notion research database, ready to group by theme during planning.
- Log new applicants in your Notion hiring pipeline
Each application arrives in your Notion candidates database as an Applied card, with the role and available start date already on it.
- Queue new orders in your Notion operations database
Each order request opens as a To do card in your Notion Orders database, with the product and quantity ready to pick.
- Turn problem reports into open tickets in Notion
Each problem report opens as a ticket in your Notion support board, already carrying a priority and the steps to reproduce.
- Add job applicants to a hiring pipeline
Each application becomes a Candidates record with role, start date and stage, ready to drag through a kanban view.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free