To create a waitlist form in Notion, add a Form view to a database with an Email question, share it with Anyone on the web with link, and each signup arrives as a new row. Add a Unique ID property and every row gets a number you can use as a queue position. A Notion waitlist form can’t confirm emails or block duplicates, so you clean the list before launch.
What a Notion waitlist form needs
A waitlist form needs one database, one required Email question and a public share link. Everything else is optional.
You can build it on any plan. Notion’s forms help says all members on all Notion plans can create and use forms, and that you need Full access to the database the form is connected to.
Keep the questions short. The KickoffLabs pre-launch guide puts the entry form plainly: email address, maybe a first name, nothing else. Qualify people later, once they’re on the list.
I’d start with these properties:
| Property | Type | Shown on the form? |
|---|---|---|
| Email (or Title) | Yes, required | |
| First name | Text | Yes, optional |
| Queue number | ID | No, Notion fills it |
| Joined | Created time | No, Notion fills it |
| Status | Select: Waiting, Invited, Joined | No, you update it |
How to build the waitlist form step by step
The build takes a few minutes in the Notion desktop or web app. Forms can’t be created from the phone app.
- Create a database called
Waitlistwith the properties in the table above. - Select
+next to your view tabs and choose Form. Notion turns properties into questions. - Remove the questions you don’t want people to answer: Status, and anything internal.
- Mark Email as required.
- Open Form settings → Submit screen and write the Confirmation title and Confirmation body.
- Share the form with Anyone on the web with link and copy the link.
- Join your own waitlist once and check the new row.
The confirmation screen is your thank-you page. You can change the submit button’s color and text along with the confirmation title and body. Use the body to say what happens next: “You’re on the list. We’ll email you when invites open.”
Sharing the waitlist form publicly
Public sharing is what makes the form a waitlist. Notion says Anyone on the web with link lets people outside your workspace, and people who don’t use Notion, fill out the form.
The catch: respondents to a public form are automatically anonymous. Notion records the answers but not who sent them. Make Email optional and you’ll collect rows you can’t contact.
Paid plans can turn Notion branding off on a public form. We explain the three sharing modes in how to share a Notion form publicly, and why visitors don’t need an account in do you need a Notion account to fill out a Notion form.
Giving each signup a queue number
The Unique ID property is the closest thing Notion has to a “you’re number X in line” counter. Add an ID property and Notion numbers every row on its own.
Notion’s Unique ID help says IDs are created for each new and existing database item once the property is added. Numbers start at 1 and never change. Notion builds the prefix from the teamspace and database names, but you can edit it to something like WAIT-.
Two caveats for a waitlist:
- Deleted rows still use up numbers. Notion assigns IDs to every page, including deleted ones. Delete your test signups and the first real person won’t be number one.
- The respondent never sees their number. The confirmation body is fixed text, so the row’s ID can’t go there.
Automations cover the second gap. Notion’s automations help has a Page added trigger that runs when a new row arrives. The Send mail to action sends from your Gmail account, and Notion says those emails may take up to two minutes to arrive. Point it at the Email property and include the Queue number in the message.
This needs a paid plan. Free only allows Slack notification automations. The forms help also mentions an email copy of each submission, but that goes to you, not the person who signed up.
Single or double opt-in
A Notion form is single opt-in: the row exists as soon as someone presses submit. Nobody confirms that the email is real or theirs.
A DEV Community post on waitlist double opt-in, written by someone who runs a waitlist tool, says you pay “twenty to forty percent of raw signups at the front door.” What you get back is a list you can email at launch. The same post puts the confirm rate at 55-75% of signups within 48 hours, and says a position like #42 should only count confirmed people.
My take: for a small product launch, single opt-in in Notion is enough. Before the launch email, sort by Email, delete repeats and obvious fakes, and expect some bounces. If your list is mostly in the EU or you plan regular promotional email, the same post calls the confirm click cheap insurance, and Notion alone can’t do it.
Managing the list before launch
Treat the database as your launch tracker, not a mailing tool. Three views do most of the work:
- Board grouped by Status shows Waiting, Invited and Joined at a glance.
- Table sorted by Queue number gives you invite order for a first-come rollout.
- Sorting a second table by Email puts duplicates next to each other, since the form accepts repeat submissions.
Set Status to Invited as you send each batch. Hold off on a public signup count until it’s big enough. KickoffLabs notes that “Zero feels bad. Ten feels bad. But 500+ is enough to trigger FOMO.”
To stop new signups, set the form to No access. Notion closes the form and keeps your rows. It also warns that a form with a very high volume of responses might load slower.
Where the native Notion waitlist form falls short
The native form covers the basic job, but four limits show up quickly on a real waitlist:
- Duplicate emails go straight in.
- There’s no confirmation email or double opt-in.
- Referral links can’t be tracked. Referral waitlists give each person a unique link and move them up the queue for each friend who joins.
- Conditional logic, such as asking companies extra questions, is only on Notion’s Business and Enterprise plans.
Our full list of Notion form limitations covers the rest.
A separate form builder fixes some of this. nDBForms writes every submission as a new row in your Notion database, respondents don’t need a Notion account, and you get an email notification for each new signup plus a custom success screen. Conditional logic is on Pro and works with any Notion plan. It doesn’t do referral queues or double opt-in either, so the Unique ID approach above still applies. You can start from the nDBForms templates. For a waitlist that’s also a sales pipeline, see the Notion lead capture form guide.
FAQ
Do people need a Notion account to join the waitlist?
No. Share the form with Anyone on the web with link and people who don’t use Notion can submit it. Their responses are anonymous, so ask for an email.
Can a Notion form show someone their place in line?
Not on the confirmation screen. The confirmation title and body are fixed text. You can store a queue number with the Unique ID property and email it with an automation.
Does a Notion form block duplicate email signups?
No. Every submission becomes a new row, even if the email is already in the database. Sort by email before launch and remove repeats.
How do I close the waitlist?
Set the form’s access to No access. Notion stops accepting new responses and keeps the rows you already have.