Fillo doesn't ship a direct Airtable destination yet. To create or update Airtable records, use the supported Zapier trigger or a signed webhook receiver.
Use Zapier (recommended)
- Create a Fillo token under Settings > Connections > Zapier.
- In Zapier, choose Fillo's new-or-updated response trigger.
- Select the published form and load a test response.
- Add an Airtable create-record or update-record action.
- Map stable raw field IDs, not only visible labels.
- Store the Fillo response ID in its own Airtable field.
- Publish the Zap and submit one production-shaped test.
If the form allows update-in-place responses, key an Airtable upsert or lookup step by the Fillo response ID. A plain create action produces another Airtable row on response.updated.
Suggested mapping
| Fillo value | Airtable field | Notes |
|---|---|---|
| Response ID | Single line text | Deduplication and update key |
| Submitted time | Date with time | Original creation time |
| Raw answer | Matching Airtable type | Use for filters and stable automation |
| Formatted answer | Single line or long text | Use when visible option labels matter |
| Verified respondent ID | Single line text | Keep separate from typed contact answers |
| File reference | URL or text | Fillo URLs require workspace authorization |
Use webhooks from your server
Point a Fillo webhook at a receiver you control. Verify X-Fillo-Signature against the raw body, commit the delivery by X-Fillo-Delivery-Id, then call Airtable from a background worker. This keeps the Airtable token on your server and gives you explicit retry and transformation behavior.
Don't point a Fillo webhook directly at an endpoint that expects Airtable's API request shape — Fillo sends its own signed response-event payload.
Limits and delivery
Fillo's Zapier trigger and signed webhooks are available on every plan. Zapier and Airtable apply their own task, automation, API, attachment, and record limits. Fillo's delivery-health dashboard can't see whether a later Airtable action inside Zapier succeeded.
Troubleshooting FAQ
Why did Airtable get two records?
The Zap may be creating on both response.created and response.updated, or a delivery may have retried. Upsert by Fillo response ID.
Why is a choice an internal ID?
Map formatted[fieldId] for the visible label and answers[fieldId] when stable IDs are more useful.
Why doesn't a file URL open publicly?
Fillo file links require authorized workspace access. Move the file through a server-authorized workflow, or store its provider reference — don't assume a public attachment URL.
Related
- Zapier: Configure the supported instant trigger and token.
- Webhooks: Build a signed, retry-safe server receiver.
- Delivery health and replay: See which first-party deliveries Fillo can monitor.