Airtable
Airtable is an easy-to-use online platform for creating and sharing relational databases.
The Airtable Wrapper allows you to read data from your Airtable bases/tables within your Postgres database.
Preparation
Before you can query Airtable, you need to enable the Wrappers extension and store your credentials in Postgres.
Enable Wrappers
Make sure the wrappers
extension is installed on your database:
1 |
|
Enable the Airtable Wrapper
Enable the airtable_wrapper
FDW:
1 2 3 |
|
Store your credentials (optional)
By default, Postgres stores FDW credentials inside pg_catalog.pg_foreign_server
in plain text. Anyone with access to this table will be able to view these credentials. Wrappers is designed to work with Vault, which provides an additional level of security for storing credentials. We recommend using Vault to store your credentials.
Get your token from Airtable's developer portal.
1 2 3 4 5 6 7 |
|
Connecting to Airtable
We need to provide Postgres with the credentials to connect to Airtable, and any additional options. We can do this using the create server
command:
1 2 3 4 5 |
|
1 2 3 4 5 |
|
Create a schema
We recommend creating a schema to hold all the foreign tables:
1 |
|
Entities
The Airtable Wrapper supports data reads from the Airtable API.
Records
The Airtable Wrapper supports data reads from Airtable's Records endpoint (read only).
Operations
Object | Select | Insert | Update | Delete | Truncate |
---|---|---|---|---|---|
Records | ✅ | ❌ | ❌ | ❌ | ❌ |
Usage
Get your base ID and table ID from your table's URL.
Note
Foreign tables must be lowercase, regardless of capitalization in Airtable.
1 2 3 4 5 6 7 8 9 |
|
Notes
- The table requires both
base_id
andtable_id
options - Optional
view_id
can be specified to query a specific view
Query Pushdown Support
This FDW doesn't support query pushdown.
Limitations
This section describes important limitations and considerations when using this FDW:
- No query pushdown support, all filtering must be done locally
- Large result sets may experience slower performance due to full data transfer requirement
- No support for Airtable formulas or computed fields
- Views must be pre-configured in Airtable
- No support for Airtable's block features
- Materialized views using these foreign tables may fail during logical backups
Examples
Query an Airtable table
This will create a "foreign table" inside your Postgres database called airtable_table
:
1 2 3 4 5 6 7 8 9 10 11 12 |
|
You can now fetch your Airtable data from within your Postgres database:
1 |
|
Query an Airtable view
We can also create a foreign table from an Airtable View called airtable_view
:
1 2 3 4 5 6 7 8 9 10 11 12 13 |
|
You can now fetch your Airtable data from within your Postgres database:
1 |
|