App capability page · Dataset v0.1.2
What can Zapier, Make and n8n natively do with Airtable?
What this page checks
The 8 canonical Airtable operations in Dataset v0.1.2 (3 triggers, 4 actions and 1 search/read operation), compared across Zapier, Make and n8n. Each cell answers one question: does the platform's own Airtable integration perform that exact job? API calls, generic webhooks, community nodes and custom code are recorded as workarounds, not as native support.
Native coverage
Zapier
7/8 TRUE1 FALSE · 0 UNKNOWN- Triggers: 2/3 native
- Actions: 4/4 native
- Search / read: 1/1 native
Make
8/8 TRUE0 FALSE · 0 UNKNOWN- Triggers: 3/3 native
- Actions: 4/4 native
- Search / read: 1/1 native
n8n
6/8 TRUE2 FALSE · 0 UNKNOWN- Triggers: 2/3 native
- Actions: 3/4 native
- Search / read: 1/1 native
Key differences
The platforms agree on 6 of 8 operations. They differ on these:
- New Form Response (trigger): native on Make; not native on Zapier and n8n.
- Bulk Update Records (action): native on Zapier and Make; not native on n8n.
Capability matrix
| Operation | Zapier | Make | n8n |
|---|---|---|---|
| New RecordTRIGGER | |||
| Record UpdatedTRIGGER | |||
| New Form ResponseTRIGGER | ✕ FALSEDelivery: Not applicableStatus: Not supportedNative record-created triggers do not prove that the event is specifically a form submission; source provenance is not equivalent.Verified 2026-10-05Source: Zapier evidence for Airtable New Form Response | ✓ TRUEDelivery: WebhookRequires: Airtable Team plan or higher required.Status: LimitedWatch Responses requires adding the Make webhook URL to the Airtable form Redirect-to-URL setting; Airtable sends only record_id.Verified 2026-10-05Source: Make evidence for Airtable New Form Response | ✕ FALSEDelivery: Not applicableStatus: Not supportedNative record-created triggers do not prove that the event is specifically a form submission; source provenance is not equivalent.Verified 2026-10-05Source: n8n evidence for Airtable New Form Response |
| Create RecordACTION | ✓ TRUEDelivery: Request responseVerified 2026-10-05Source: Zapier evidence for Airtable Create Record | ||
| Update RecordACTION | ✓ TRUEDelivery: Request responseVerified 2026-10-05Source: Zapier evidence for Airtable Update Record | ||
| Upsert RecordACTION | ✓ TRUEDelivery: Request responseVerified 2026-10-05Source: Zapier evidence for Airtable Upsert Record | ||
| Search RecordsSEARCH_READ | ✓ TRUEDelivery: Request responseVerified 2026-10-05Source: Zapier evidence for Airtable Search Records | ✓ TRUEDelivery: Request responseVerified 2026-10-05Source: Make evidence for Airtable Search Records | |
| Bulk Update RecordsACTION | ✓ TRUEDelivery: Request responseVerified 2026-10-05Source: Zapier evidence for Airtable Bulk Update Records | ✓ TRUEDelivery: Request responseVerified 2026-10-05Source: Make evidence for Airtable Bulk Update Records | ✕ FALSEDelivery: Not applicableStatus: Not supportedCurrent built-in Airtable node exposes single-record operations, not a native bulk-update operation comparable to Make/Zapier.Verified 2026-10-05Source: n8n evidence for Airtable Bulk Update Records |
Gaps and uncertainty
Of the 24 platform records on this page, 3 are not native.
Not native
- New Form Response on Zapier and n8n: Native record-created triggers do not prove that the event is specifically a form submission; source provenance is not equivalent.Evidence: zapier.com/apps/airtable/integrations, docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes…; evidence strength B_STRONG, checked 2026-10-05.
- Bulk Update Records on n8n: Current built-in Airtable node exposes single-record operations, not a native bulk-update operation comparable to Make/Zapier.Evidence: docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-bas…; evidence strength B_STRONG, checked 2026-10-05.
Requirements and limitations
Plan requirements on native records
- New Form Response on Make: Airtable Team plan or higher required.
Conditions on native records
- New Form Response on Make: Limited status. Watch Responses requires adding the Make webhook URL to the Airtable form Redirect-to-URL setting; Airtable sends only record_id.
How native triggers are delivered
- Zapier: not established by the evidence
- Make: webhook (event pushed to the platform) for New Form Response; not established by the evidence for New Record and Record Updated
- n8n: polling (checked on a schedule)
Native vs workaround
A FALSE record is a statement about the platform's own Airtable integration only; it is not a claim that the workflow is impossible. The fallback routes below are the ones the evidence records, and they are never counted as native.
- Zapier natively covers 7 of 8 operations. No fallback route is recorded for New Form Response.
- n8n natively covers 6 of 8 operations. The evidence records an API route for Bulk Update Records. No fallback route is recorded for New Form Response.
Sources and verification
Every record on this page cites an official platform source. Records were verified on 2026-10-05.
- Zapier: zapier.com/apps/airtable/integrationsIntegration directory · 8 of 8 operations · checked 2026-10-05
- Make: apps.make.com/airtable-modulesOperation documentation · 8 of 8 operations · checked 2026-10-05
- n8n: docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes…Operation documentation · 3 of 8 operations · checked 2026-10-05
- n8n: docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-bas…Operation documentation · 5 of 8 operations · checked 2026-10-05
Check an Airtable workflow
Pick the other app and step in the checker to see the end-to-end result on each platform.
Start a workflow with an Airtable triggerEnd a workflow with an Airtable action
How these records are classified: Ablelume methodology