Airtable source

Airtable is available as a source connector. Arcyria discovers the bases and tables available to a Personal Access Token, previews records, stages the selected table, applies the saved SQL model, and delivers the resulting rows to a configured destination.

Before you begin

Create an Airtable Personal Access Token that can read records and base schema for only the bases you intend to sync. In Airtable, give the token these scopes:

data.records:read
schema.bases:read

Limit the token’s resource access to the required workspace or bases. Copy the token when Airtable displays it and store it in a password manager. Arcyria encrypts the saved token and never displays it again.

Airtable API keys are deprecated. Use a Personal Access Token beginning with pat, not a legacy API key.

Create the source connection

Open Connections in the Arcyria workspace.
Click + New Connection.
Choose the Source role.
Select Airtable.
Enter a descriptive connection name and the Personal Access Token.
Click Test Connection.
Confirm that the result reports at least one accessible base, then save.

The token does not need to contain a base ID. Base and table selection happens in the pipeline Source tab after the connection is saved.

Discover a base and table

Create a pipeline with the Airtable connection as its source.
Open the Source configuration.
Click Load bases or Discover catalog.
Select a base.
Select one or more tables returned for that base.
Preview the selected table and confirm the expected fields and records.
Save the source configuration.

Arcyria uses stable Airtable IDs internally. A selected table is represented as airtable.tbl..., while its DuckDB staging relation is normalized to a lowercase name such as airtable__tblefetdfzjakhuqt.

Renaming an Airtable table does not change its table ID, so a saved pipeline remains stable. Deleting and recreating the table creates a new ID; refresh discovery and select the replacement table before running again.

Source record shape

Every staged row includes the Airtable fields plus two lineage columns:

Column	Meaning
`_airtable_record_id`	Stable Airtable record ID used as the source primary key
`_airtable_created_time`	Airtable record creation timestamp

The record ID is used because Airtable permits an empty value in the configured primary field. User-created fields can be sparse: when a record has no value for a field, Arcyria preserves it as a nullable column instead of changing the schema between records.

Sync mode

Each table has its own sync mode.

Full table is the default. Each run reads all records visible to the token from the selected table.
Incremental is offered only for tables that have a Last modified time field set to watch all fields. Arcyria uses that field as the cursor and reads records edited since the previous run, with a short overlap window so recent edits are not missed. Tables without such a field show Full table only.

Incremental runs do not detect deleted records on their own. To remove them from the destination, open the table’s Options and turn on delete detection. At the interval you choose, Arcyria lists the record ids in the table and removes or flags destination rows whose record no longer exists. The pass is skipped when it would remove more than half of the destination rows, and it needs a destination key that is the Airtable record id. Arcyria only reads from your base; it does not add fields or webhooks. CDC, Replace, and Delete modes are not available for Airtable. Use a stable merge key at the destination so repeated runs update existing records instead of duplicating them.

Example SQL model

Replace the staging relation with the lowercase value shown by the SQL editor:

SELECT
  _airtable_record_id AS airtable_record_id,
  Name AS name,
  Email AS email,
  _airtable_created_time AS created_at
FROM {{ source('raw', 'airtable__tblefetdfzjakhuqt') }}
WHERE Email IS NOT NULL

Column names containing spaces should be double quoted:

SELECT
  _airtable_record_id,
  "Customer Name" AS customer_name,
  "Account Status" AS account_status
FROM {{ source('raw', 'airtable__tblefetdfzjakhuqt') }}

Validate and preview the model before configuring the destination mapping.

Verify a run

Open Runs after starting the pipeline and confirm:

Extract + Stage reports the expected source row count;
Transform reports the published SQL model;
Deliver reports the configured destination table;
failed rows are 0.

For an Airtable destination, also open the target base and confirm the merge-key values. For a database destination, query the target table directly.

Troubleshooting

Symptom	Resolution
Authentication failed	Create a new Personal Access Token and update the connection.
No bases appear	Add the required base to the token’s resource access.
No tables appear	Add `schema.bases:read`, then test and refresh the connection.
Preview is forbidden	Add `data.records:read` and confirm the token can access that base.
A saved table disappears	The table was deleted, recreated, or access was removed. Refresh discovery and select it again.
SQL cannot find the staging table	Use the lowercase staging name shown in the transformation editor, not the visible Airtable table name.
Repeated runs duplicate rows	Configure a stable Upsert key at the destination.

Next, follow the Airtable and MySQL pipeline guide or configure Airtable as a destination.

Introduction

Getting started

Connections

Connector Reference

Coming Soon Connectors

Pipelines

Transformations

Scheduling and Sync Modes

Pipeline Runs

Workspace

Billing and Usage

Security and Data Handling

Troubleshooting

Examples and Updates

Airtable source

Before you begin

Create the source connection

Discover a base and table

Source record shape

Sync mode

Example SQL model

Verify a run

Troubleshooting

​Before you begin

​Create the source connection

​Discover a base and table

​Source record shape

​Sync mode

​Example SQL model

​Verify a run

​Troubleshooting

Before you begin

Create the source connection

Discover a base and table

Source record shape

Sync mode

Example SQL model

Verify a run

Troubleshooting