DocumentationWorkflowsLogic and data
Airtable node
Use Airtable bases as a database: list, create, and update records. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
8 min readUpdated
What this node does
Use Airtable bases as a database: list, create, and update records.
Use Airtable as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Airtable from the node catalog.
- 02Complete the required fields and map values from previous steps.
- 03Run the node with a small test record and inspect its output.
- 04Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Choose the required function in Action. The panel then shows the relevant settings.
- List records
- Create record
- Update record
Settings
| Field | Meaning | Area |
|---|---|---|
| Airtable Personal Access Token | Pick the workflow secret holding your Airtable Personal Access Token. The token itself is never stored in the workflow, only the secret's name. | Protected |
| Action | Choices: List records, Create record, Update record | Standard |
| Base ID | The ID of your Airtable base (found in Airtable's API docs for your base or in the URL). | Standard |
| Table name | Name or ID of the table within the base. | Standard |
| Filter formula | Optional Airtable formula to only return matching records. | Standard |
| Max records | Optional: caps the total number of records returned. | Standard |
| Record ID | The ID of the record to update. | Standard |
| Fields (JSON) | JSON object with the column names and values for the new record. | Standard |
| Run once per item | Off (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry. | Standard |
| If one item fails | "Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file. | Standard |
| Pause between items (milliseconds) | Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes). | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
This node can process lists item by item. Error handling and the delay between items are available in advanced settings.
Example and test run
Fetch open tasks from an Airtable table: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"base_id": "appXXXXXXXXXXXXXX",
"table_name": "Tasks",
"filterByFormula": "{Status}='Offen'",
"max_records": 50
}Access and security
Before activation, review which data enters this step and what its output contains.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.
- List processed once: enable per-item execution in advanced settings.