Skip to main content
Use the @bijection/connectors/airtable entrypoint to declare Airtable resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Table records

pull: List, point reads and unconditional updates

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: standard

Case: airtable/records/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: airtable. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: readOnly

Case: airtable/records/pull/readOnly. Connection and resource configuration are declared by this exact case. Credential kind: airtable. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Webhook payload log

log: Retained payloads with signed pings as hints

The following example matches configuration pinged.

Configuration: pinged

Case: airtable/changes/log/pinged. Connection and resource configuration are declared by this exact case. Credential kind: airtable. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: changes
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: polled

Case: airtable/changes/log/polled. Connection and resource configuration are declared by this exact case. Credential kind: airtable. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: changes
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection holds an airtable credential (airtable.credential), a personal access token for https://api.airtable.com. Identity is the token’s user id from v0/meta/whoami. Bindings select the table with baseId and tableId, and the payload log with baseId and webhookId. records.pull lists the table by Airtable’s opaque offset, which is absent on the last page. Each record keeps id, createdTime and every returned cell as the JSON text of the value received. A number is a JSON double, so its text is that double’s shortest spelling; it is never re-rounded to the field’s precision or claimed as an exact decimal. A point read of a deleted record answered 403, the same status as a permission refusal, so neither 403 nor 404 is a tombstone: reconciliation refreshes known records and never withdraws one. A listing ends without withdrawing anything. update sends PATCH with { fields, typecast: false }. typecast: true would let Airtable create select options and coerce values, which changes the base, so it stays off. Identical requests produced distinct records and no idempotency key exists, so a send is a single attempt and reconciliation reports an unknown outcome. changes.log reads the webhook’s payload log by Airtable’s numeric cursor while mightHaveMore holds. Airtable keeps payloads for seven days; a pass walks the retained window, and changes older than it are lost without a tombstone. Each payload is kept by baseTransactionNumber, with Airtable’s changed, created and destroyed ids as JSON text. Deletions of records appear only here. With updates: "pings", a webhook ping verified as HMAC-SHA256 over the raw body (X-Airtable-Content-MAC: hmac-sha256=<hex>) requests another pass. The signing credential is the webhook’s macSecretBase64, and the key is its base64-decoded bytes. The ping carries no change data and no timestamp, so it proves a refresh hint and replay is bounded only by the delivery ring. Airtable allows five requests per second per base, declared as one shared five-per-second bucket for the connection. A stated Retry-After is honoured; the documented 30-second penalty after a 429 is not stated in the response and is not modelled beyond the transient-failure back-off. Nothing here has run against Airtable or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.