The airtable connector finds every base and table the token can read and sends each table's records as their own type. It runs Airbyte's Airtable connector definition inside the SDK.
| Connector name | airtable |
| Products | Records |
| Credentials | The portal's Connect button, or a personal access token |
| Scopes | data.records:read, schema.bases:read |
| Definition | Airbyte's source-airtable manifest, version 4.6.43 (Elastic License 2.0) |
| Status | Preview: tested against Airtable's documented responses, not yet on a live account |
What it pulls
One record type per table, named <base>__<table> in lower case (client_ledger__invoices). Field names are lower-cased with spaces as underscores. Each record keeps _airtable_id, _airtable_created_time and _airtable_table_name.
Credentials
- Go to airtable.com/create/tokens and create a token with the two scopes above.
- Under Access, add the bases you want to send.
Or skip the tokens: click Connect next to Airtable in the portal (Settings → Connected systems), then run datayield connect airtable --broker.
Connect
datayield connect airtable -o accessToken=env:AIRTABLE_TOKENOptions
| Option | Required | Meaning |
|---|---|---|
accessToken |
yes | The personal access token. Stored as a secret. |
New records on each run
Airtable records carry no last-modified time unless a base adds one, so each run sends every table whole. Airtable allows 5 requests a second per base; the SDK keeps to that.