Airtable

UI Bakery allows you to connect easily to Airtable without additional layers like APIs and 3rd-party services.

Airtable imposes certain limitations to API abilities:

• 5 requests per second, per base.

Configuration

3 essential components are required to connect your Airtable database to UI Bakery:

• Personal access token.

You can create and copy it from your Airtable Developer page:

Click the Create new token button, specify Name, Scopes, and Access properties based on your requirements, and Create the token.

When copied, paste it into the Personal access token data source property.

• Database ID.

Open an Airtable APIs page, click on a database that you need to connect and copy over the base ID:

• List of database Tables.

Open your database and copy the exact names of the Tables you need to use in your app.

A table must have at least one row for UI Bakery to recognize its fields.

Click Test Connection. If the test is successful, click Connect Data source. UI Bakery will extract the database structure and store column types. This information will be used to suggest the proper table columns and form field types.

Usage

Once you have a connection between UI Bakery and Airtable, you can access its data, load and send it back.

Please note that UI Bakery limits the number of loaded records by default to 1000. To expand this limit, enter the required limit in action that loads Airtable data

Airtable supports the below action types:

• Load Table

• Load Row

• Create Row

• Update Row

• Delete Row

Loading table views

Additionally, it is possible to set a specific Airtable view that will be loaded for the selected table. This comes in handy in case you'd like to configure advanced filters on the Airtable side and load the pre-configured view.

To do this, scroll down the Load Table configuration to the Additional settings section and specify view as a key and name of your view as a value:

Loading a custom view

Filter by linked items

Unfortunately, Airtable API is limited to filtering only by displayed values, thus filtering by internal ID is not supported (other than by a record ID of the table).

You'll need to:

• Create a new formula field ID with the formula RECORD_ID() in the related table - this will list the internal record ID as a value.

• In the main table, create a lookup field to display the value from step 1, for instance Related Ids.

• Use your filtering logic on the value from step 2, for example you can use in or = operators.