Skip to content
All connectors
Airtable logo

Airtable

Analytics, databases & data platforms

Bring your business data together in Airtable, and act on it in the apps your team already uses.

16 ways to read, 12 ways to write, each write switched on by you.

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Airtable with Nexra

Connected, approved, proven.

The things teams do most with Airtable, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Add record commentcomments.createApproval by rule
  • Create fieldfields.createApproval by rule
  • List basesbases.listRead

Example flow

  1. Airtable · List basesbases.listDone
  2. Airtable · Add record commentcomments.createMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Airtable.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Airtable
  • Airtable's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

For developers

Technical detail

Airtable bases, tables, fields and views, records (search, batch create, update and upsert with typecast), comments, webhooks and enterprise users.

Airtable API docs
Source actions
16
Destination actions
12
Data types
12

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

bases2
  • Get baseSource

    A base's name, workspace and the token's permission level.

  • List basesSource

    Bases the token can access, with permission level.

comments3
  • Add record commentDestinationNot retried automaticallyApproval before production

    Adds a comment (or threaded reply) to a record.

  • List record commentsSource

    Comments on a record, newest first.

  • Update record commentDestinationProvider duplicate protectionApproval before production

    Edits the text of a comment created by the token owner.

enterprise accounts1
  • Get enterprise accountSource

    Enterprise account overview: workspaces, users, groups and email domains.

enterprise users1
  • Get enterprise userSource

    One user in an enterprise account with licence, state and security settings.

fields3
  • Create fieldDestinationNot retried automaticallyApproval before production

    Adds a field to a table.

  • List table fieldsSource

    Fields of one table with their types and type-specific options.

  • Update fieldDestinationProvider duplicate protectionApproval before production

    Renames a field or changes its description. Field types cannot be changed by API.

record batches3
  • Create records (batch)DestinationNot retried automaticallyApproval before production

    Creates up to 10 records in one request.

  • Update records (batch)DestinationProvider duplicate protectionApproval before production

    Updates supplied fields on up to 10 records. Omitted fields are unchanged.

  • Upsert records (batch)DestinationProvider duplicate protectionApproval before production

    Updates or creates up to 10 records matched on merge fields (performUpsert with fieldsToMergeOn).

records6
  • Create recordDestinationNot retried automaticallyApproval before production

    Creates a record.

  • Get recordSource

    A single record by ID.

  • List recordsSourceIncremental

    Records in a table or view, optionally modified since a time.

  • Search recordsSource

    Records matching an Airtable formula, sorted and limited to chosen fields. The formula is sent in the request body, not the URL.

  • Update recordDestinationProvider duplicate protectionApproval before production

    Updates supplied fields on a record. Omitted fields are unchanged.

  • Upsert recordDestinationProvider duplicate protectionApproval before production

    Updates the record matching the merge fields, or creates one (performUpsert with fieldsToMergeOn).

tables4
  • Create tableDestinationNot retried automaticallyApproval before production

    Creates a table with its fields. The first field becomes the primary field.

  • Get table schemaSource

    One table's fields (with types and options) and views.

  • List tables and fieldsSource

    Table schema for a base: fields with types and options, and views.

  • Update tableDestinationProvider duplicate protectionApproval before production

    Renames a table or changes its description.

user1
  • Get token userSource

    The user that owns the token (and, for OAuth tokens, its scopes).

views2
  • Get viewSource

    One view's name and type.

  • List viewsSource

    Views in a base with their type.

webhook payloads1
  • List webhook payloadsSourceIncremental

    Change payloads a webhook has recorded, from a transaction cursor. Use with the cursor from List webhooks.

webhooks1
  • List webhooksSource

    Webhooks registered on a base with their status and next payload cursor.

Access and limits

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.
Pagination
offset tokens for bases, records and comments; webhook payloads use a numeric cursor with mightHaveMore.
Provider events
Airtable webhooks (base change notifications with payload polling). Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Batch writes are limited to 10 records per request, as Airtable documents.
  • Record creation has no idempotency key; use Upsert with merge fields for repeat-safe writes.
  • Destructive record replacement (PUT) is not used; updates only change supplied fields.
  • Webhook creation, refresh and deletion are not implemented; webhooks and payloads are read-only.
  • Enterprise user lookups are by user ID only; Airtable takes email lookups in the query string, which Nexra does not send.
  • Base collaborators, shares and audit logs are not implemented.
  • Attachments are written as URL objects in field values; file uploads are not implemented.
  • Record, table, field, comment and webhook deletes are intentionally not implemented.
  • Incremental reads use LAST_MODIFIED_TIME() in filterByFormula, which ignores computed-field changes.

Developer reference

  1. Create the Airtable credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Airtable, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide

Machine-readable detail: GET /api/public/connect/connectors/airtable and the Connections API.