Notion

What you get

• One Notion page per submission
• Field-level mapping: form field → database property
• Optional rich page body composed from answers
• Backfill existing submissions on demand
• Auto-recovery when database properties are renamed

Connect Notion

1. 1

   Open Form settings → Integrations

   Choose Notion from the list.

2. 2

   Connect and pick a database

   Pick an existing connected Notion account, or authorize a new one. You'll be redirected to Notion to grant access — formbase can only see databases you share during this step. Then choose the target database.

3. 3

   Map fields → properties

   Match each form field to a Notion property. Only compatible types are shown (see table below). You can also compose a rich page body using the template editor.

4. 4

   Finalize

   Use "Send test" to create a placeholder page and verify the connection. Enable "Export existing submissions" to backfill past responses. New submissions start syncing once you save.

Test event

The Finalize step and the integration detail panel both have a Send test button that creates a real page in your database. Text and title properties get [Question Title] placeholders, numbers get 0, emails get test@example.com, dates get the current timestamp, selects use the first available option, and files get a tiny placeholder image. Delete the test page after verifying.

Backfill existing submissions

After connecting, you can backfill past responses into the database. Pages are created one at a time (~3 per second to stay within Notion’s rate limits), with progress logged every 10 pages.

Property types

Metadata properties

Channel reads “Public link” or “Request”, and Request ID holds the id of the request a response answered, so a database that collects both share-link and request responses can tell them apart and join back to the request.

Repeating groups

If your form has a repeating group, the field picker gives you two ways to map it, depending on whether you want the whole group in one property or each member field broken out.

• The whole group → one property — pick the group itself to map every entry into a single Rich text (or Title) property. Each entry shows as a numbered, labeled row, like “1. Full name: Jane Appleseed, Age: 34, 2. Full name: Marcus Lee, Age: 29”.

• Each member field → its own property — pick a member field to give it a dedicated property. The values from every entry join with “ · “ (for example “Jane Appleseed · Marcus Lee”).

Member fields that no longer exist in the form but appear in past submissions stay mappable, so syncing never breaks for older responses.

Rich page body

Beyond property mapping, you can compose a rich page body with the template editor. Type @ to insert any form field value or metadata such as PDF Link — the editor shows them as mention chips that resolve at sync time.

Page bodies support paragraphs, bold, italic, underline, and links. Headings, lists, and images are not supported — they render as plain paragraphs. Text is automatically chunked at 2,000 characters per rich-text block (Notion’s limit).

Abandoned response events

If a respondent starts your form but doesn’t finish, formbase can still sync the partial data. On the Abandoned submissions step, set Send abandoned event after to 12 hours, 1 day, 3 days, or 1 week. An hourly sweep then creates a page with whatever the respondent filled in, using the same property mapping as a completed submission. Map the “Submission status” metadata field to a Status or Select property to tell them apart in Notion.

Only drafts from a share link are swept, and you can narrow it further with Required fields — the page is created only when at least one of the fields you pick was filled in.

Schema changes and auto-recovery

If you rename a property in Notion, formbase detects the change on the next submission and updates its mapping automatically. Properties are matched by their stable internal ID, so renames are transparent.

If you delete a property, formbase drops it from the mapping and keeps syncing the remaining fields. If a property’s type changes to something incompatible (e.g., number becomes select), the value may fail to sync — re-open the integration and re-map that field.

Troubleshooting

• Database not visible — Re-authorize and share the database with formbase during the Notion consent screen.

• Property mismatch — Mismatched types prevent syncing. Re-open the integration to see which fields need attention.

• Rate limits — Notion’s API has per-workspace limits. formbase retries automatically; backfills throttle to ~3 pages per second.

• Access revoked — If you remove formbase from Notion Settings → Connections, the integration stops with an error and the person who set it up receives an email. Reconnect to restore.

FAQ

Next steps