To build a Notion lead capture form, create a Leads database with properties for contact details, the lead’s need, a Source and a Status, then add a Form view and share or embed it. Each submission lands as a new row, ready to sort into a pipeline. The part most setups miss is recording where each lead came from.
Set up a leads database for the Notion lead capture form
A Notion lead capture form writes into a database, and Notion’s help center says each question is connected to a property. So the leads database decides what you can capture, sort and report on.
Here’s a lean schema for a small team:
| Property | Notion type | Filled by |
|---|---|---|
| Name | Title | The lead |
| The lead | ||
| Company | Text | The lead |
| Need | Select | The lead |
| Timeline | Select | The lead |
| Source | Select | The lead |
| Lead ID | ID | Notion |
| Received | Created time | Notion |
| Stage | Status | You |
| Owner | Person | You or an automation |
According to Notion’s property reference, Created time records the timestamp of an item’s creation and isn’t editable. ID creates a unique number for each item that can’t be changed, which is handy when a teammate says a specific lead never got a reply. Status tracks progress with tags grouped as To-do, In Progress or Complete, so New, Contacted, Qualified, Won and Lost fit neatly.
Create the form and share it
You add the lead capture form as a view of the Leads database. Open the database, click + next to your views and pick Form. Notion’s forms guide notes that forms only work in the original database, so if Form is missing from the menu, you’re probably in a linked view.
Then:
- Add questions for Name, Email, Company, Need, Timeline and Source.
- Mark Name and Email as Required, so nobody can submit without them.
- Leave Stage, Owner, Lead ID and Received off the form.
- Turn on the email copy of each submission.
- Share with Anyone on the web with link and put the link on your site.
Respondents on a public link are automatically anonymous, so your Name and Email questions do all the identifying. The guide on sharing a Notion form publicly covers each sharing option.
How to record where each lead came from
Source tracking is where a Notion form falls short. Notion’s forms guide doesn’t mention hidden fields or reading values from the form’s URL, so a native form can’t silently pick up a campaign tag the way many marketing tools do.
There are three workarounds.
Ask for the source as a Select question
The simplest fix is a required Source question with options like Google search, LinkedIn, Referral, Newsletter and Other. It relies on memory, so expect some “Other” answers. Notion lets you set the sort order of Select options by dragging them, so put the likeliest answers first.
Tag the links that point to your form
Tag every link you share with campaign parameters, even when the form itself can’t read them. Google’s Analytics help says you should always use utm_source, utm_medium and utm_campaign, and their example looks like this:
https://www.example.com/?utm_source=summer-mailer&utm_medium=email&utm_campaign=summer-sale
Point that link at the page where your form is embedded. The values then appear in the Traffic acquisition report, so you can compare which campaigns send visitors, even if each Notion row doesn’t carry the tag. Google also notes that values are case sensitive, so utm_source=google and utm_source=Google count as two sources. Stick to lowercase.
Use one database with several forms
Notion’s forms guide says you can link multiple forms to a single database, keeping shared properties the same across forms. A “Book a demo” form and a “Get the price list” form can both feed Leads, each asking the questions that fit, so you see every lead in one pipeline.
My take: a small team needs nothing more than a required Source question and tagged links. Exact per-lead attribution only matters once you’re spending real money on ads.
Turn leads into a pipeline
A Board view grouped by Stage turns the Leads database into a sales pipeline. Notion’s views help describes the Board view as grouping items by a property, like a Kanban board you move cards across as they progress.
Two more views are worth adding:
- Hot leads: a table filtered to Timeline “This month” and Stage “New”. Filter groups can mix AND and OR rules, nested up to three layers deep.
- By source: the same table grouped by Source, to see which channel brings the leads that close.
Route new leads automatically
Notion’s database automations can assign and announce each lead as it arrives. A Page added trigger fires when a new page is added to the database.
The forms guide shows the routing pattern with a request form. Translated to leads:
- Trigger: Need is set to “Enterprise”.
- Action: set Owner to your sales lead.
- A second automation: when Owner is set, Send Slack notification to your sales channel, or Send mail to the owner.
Emails sent this way go from your Gmail account and can take up to two minutes to arrive. Automations need a paid Notion plan; the Free plan only allows Slack notification automations.
Common problems with Notion lead forms
Most lead form problems show up as missing data, not errors. Run one test submission from a private browser window before you share the link.
- No source on old leads. Add the Source question before launch. You can’t recover it later.
- Long forms. Every question is another property, and Notion allows up to 500 per database, but a lead form with more than a handful of questions asks a lot from a stranger.
- One form for every buyer. Branching questions need conditional logic, which Notion only offers on Business and Enterprise plans.
- Contact vs lead. If you only need a general inbox, a simpler Notion contact form is the better fit.
How nDBForms handles lead capture
nDBForms reads your Leads database properties, builds matching fields, and writes each submission as a new page. You embed the form on any page with an iframe, and each new submission can trigger an email notification.
On Pro, its analytics show views, starts, completions, drop-off by question and referrers, which answers “where did visitors come from” at the form level. The limitation: those referrers live in the nDBForms dashboard, not as a property on each Notion row, so keep the Source question if you want attribution in Notion itself. You can see how it works on the nDBForms homepage.
If you’re comparing tools, this roundup of the best Notion form builders covers the main options. The client intake form guide shows what to ask once a lead turns into a client.
FAQ
Can a Notion form capture UTM parameters?
Notion’s form documentation doesn’t mention hidden fields or reading values from the form URL. Ask for the source as a Select question, or use a form builder or your own handler that can read the URL.
Can I have several lead forms feeding one Notion database?
Yes. Notion’s forms guide says you can link multiple forms to a single database, keeping common properties across forms and customizing the rest.
How do I get notified about new leads in Notion?
Turn on the email copy of each submission in the form settings. On a paid plan, a database automation with a Page added trigger can also assign the lead and send a Slack message or email.
Do leads need a Notion account to fill out the form?
No. A form shared with anyone on the web with the link can be filled out by people who don’t use Notion. Their responses are anonymous, so ask for name and email.