Airtable

Create an Airtable record for each form submission.

The Airtable integration creates one record per submission in a table you pick. You connect an Airtable account once per team with a personal access token; after that, any form can write to any base that token can access.

Connect your Airtable account

Connecting is a one-time step per team, and requires a team admin:

  1. In Airtable, create a personal access token at airtable.com/create/tokens with the scopes data.records:write and schema.bases:read, and grant it access to the base(s) you want submissions in.
  2. In Formiary, go to Settings → Integrations, click Connect Airtable account, and paste the token.

Formiary verifies the token with Airtable before saving it (stored encrypted; it's never shown again). Pasting a new token for the same Airtable account later — for example after rotating it — updates the existing connection.

Add the integration to a form

  1. Open the form and go to its Integrations tab.
  2. Click Add integration and choose Airtable.
  3. Pick the account (pre-selected if your team has exactly one), then the base and table to write to.
  4. Use Send test event to create a sample record and confirm the setup.

How fields map to columns

Values map to the table's columns by field name: a form field named email fills a column named email. Name your table's columns after your form's field names (case-sensitive). Values are typecast, so text values can fill select, number, and date columns where they parse cleanly.

A submission that includes a field with no matching column is rejected by Airtable and won't be retried — the delivery log shows the offending field name. Add the missing column (or rename it to match) and use the log's retry button.

Disconnecting

Deleting the credential from Settings → Integrations (admin only) deactivates attached form integrations but keeps their base/table settings, so you can reconnect later and reattach each integration from its settings page. If Airtable revokes the token (or it expires), deliveries stop with a clear error in the delivery log — reconnect with a fresh token and reattach.