Notion Forms are a Game Changer

Notion Forms lets users create and share a database-backed form in minutes—then automatically routes submissions into database properties—without making the underlying database public. The workflow is fast enough to treat forms as a lightweight input layer for ideas, questions, and internal requests, while still keeping the data model and permissions inside Notion.

A public form can be created from a new page by typing “/form” in Notion. Once shared as “anyone on the web with the link,” the form opens in a browser and submissions appear under “responses.” Those responses are automatically mapped to database properties: a text answer lands in a title-like field, multiple-choice answers become select properties, and the system records the respondent as “Anonymous” when no account is involved. Notion Forms can also be embedded into public Notion Pages (including Notion Sites), so a portfolio or landing page can collect submissions directly at the bottom of the page.

The practical payoff comes from using forms as an interface to existing databases. For an “audience ideas” database, the creator builds a public “video suggestion form” that writes new pages into the database. Instead of relying only on auto-generated questions from existing properties, the form builder can create custom fields: a required “first name,” a required “type of suggestion” (video topic, question, template suggestion, or other), and an optional email field for newsletter signups. A key nuance is that the database itself can remain private while the form link is public—so the builder is publishable even when the responses live in a non-public workspace.

For internal workflows, a second form is created directly from a source database in the workspace. This internal “topic suggestion form” is shared to “anyone on the web with the link” but is intended for team members logged into the workspace. It demonstrates advanced binding: form questions can map to properties like description, and can also bind to relation properties, producing a dropdown of related pages (e.g., selecting which channel a content idea belongs to). It can even include file uploads via a files/media property, letting teammates attach an image with the submission.

Sharing the external form is made easier with short links. Since form URLs can be long and Notion doesn’t offer custom slugs for these form links, the creator uses a third-party short-link service (dub.co) and a Raycast extension to generate a branded, shareable URL.

Finally, the submissions can be turned into actionable work using Notion automations and button properties. A queue view is set up with statuses like “not reviewed,” “approved,” and “rejected.” Clicking an “approve” button updates the submission status and creates a new page in the content ideas database, using the automation formula builder to pull context from the button-triggering page (e.g., copying the submission text into the new page’s name/description and setting the new page’s status to “idea”).

The main limitations are practical: hidden fields with default values can’t be created for form submissions, and form submissions can’t be distinguished from pages created through other methods—making it harder to target automations specifically to form inputs. There’s also no current way to embed Notion Forms on external websites (like Framer or WordPress), only on Notion pages. The creator compares alternatives such as Tally, uForm, Typeform, and Google Forms, but positions Notion Forms as the simplest option when the goal is automation and database integration inside Notion.