Airtable
Read and write Airtable bases, table schemas, fields, records (create, update, upsert) and record comments.
Keep Airtable operational bases in sync with CRM, ERP and finance systems without hand-built scripts.
Source actions
5
Destination actions
9
Data types
5
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
bases
- List basesSource
Bases the token can access, with permission level.
comments
- Add record commentDestinationNot retried automatically
Adds a comment (or threaded reply) to a record.
- List record commentsSource
Comments on a record, newest first.
- Update record commentDestinationDuplicate protected
Edits the text of a comment created by the token owner.
fields
- Create fieldDestinationNot retried automatically
Adds a field to a table.
- Update fieldDestinationDuplicate protected
Renames a field or changes its description. Field types cannot be changed by API.
records
- Create recordDestinationNot retried automatically
Creates a record.
- Get recordSource
A single record by ID.
- List recordsSourceIncremental
Records in a table or view, optionally modified since a time.
- Update recordDestinationDuplicate protected
Updates supplied fields on a record. Omitted fields are unchanged.
- Upsert recordDestinationDuplicate protected
Updates the record matching the merge fields, or creates one (performUpsert with fieldsToMergeOn).
tables
- Create tableDestinationNot retried automatically
Creates a table with its fields. The first field becomes the primary field.
- List tables and fieldsSource
Table schema for a base: fields with types and options, and views.
- Update tableDestinationDuplicate protected
Renames a table or changes its description.
Authentication
Airtable personal access token
Plans and access
All Airtable plans; API call allowances depend on the workspace plan. Personal access tokens are limited to the scopes and bases chosen when created.
Test environment
Use a free workspace and a copy of a production base.
Rate limits
5 requests per second per base and 50 per second per token; HTTP 429 then a 30-second wait.
Provider events
Airtable webhooks (base change notifications with payload polling). Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Each write handles one record; batches of up to 10 records per request are not exposed.
- Record creation has no idempotency key; use Upsert with merge fields for repeat-safe writes.
- Attachments are written as URL objects in field values; file uploads are not implemented.
- Record, table and field deletes are not implemented.
- Incremental reads use LAST_MODIFIED_TIME() in filterByFormula, which ignores computed-field changes.