All docs

Notion

Updated . 3 min read.

Create a new page in a Notion database for each submission. Formspring calls Notion’s API with your internal integration token-no middleware required.

What you need

  • A Notion internal integration and the database shared with that integration.
  • The database ID from the Notion URL.

What you configure

  • Integration token (secret_...) - encrypted at rest.
  • Database ID.
  • Title field - which form field becomes the page title (defaults to name; falls back to form name + id if empty).
  • Title column name - must match your database’s title property (often Name).
  • Field map (optional) - JSON like {"email":"Email","message":"Notes"} mapping form keys to rich_text property names. Columns must already exist with compatible types.

Steps

  1. In Notion, create the integration, copy the secret, and connect it to your database.
  2. In Formspring, open your form → Integrations → Notion → fill token, database id, title settings, optional map → Save.
  3. Submit a test; confirm a row appears and Deliveries is 2xx.

When a property changes

Manage connection can check your mapping against the database. If a mapped property was renamed or deleted, only that mapping is paused and every other property keeps arriving. Restore the property (or change the mapping) and resume it; you do not need to enter the token again. If the property is gone for good, choose Accept the change to remove that one mapping, or Pause field to stop sending a property without removing it.

Reading changes from Notion

On Manage connection, Read changes now reads only the pages edited since the last read. If a read is interrupted it continues from where it stopped, and the result (how many pages changed and how many are linked to Formspring records) appears in the connection's health timeline.

This is a read-only sync unless you turn on Apply changes made at the provider to the submission for a record sync of the form: Formspring counts what changed and writes nothing back to your submissions. With that option on, an edit made in Notion to a linked page is applied to the submission as a new revision. A field you also changed in Formspring is never overwritten silently; it follows the conflict rule you chose, or waits under Needs a decision.

If Notion stops accepting the position Formspring saved, the connection is not marked as broken. The pages are read once from the start, each page is handled once, and the connection panel says so until the read finishes.

Notion does not offer change notifications for each connection, so Formspring reads on a schedule instead.

Tips

  • A 404 from Notion almost always means the database was not shared with the integration.
  • The built-in path targets title and rich_text properties; use automations for selects, relations, or rollups.

More help