Typeform to Airtable Automation

A practical field guide from Automation Ace.

Typeform to Airtable Automation

Typeform collects beautifully structured data; Airtable stores and organizes it. Connecting the two turns your forms into a real operational database — with deduplication, routing, follow-up tasks, and team notifications built in. This guide covers how to build a Typeform → Airtable pipeline that goes beyond the basic "append a row" integration. For the form design principles that make this work cleanly, see form automation intake systems. For the Airtable database design that receives these responses, see using Airtable as an operations database.

Why the Basic Typeform → Airtable Integration Falls Short

Typeform has a native Airtable integration that creates a new record for each response. It works for simple logging but has no deduplication (the same person can submit three times and you get three records), no conditional logic (can't route different form answers to different Airtable tables), and no way to trigger follow-up actions like a confirmation email or a task creation. Zapier solves all three of these, and the Typeform → Airtable Zap is one of the most common and reliable integrations to build.

Mapping Typeform Question Types to Airtable Field Types

Before building the Zap, decide on your Airtable field types based on the Typeform question types you're collecting:

• Short text / Long text questions → Single line text or Long text field: maps directly, no transformation needed
• Multiple choice (one answer) → Single select field: map the question response directly; make sure your Airtable single-select options match the Typeform choice labels exactly (case-sensitive)
• Multiple choice (multiple answers) → Multiple select field: Typeform returns multi-select answers as a comma-separated string; Airtable's Zapier integration can accept this format for multiple select fields
• Email question → Email field: maps directly and Airtable validates the format
• Date question → Date field: add a Zapier Formatter step to convert the Typeform date format (YYYY-MM-DD) to your Airtable date format if needed
• File upload → URL field: Typeform passes a URL to the uploaded file; store it as a URL field in Airtable, not an Attachment field (Airtable's Zapier integration doesn't support adding attachments by URL via Zapier directly)

Building the Typeform → Airtable Zap with Deduplication

1. Trigger: Typeform: New Entry. Select your form and pull a test submission to populate the field list. Confirm all question fields you need are present.
2. Add Airtable: Search Records in your target table, searching where your Email field equals the email from the Typeform submission. This checks for an existing record.
3. Add a Filter by Zapier: only continue if the Airtable search returned no matching record (i.e., "Airtable Record ID is empty"). This prevents duplicate records when the same person submits the form twice.
4. Add any Formatter steps needed: capitalize name fields, reformat the date, trim whitespace from text fields.
5. Add Airtable: Create Record in your target table. Map each Typeform field to the corresponding Airtable field. Add a "Submitted At" date field mapped to the Typeform submission timestamp.
6. Add downstream actions: Gmail: Send Email for a confirmation to the respondent, Slack: Send Message to notify your team, or a second Airtable: Create Record to create a follow-up task linked to the new record.

Tip: For forms where you want to update an existing record (not create a new one), replace step 3's Filter with a Paths setup: Path A (record exists) → Airtable "Update Record" using the ID from the search; Path B (record doesn't exist) → Airtable "Create Record." This pattern is perfect for forms that people might fill out multiple times with updated information, like annual renewal surveys or updated contact preference forms.

Routing Submissions to Different Airtable Tables

If your Typeform has a logic-jump question like "Are you a new client or an existing client?" you can route submissions to different Airtable tables based on the answer. After your Filter/dedup step, add a Paths by Zapier with two branches: Path A (answer = "New Client") creates a record in your Leads table; Path B (answer = "Existing Client") searches for the existing client record by email and updates it. This single Typeform with branched routing replaces two separate forms and two separate workflows.

Using Typeform Hidden Fields for Source Tracking

Typeform supports hidden fields — URL parameters that are passed in the form URL and captured with the submission without the respondent seeing them. Add a hidden field called "source" and append it to your form URLs when sharing: yourform.typeform.com/to/FORMID#source=email-newsletter. In Zapier, map the hidden "source" field to a Source single-select field in Airtable. This gives you automatic UTM-style attribution on every form response without asking the respondent how they found you.