Read, create and update Airtable records from any Windmill script, flow or app.
Set up in 3 steps
Create a personal access token
At airtable.com/create/tokens, create a token, grant it the scopes and the bases your scripts need, and copy it. It starts with pat.
Add the resource in Windmill
Open Resources, add a resource of type airtable, and paste the token.
Run your first script
Fork any script below. The base id is the app… segment of the base URL, and the table name is the tab's name.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Flows
Multi-step workflows that already wire Airtable to something else.
Resource types
The credential shapes the scripts on this page expect — pick the one your script asks for.
airtable
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| apiKey | string | No |
airtable_table
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| baseId | string | No | |
| tableName | string | No |
Questions
What is the airtable_table resource for?
It pairs a base id with a table name, so a flow can point at a table without repeating both in every step. It holds no credential — you still need an airtable resource alongside it.
A base returns nothing
A personal access token only reaches the bases you added to it. Edit the token in Airtable to grant the base.
Is my key stored on the hub?
Never. It lives only in your own Windmill workspace, encrypted at rest.