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.
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.
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.
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.
Member fields that no longer exist in the form but appear in past submissions stay mappable, so syncing never breaks for older responses.
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).
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.
> ℹ️ **Pro feature** >> Abandoned response delivery requires a Pro or Business plan. The core Notion integration is available on all plans. See{' '} > plans & pricing. >
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.
No. Create the database in Notion first, then share it with formbase during authorization.
The next submission fails with a "not found" error and the integration stops. The database is fixed when the integration is created, so delete this integration and create a new one against the new database.
Yes. Notion accounts are connected at the workspace level. Any member can use any connected account when setting up an integration.
Yes. Authorize additional Notion workspaces during new integration setups. Each form picks which account to use.
No. But if you remove formbase from Notion Settings → Connections, the token is revoked and you'll need to reconnect.
Both appear as pages in the same database. The "Submission status" property reads "Completed", "Partial", or "Updated" when a respondent edited an earlier answer — use Notion's filtered views to separate them.
Go to Form settings → Integrations → Notion and delete the integration. To also revoke formbase's access to your Notion workspace, go to Notion Settings → Connections and remove formbase.