A normal integration adds a new row for every submission. Record sync can instead change a record that already exists: a contact in HubSpot, a row in Airtable or a page in Notion. Open Integrations on your form and use Update existing records under the integration.
How a record is found
Record ids never come from the form. Formspring finds the record in one of two ways:
- It already linked a record to this respondent earlier.
- It looks up the lookup field (usually email) at the provider.
An existing record is only updated when the respondent verified that email address, for example through restricted access. A match on an address nobody verified stops with Needs review and changes nothing. If more than one record matches, nothing is changed either. If no record matches, a new one is created.
Before and after
Choose a record type, the lookup field, the field mapping and the fields that must never be written. Save, then choose Preview before and after. The preview shows what the latest submission would change, with values partly hidden. Record sync cannot be turned on until you have seen a preview, and any change to the mapping needs a new one.
Conflicts
Formspring remembers what it last wrote. If the record was changed at the provider since then, the conflict policy decides:
| Policy | What happens |
|---|---|
| Ask me (default) | Nothing is overwritten. You choose to keep the provider's value or use the form's. |
| Formspring wins | The form's value is written. |
| Provider wins | The provider's value is kept. |
| Newest change wins | Whichever side changed last. |
Filling a field that is empty at the provider never counts as a conflict. A staff edit to an answer in Formspring goes through exactly the same sync and the same policy as a respondent's edit.
Read-only fields and property types
Fields you list as read-only are never written, and record ids can never be a target. For Notion, choose Load property types to see each property and its type. Text, number, select, status, tags (multi-select), date, checkbox, link, email and phone number are written in their own type. Relations, rollups, formulas and other computed properties are shown as read-only and are never written. Tags are separated by commas or semicolons.
Linking a deal to a contact (HubSpot)
For HubSpot deals you can add a link: after the deal is saved, it is linked to the contact with the same email address. Only an address the respondent verified is used. If no contact matches, more than one matches, or the address was not verified, the deal is saved without a link and the reason is shown. A contact is never created or changed by a link.
When something goes wrong
| State | Meaning | What to do |
|---|---|---|
| Conflict | The record changed at the provider | Choose a value |
| Needs review | An unverified match, several matches, or the provider did not confirm a write | Check the record, then choose I checked it |
| Failed | The provider rejected the request | It is retried; you can also re-send |
| Reconnect needed | The provider no longer accepts the saved sign-in | Reconnect the integration; your data is unchanged |
A write that may or may not have reached the provider is never retried automatically, so a record is never changed twice. Use Re-send missed updates to send submissions that never reached the provider or failed. It runs in batches of 200 and leaves anything waiting for your decision untouched.
For developers
REST: /forms/{form}/webhooks/{webhook}/record-sync (abilities webhooks:read and webhooks:write). MCP: get_form_record_sync, save_form_record_sync, set_form_record_sync_state and resolve_form_record_sync_operation.
