Airtable (Edge)

Configure Airtable as a Source in your Pipeline

Perform the following steps to configure your Airtable Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Airtable.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Airtable Source.

   • In the Connect to Airtable section, click Authorize Airtable, and log in to your Airtable account if prompted. After you grant access, Hevo displays the email address of your Airtable user as Account Added.

6. In the Airtable window, select the bases that Hevo can access, and then click Grant access:

   • Everything you have access to: Hevo can access all your current and future bases.

   • Custom access: Hevo can access only the bases, interfaces, and workspaces that you select.

   

7. Click Test & Continue to test the connection to your Airtable Source. Once the test is successful, you can proceed to set up your Destination.

You can change the bases that Hevo can access later from the Integrations section of your Airtable account. If you remove a base from the access granted to Hevo, Hevo marks the tables of that base as inaccessible and continues to ingest the tables of the other bases. If you revoke all the access granted to Hevo, Hevo cannot read your Airtable data, and the jobs of the Pipeline fail. To resume data replication, modify the Source configuration in the Pipeline and authorize Hevo again.

---

Data Replication

Hevo replicates the data of all the tables selected on the Configure Objects page during Pipeline creation. Hevo lists the tables of each base that you granted access to as objects. By default, all the tables and their fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Hevo ingests data as follows:

• Historical Data: In the first run of the Pipeline, Hevo ingests all the records of the selected tables.

• Incremental Data: In the subsequent runs, as per the sync frequency, Hevo ingests the records that were created, changed, or deleted since the previous run. Hevo detects these records using a webhook that it creates in each base.

Hevo also ingests all the records of each table once every seven days. This brings the values of formula, rollup, and lookup fields up to date, because these fields can change without the record itself being changed, for example, when a linked record changes or when a formula uses the NOW() or TODAY() function. These values are also updated whenever their own record changes or Hevo ingests all the records of the table for another reason. Contact Hevo Support to change this interval for your Pipeline.

Hevo also ingests all the records of a table in the following cases:

• A field is added to or removed from the table, or the type of a field changes. Renaming a field does not cause a full read.

• Hevo cannot read the changes from the webhook, for example, when the Pipeline does not run for more than seven days and Airtable discards the changes.

Airtable allows 5 API requests per second for a base. Read Rate Limits. Hevo sends up to 5 requests per second to a base. If Airtable returns a rate limit error, Hevo waits and retries the request. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Pipelines with this Source support the Merge load mode. For the tables that have a Last modified time field that tracks all the fields of the table, you can also use the History Tracking load mode. Read History Mode.

---

Schema and Primary Keys

Hevo creates a schema in the Destination for each Airtable base. The name of the schema is made of the Destination prefix that you specify while creating the Pipeline, the name of the base, and the base ID. For example, for the base Project tracker with the ID app3UrkQfKNZMMnw7 and the prefix airtable, Hevo creates the schema airtable_project_tracker_app_3_urk_qf_knzmmnw_7. Hevo converts the name to lowercase and separates words, letters, and digits with underscores.

Each table of the base is loaded into a table with the name of the Airtable table. The primary key of each table is the id field, which contains the Airtable record ID.

---

Data Model

The tables and fields that Hevo creates in the Destination depend on the tables and fields of your Airtable bases:

Read Airtable field model for the types of fields in Airtable.

---