Notion
The Notion integration adds a new page to a Notion database every time someone submits your form. You choose the database and decide which Notion property each answer is written to, so responses land in a database you already work in rather than a new one.
Setting it up
- Open your form and go to the Connect tab
- Click Connect next to Notion
- Authorize FormGrid in Notion and select the pages and databases it may access
- Back in FormGrid, pick your Notion database
- Map each form field to a Notion property, then click Save
The integration stays off until you have picked a database and mapped at least one field.
Choosing a database
The integration writes to a database that already exists in your workspace. It does not create one, so make sure your target database is there before you connect, and select it in Notion’s page picker while authorizing.
Only databases you shared during that step appear in the dropdown. To add more later, click Connect next to Notion again and select them.
Mapping fields
Each row of the mapping connects one form field to one Notion property. Click Add property to map another field.
Only properties the answer can actually be written to are offered, so a file upload will not list a Number property. A Notion property can hold one form field, so a property already in use disappears from the other rows.
Alongside your form’s own fields you can also map:
- Submitted at, the time the response came in
- Response ID, the ID FormGrid gave the response
Fields you do not map are not sent to Notion.
Questions inside a repeat group
A question inside a repeat group is answered once per repetition, so the picker labels it (all repetitions). Every answer goes into the one property, separated by commas: Ada, Grace, Alan.
The mapping targets the question rather than any single repetition, because how many repetitions a response has is only known once it arrives: a repeat’s count can be a fixed number or an answer to an earlier question.
Note: since the answers are joined into one value, a repeated number or date no longer fits a Number or Date property and leaves it empty. Map those to a Text property instead.
Writing an answer to the page content
Every database row in Notion is a page, and that page has a body below its properties. Alongside the database’s properties, the mapping offers Page content as a target, which writes the answer into that body instead of into a column.
This suits a long answer better than a Text property does: the body has room for the whole thing, and a Text property gets truncated in table views. Each line of the answer becomes its own paragraph.
One field can be mapped to the page content, the same as for any property. If nothing is mapped to it, the page is created with an empty body.
What each field type can be mapped to
| Form field | Notion property |
|---|---|
| Short answer | Text, Title, Select, Multi-select, Status, Email, Phone, URL, Page content |
| Long answer | Text, Page content, Title |
| Email, Text, Title | |
| Phone | Phone, Text, Title |
| Number | Number, Text, Title |
| Rating, linear scale | Number, Text, Title, Select, Status |
| Multiple choice | Multi-select, Select, Status, Text, Title |
| Country | Multi-select, Select, Text, Title |
| Ranking | Text, Multi-select, Title |
| File upload, signature | Files & media, URL, Text |
| Hidden field | Text, Title, Select, Multi-select, Status, Number, Email, Phone, URL, Page content |
| Variable | Number, Text, Title, Select |
| Submitted at | Date, Text, Title |
| Response ID | Text, Title |
Person, Relation, Rollup and Formula properties can’t be mapped. The first two need IDs that only exist inside Notion, and the last two are values Notion calculates for itself.
Note: a Status property only accepts option names that already exist in it, because the Notion API can’t add new ones. Map to a Select property instead if you want new answers to create their own options.
How it works
Every time someone submits your form:
- FormGrid creates a new page in your database
- Each mapped answer is written to its property
- The page appears in Notion in near real-time
FormGrid only adds pages. It never renames, adds, or deletes properties in your database. Renaming a property in Notion keeps the mapping intact, but deleting one breaks it, so open Configure fields and map that field again.
Uploaded files
A file mapped to a Files & media property is handed to Notion, which downloads it and stores its own copy. The attachment then belongs to your workspace and keeps working even if the response is later deleted in FormGrid.
Notion applies its own size limit to imported files, which depends on your Notion plan. If a file is too large, or Notion cannot fetch it, the attachment falls back to a link to the file in FormGrid rather than being dropped. Those links stop working once the response is deleted.
Note: a URL or text column gets a link to the file in FormGrid, which never expires but only opens for someone signed in with access to the form. A text column lists every uploaded file, a URL column holds only the first.
Changing the mapping
Open the … menu next to the integration and choose Configure fields to switch databases or change the mapping at any time. Changes apply to new responses only.
If you add a question to your form after setting the integration up, map it there too. New questions are not mapped automatically.
Event log
Every write is logged. Open the … menu and choose Event log to see whether pages were created and what went wrong when they weren’t. Errors name the property they are about, so Status is expected to be multi_select tells you which mapping to fix.
Common causes are a deleted database or property, an option name a Status property doesn’t have, and access that was removed in Notion.
Disconnecting
Turn the integration off with its toggle to stop sending new responses. The pages already in your database stay where they are. Turn it back on to resume.