Send form responses to an Airtable base
New responses land as new records in an Airtable base, one field per question, ready for the views and automations already built around it.
Set up in three steps.
- 1
Create a personal access token
In Airtable, generate a personal access token scoped to the base you want to write into.
- 2
Copy the base ID
Find the base ID from the base’s API documentation page or its URL.
- 3
Save the connection
Paste both into the form’s Airtable card in the Integrations tab. Every new response becomes a new record from that point on.
What teams do with it.
- Feed a hiring, intake, or request pipeline that already lives in an Airtable base.
- Trigger existing Airtable automations off a newly created record.
- Keep responses in the same base as related records they need to link to.
- Give non-technical teammates Airtable’s views over form data without a CSV import step.
What Airtable receives
Each response writes as one record, with question labels matched to field names in the base. As with Notion, fields that don’t already exist on the base are not created automatically, so set up the columns you want mapped before connecting.
Questions, answered.
New responses land as new records in an Airtable base, one field per question, ready for the views and automations already built around it.
1. Create a personal access token: In Airtable, generate a personal access token scoped to the base you want to write into. 2. Copy the base ID: Find the base ID from the base’s API documentation page or its URL. 3. Save the connection: Paste both into the form’s Airtable card in the Integrations tab. Every new response becomes a new record from that point on.
Each response writes as one record, with question labels matched to field names in the base. As with Notion, fields that don’t already exist on the base are not created automatically, so set up the columns you want mapped before connecting.