Docs · Setup
Airtable connections
Rowvela writes to Airtable through a connection saved in your workspace. A connection is either an Airtable sign-in (OAuth) or a personal access token. Members of the workspace can use it in their imports, but nobody can read the token back.
Sign in with Airtable
In Settings → Airtable connections, select Connect with Airtable and choose the bases Rowvela may use. Rowvela refreshes the access on its own. If you later need another base, connect again and add it. The button is shown only when the installation has Airtable OAuth set up.
Use a personal access token
- In Airtable, open the developer hub and create a personal access token.
- Add the scopes below and, under Access, add the bases Rowvela should write to or read from.
- In Rowvela, select Add connection (or Use a token instead), enter a name and paste the token. After saving, the token is never shown again.
| Scope | Needed for |
|---|---|
data.records:read | Reading the table to compare it with the source |
data.records:write | Creating, updating and deleting records |
schema.bases:read | Listing bases, tables, views and fields, and checking field types |
schema.bases:write | Optional: Create them in Airtable for missing fields |
webhook:manage | Optional: Airtable change triggers |
Base, table and view
In an import, choose the Saved connection, then the Base and Table. If bases cannot be listed, enter the IDs from the Airtable URL: https://airtable.com/appXXXXXXXX/tblYYYYYYYY/… contains the base ID (app…) and the table ID (tbl…).
A Destination view limits matching and deletion to the records in that view. Rowvela cannot see view filters, so a record outside the view with the same key can be duplicated, and an updated record can drop out of a filtered view. Leave it on Entire table unless you need it.
Airtable permissions still apply. A token or sign-in can only do what the Airtable user behind it may do in that base.