Menu

Mattering Automations Airtable integration

Connect Airtable to Mattering Automations: bases, records with formulas and views, schema, comments, and webhook management as workflow steps, authenticated with an Airtable Personal Access Token.

The Mattering Automations Airtable integration adds Airtable to your automation canvas: list bases and read their schemas, list records with formula filters, views, and sorts, create, update, upsert, and delete records in batches, manage tables and fields, work with record comments, and manage webhook subscriptions.

Setup takes a few minutes: create a Personal Access Token in Airtable's Builder Hub, attach it as a credential in Mattering, and test the connection. This guide walks through each step and ends with the full node reference.

Two things are worth knowing before you start. Airtable tokens carry both scopes and a per-base access list, so most permission errors are token configuration rather than bugs. And record updates here are PATCH-only by design: Airtable's replace-style update, which silently clears fields you omit, is deliberately not shipped.

Before you start

  • An Airtable account with at least one base.
  • Access to Airtable's Builder Hub (airtable.com/create/tokens) to create a Personal Access Token.
  • A Mattering workspace with access to the Automations app.
  • For schema-write flows: a scratch base to test against first, because the API cannot delete tables or fields it creates.

Create an Airtable Personal Access Token

Mattering authenticates to Airtable with a Personal Access Token, sent as a bearer credential on every request. Airtable retired API keys in 2024; PATs are the current mechanism. A token is defined by two lists chosen at creation: the scopes it may exercise, and the bases or workspaces it may touch.

Open Airtable's Builder Hub at airtable.com/create/tokens and create a token.
Add the scopes your automations need: data.records:read and data.records:write for record flows, schema.bases:read for listing bases and schemas, schema.bases:write for table and field management, plus webhook:manage for the webhook nodes.
Grant the token access to the specific bases or workspaces your automations will touch.
Copy the token.
Both lists matter. A token with the right scopes but no access to a base, or access to a base but a missing scope, returns 403s that look like permission bugs. The connection test only proves the token is valid, not that it can reach your data, because it uses an endpoint that needs no scopes at all.

Connect Airtable to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Airtable from the list.
Click Create new credential, paste your Personal Access Token, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection: Mattering calls Airtable's who-am-i endpoint and confirms the token authenticates.
Click Connect. All 22 Airtable nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: an Airtable section should list the query and action nodes. Drop Airtable: List Bases onto the canvas and run a test step. It is a safe read; a successful response lists the bases the token was granted, with the base ids every record node asks for. If it returns an empty list or a 403 while the connection test passed, the token's scope or base grants need editing in the Builder Hub.

Next, run Airtable: Get Base Schema with a base id from the first step: it returns every table and field, including the table ids and field names that record operations use. Then Airtable: List Records against any table confirms data access end to end. Everything in this path is read-only.

Node reference

22 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 8

Airtable: Get Base Schema

airtable_get_base_schema

Return the full schema of a base: every table with its id, name, primary field, fields (id, name, type, options) and views. This is where table ids (tblXXX) and field ids (fldXXX) come from. Requires the schema.bases:read scope.

Airtable: Get Record

airtable_get_record

Fetch one record by id, returning its fields and created time. Empty cell values (empty string, false, empty array) are omitted from the response. Attachment cells return URL objects whose URLs expire 2 hours after the response, so download promptly rather than storing the URL. Requires the data.records:read scope.

Airtable: List Bases

airtable_list_bases

List every base the token can access, with the permission level on each. This is where the base ids (appXXX) used by every other Airtable node come from. Returns up to 1,000 bases per page with an offset cursor. Requires the schema.bases:read scope; a base missing from the token's resource list will not appear.

Airtable: List Comments

airtable_list_comments

List the comments on a record, newest first, with author, text, reactions and thread parent ids. Requires the data.recordComments:read scope.

Airtable: List Records

airtable_list_records

List records from a table, with filtering (filterByFormula), a view, sorting, field selection and offset pagination (up to 100 records per page; data.offset carries the cursor for the next page). A read despite the POST: this is Airtable's documented POST /listRecords variant of the list endpoint, used so long formulas and sort arrays travel in the JSON body instead of the query string. Requires the data.records:read scope. Airtable allows 5 requests per second per base; a 429 means wait 30 seconds.

Airtable: List Webhook Payloads

airtable_list_webhook_payloads

Fetch the change payloads a webhook has accumulated, in transaction order, with a cursor for the next call and a mightHaveMore flag. Side effect worth knowing: calling this on an active webhook resets its 7-day expiration clock. Requires the webhook:manage scope.

Airtable: List Webhooks

airtable_list_webhooks

List the webhooks registered on a base with their specification, notification URL, enabled state, expiration time and payload cursor. Requires the webhook:manage scope.

Airtable: Who Am I

airtable_whoami

Return the user id behind the token (plus email when the token has the user.email:read scope). Requires NO scopes, so it is the cleanest credential health check: 200 means the token is valid, 401 means it is not. Note a 200 here does not prove data access; scopes and the token's base list gate every other node.

Action nodes 14

Airtable: Create Comment

airtable_create_comment

Post a comment on a record, optionally as a threaded reply. Mention a collaborator inline with @[usrXXX] and Airtable notifies them. Requires the data.recordComments:write scope and base commenter access.

Airtable: Create Field

airtable_create_field

Add a new field (column) to a table. Additive, but note the Web API has NO delete-field endpoint, so this cannot be undone from an automation; removal is manual in the Airtable UI. Requires the schema.bases:write scope and base creator access.

Airtable: Create Records

airtable_create_records

Create up to 10 records in one call. Each record is a {"fields": {...}} object keyed by field name or id. To attach a file, set an attachment field to [{"url": "https://example.com/file.pdf"}] and Airtable fetches it server-side. Requires the data.records:write scope and base editor access. Airtable allows 5 requests per second per base; a 429 means wait 30 seconds.

Airtable: Create Table

airtable_create_table

Create a new table in a base, defining its fields up front (the first field becomes the primary field). Additive, but note the Web API has NO delete-table endpoint, so this cannot be undone from an automation; removal is manual in the Airtable UI. Requires the schema.bases:write scope and base creator access.

Airtable: Create Webhook

airtable_create_webhook

Register a webhook on a base. Management only: this does NOT create an inbound trigger on this platform; notificationUrl must be an endpoint you operate (or omit it and poll List Webhook Payloads). PAT-created webhooks expire after 7 days unless refreshed. The response's macSecretBase64 (for verifying pings) is shown ONLY here and cannot be retrieved again, so persist it immediately. Limit 10 webhooks per base. Requires the webhook:manage scope and base creator access.

Airtable: Delete Comment

airtable_delete_comment

Permanently delete a comment from a record. DESTRUCTIVE: there is no undo. Non-admin tokens can only delete comments their own user created. Requires the data.recordComments:write scope and base commenter access.

Airtable: Delete Records

airtable_delete_records

Permanently delete up to 10 records by id in one call. DESTRUCTIVE: deleted records are only recoverable through Airtable's own trash/snapshot features, not through the API. A single id in the list deletes one record. Requires the data.records:write scope and base editor access.

Airtable: Delete Webhook

airtable_delete_webhook

Permanently delete a webhook from a base. DESTRUCTIVE: the webhook, its undelivered payloads and its MAC secret are gone; a replacement gets a new id and secret. Requires the webhook:manage scope and base creator access.

Airtable: Refresh Webhook

airtable_refresh_webhook

Extend an active webhook's life by 7 days from now and return the new expiration time. Schedule this on a cadence shorter than 7 days to keep a webhook alive indefinitely. Requires the webhook:manage scope and base creator access.

Airtable: Update Comment

airtable_update_comment

Edit a comment's text. The API only lets a token edit comments its own user created. Requires the data.recordComments:write scope and base commenter access.

Airtable: Update Field

airtable_update_field

Update a field's name, description, or type-specific options (send at least one). The field's TYPE cannot be changed through the API. Requires the schema.bases:write scope and base creator access.

Airtable: Update Records

airtable_update_records

Partially update up to 10 records in one call: only the fields you send change, everything else is left alone (PATCH). Clear a single field by sending null for it. Airtable's PUT variant, which wipes every field you do NOT send, is deliberately not shipped. Requires the data.records:write scope and base editor access. Airtable allows 5 requests per second per base; a 429 means wait 30 seconds.

Airtable: Update Table

airtable_update_table

Rename a table or change its description (send at least one of the two). Returns the full updated table schema. Requires the schema.bases:write scope and base creator access.

Airtable: Upsert Records

airtable_upsert_records

Update-or-create up to 10 records keyed on your own external id fields (Airtable's documented performUpsert mode of the PATCH update endpoint). Records without an id are matched on fieldsToMergeOn: zero matches creates, one match updates, several matches fails the request. The response lists createdRecords and updatedRecords ids separately. Requires the data.records:write scope and base editor access. Airtable allows 5 requests per second per base; a 429 means wait 30 seconds.

Using the integration

On the automation canvas

Airtable nodes chain with every other node: a scheduled Airtable: List Records sweep with a filterByFormula can open tasks in Mattering Productivity for rows needing attention, completed work can flow back through Airtable: Update Records, and Airtable: Create Comment leaves the trail on the record itself.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can read schemas, query records with formulas, and file new rows through the same nodes your workflows use. Airtable: Get Base Schema is the natural first call for an assistant: one read and it knows the shape of everything in the base.

Batch-first record operations

Airtable: Create Records, Airtable: Update Records, Airtable: Upsert Records, and Airtable: Delete Records each handle up to 10 records per call, per Airtable's API. Updates are PATCH semantics: only the fields you send change, and clearing a field is an explicit null, never an accident of omission. Upsert matches on the merge fields you name and reports which records were created versus updated, which makes recurring syncs idempotent.

Formulas, views, and sorts on reads

Airtable: List Records accepts filterByFormula, a view name, sort rules, field selection, and pagination, and posts through Airtable's documented body variant so complex formulas travel intact. The practical pattern: express the condition once as a formula, or maintain it as a view in Airtable and just name the view.

Schema writes are one-way

Airtable: Create Table, Airtable: Create Field, Airtable: Update Table, and Airtable: Update Field manage base structure from the canvas, but the Web API has no delete for tables or fields, so what a workflow creates only a person in the Airtable UI can remove. Test provisioning flows against a scratch base, and treat schema creation as deliberate, not incidental.

Webhooks and attachments, honestly

The webhook nodes (Airtable: Create Webhook, Airtable: List Webhooks, Airtable: List Webhook Payloads, Airtable: Refresh Webhook, Airtable: Delete Webhook) manage subscriptions and read change payloads; there is no inbound Airtable trigger, and subscriptions expire unless refreshed. Attachments travel as URLs in both directions: download URLs in responses are valid for about two hours, and uploads happen by giving Airtable a public URL in a field value. Raw file bytes never pass through workflows.

Troubleshooting

Test Connection fails with a 401
The token is invalid, was revoked, or picked up stray whitespace when pasted. Create a fresh Personal Access Token in the Builder Hub and update the credential on the connector.
Test Connection passes but nodes return 403
The defining Airtable failure mode. The connection test uses the scope-free who-am-i endpoint, so it proves token validity only. A 403 on a real node means the token lacks the needed scope (for example data.records:write) or was never granted the base it is touching. Edit the token's scopes and base access in the Builder Hub; no connector change needed.
List Bases returns an empty list
The token is valid but was granted no bases. Token base access is chosen at creation and editable afterward in the Builder Hub: add the bases or workspaces your automations need.
A batch write fails partway or rejects the whole call
Batch calls are limited to 10 records each, and Airtable validates the batch as a unit: one malformed record can reject the call. Check field names against Airtable: Get Base Schema (they are case-sensitive), confirm computed fields are not being written, and split large volumes into successive 10-record calls.
Calls start failing with 429
Airtable's rate limit is 5 requests per second per base, and after a 429 the API expects a roughly 30-second pause before resuming. Space out scheduled sweeps, batch records instead of writing one at a time, and let the workflow wait and retry rather than hammering.
An attachment URL from a record no longer works
Attachment download URLs expire after about two hours by design. Use them promptly in the same workflow run, or re-fetch the record with Airtable: Get Record when the file is needed again. For durable storage, copy the file to your own storage while the URL is fresh.
A webhook stopped delivering payloads
Airtable webhooks expire unless refreshed. Run Airtable: Refresh Webhook on a schedule to keep a subscription alive, and use Airtable: List Webhooks to check expiration times. Missed changes are recoverable: Airtable: List Webhook Payloads returns the queued payloads a subscription accumulated.
A field was supposed to be cleared but was not
PATCH semantics: fields you omit are left untouched, which is the safety property that prevents accidental wipes. To clear a field deliberately, send it explicitly with a null value in Airtable: Update Records.

Airtable is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products