Yes. A Notion form can fill a relation property: add the relation to the database, and the Form view shows it as a question where respondents pick one or more pages from the related database. You can cap the number of picks. Two things trip people up, though: you can’t filter which pages appear in the picker, and on a public form you should test what an outside respondent actually sees.
How a relation question works in a Notion form
A relation question in a Notion form is a picker that lists pages from the related database. When someone submits, the new row is linked to the pages they chose, the same as if you had set the relation by hand.
Notion’s forms help says questions tied to multi-select, relation and people properties can have a maximum number of selections per response. That’s the main control you get.
Typical setups:
- Volunteers pick a shift page from a
Shiftsdatabase. - Each bug report links to a page in
Projects. - A client request form points at the client’s page in
Clients.
How to add a relation property to a Notion form
The relation has to exist on the database before the form can ask about it. Set it up in the desktop or web app:
- Open the database the form writes to. Add a property, search for
Relation, pick the database you want to link to, and clickAdd relation, as Notion’s relations help describes. - Optionally turn on
Show on [name of related database]to make it two-way, so each project page lists the reports linked to it. - Open the Form view. Add the relation property as a question if Notion didn’t add it already.
- In the question settings, set a maximum number of selections if people should pick only one.
- Submit a test response and check that the new row shows the link.
You can also limit the property itself. Notion’s relations help says you can set a relation to 1 page or No limit, and with 1 page people can only select one page. I’d set both for anything like a shift or a project, where two picks is always a mistake.
What you can’t do with a relation question
The picker shows the whole related database. Simone Smerilli’s guide to Notion forms puts it plainly: when you use a relation property as a question, “you can’t restrict the visible pages,” and you can’t filter the options based on conditions.
If your Projects database holds dozens of archived projects and a few live ones, respondents scroll past all of them. The fixes are blunt: move archived pages to a separate database, or keep a small “pickable” database just for the form.
The same guide notes that form submissions only create new pages. A form can’t edit an existing row, and it can’t create a page in the related database. If a client isn’t in Clients yet, they can’t pick themselves.
Test the relation picker on a public form
The relation picker needs a check before you post the link. Notion’s forms help says Anyone on the web with link lets people outside your workspace and people who don’t use Notion fill out the form, and that their responses are anonymous.
The same page doesn’t say what those outside respondents see in a relation picker, or whether the related database needs its own sharing. So test it the way a stranger would:
- Open the form link in a private browser window where you aren’t signed in to Notion.
- Click the relation question and check that the pages you expect are listed.
- Submit, then confirm the row in your database is linked to the right page.
Guests are a separate case. Notion says guests can only fill out a form if they have access to the database the form is connected to.
How form tools write to Notion relations
Third-party form tools fill relations through the Notion API, and the API has rules that explain most “the relation is empty” complaints. A relation value is an array of page IDs, and Notion’s property value reference says each page must belong to the data source the relation points at.
| API rule | What it means for a form |
|---|---|
| Share the related database with your connection too | If you only share the main database, relation values can come back empty |
| A page write replaces the relation | A tool that updates a row must read the existing links first, or it wipes them |
| 100 related pages per request | A request that sets more fails with validation_error, HTTP 400 (request limits) |
has_more: true past 25 references |
A page response lists 25 links; tools must page through the rest |
The first row is the one that bites. Notion’s reference says missing access “can leave relation values empty or make formula and rollup results incomplete.” If a form tool’s rows arrive with the relation blank, check that both databases are shared with that tool’s connection before you blame the form.
The 100-page cap applies per request. A relation can hold far more than 100 pages in total, and a form respondent picks a handful at most.
Counting responses per related page
Once responses link to pages, a rollup turns the links into numbers. Notion’s relations help says the Count all rollup counts the total number of values for all related pages.
Add a Count all rollup on Shifts and each shift page shows how many people signed up. Our volunteer sign up form guide builds exactly this, with a formula that compares the count to the spots available.
One warning from the same help page: duplicating a database with a two-way relation converts it to one-way. If you copy a template, check the relation before you rely on the count.
When the native relation question is enough
My take: the native relation question is good enough when the related database is short and public respondents can see it in your test. A shift list or a handful of event sessions is fine.
It gets awkward when you need filtering, different questions per answer, or respondents who pick a page and also answer follow-ups about it. Conditional logic in native forms is limited to the Business and Enterprise plans, and the picker can’t be filtered at all. Our list of Notion form limitations covers the rest.
nDBForms has a Notion relation question type that writes to the relation on the new row, reads your database properties to build matching fields, and doesn’t need respondents to have a Notion account. It keeps a copy of each response so it can retry a failed Notion write.
The limitation is the same as with any API tool: share the related database with the connection, or the links can’t be written. See how it maps fields on the nDBForms home page, and for a related pattern, the booking request form guide. If you’re still deciding who can open the form, read how to share a Notion form publicly.
FAQ
Can respondents pick only one related page?
Yes. Set a maximum number of selections on the relation question, or limit the relation property itself to 1 page in its settings.
Can I filter which pages show up in the relation picker?
Not in native Notion forms. The picker can’t be restricted to a subset of the related database, so keep that database small or split it.
Can a form create a new page in the related database?
A native Notion form only creates the new response row. It links that row to pages that already exist in the related database.
Why is the relation empty on rows created by a form tool?
A likely cause is that the related database isn’t shared with the tool’s Notion connection. Notion’s API docs say missing access can leave relation values empty.