This n8n airtable integration tutorial covers how the n8n Airtable integration lets you create, read, update, and delete records in your Airtable bases directly from n8n workflows. But here’s something most tutorials don’t mention: the native Airtable node in n8n only covers 8 actions. To access the full Airtable API, you need to use the HTTP request node.
This airtable n8n integration guide covers both approaches. You’ll learn how to set up the Airtable access token, use the native node for standard CRUD operations, set up advanced API calls through HTTP request, configure the Airtable polling trigger, and connect Airtable to an AI agent.
Airtable — and the airtable n8n workflow — is a database-spreadsheet hybrid more structured than Google Sheets but easier to use than a traditional database. If you already use n8n with spreadsheets, this guide covers the key differences compared to the n8n Google Sheets guide. For a general n8n introduction, see the n8n beginner guide.
What Is the n8n Airtable Integration?
The n8n Airtable integration connects via the n8n airtable node to your Airtable bases using a personal access token. It includes a native Airtable node with 8 built-in actions, a polling trigger for event-driven workflows, and full HTTP request support for advanced Airtable API operations.
Airtable organizes data into workspaces, bases (databases), tables, and records (rows). Each base can have multiple tables, and each table has its own set of fields. n8n interacts with this structure by targeting a specific base and table in each node.
The native n8n airtable node covers the most common operations. For anything beyond that, the HTTP request node connects directly to the Airtable REST API, which gives you access to fields management, webhooks, views, and more.
How to Set Up Airtable Credentials in n8n
Airtable uses personal access tokens for API authentication. Here’s how to create one and connect it to n8n.
Step 1: Create an Airtable Personal Access Token
Go to airtable.com/create/tokens and click Create Token. Give it a name that describes what it’s for (like ‘n8n Integration’).
Under Scopes, add the permissions this token needs. Click Add Scopes and select all the data:records, data:bases, and schema options you’ll need. For full access, add everything. If you’re creating a token for an external developer or limited use, select only the specific scopes required.
Under Access, choose whether to grant access to specific bases or all current and future bases. For admin-level automation, select all resources. For client or external workflows, add only the specific bases they should reach — do not share a token with access to your entire Airtable account unless necessary.
Click Create Token. Airtable shows the token once. Copy it immediately and keep it somewhere safe — you’ll need it twice in this guide. If you lose it, you’ll need to regenerate it.
Step 2: Add the Airtable Credential in n8n
For n8n airtable integration setup: in n8n, add an Airtable node. Click the credential dropdown and select Create New Credential. Choose ‘Connect using access token’ and paste in the token. Click Save.
If the connection test succeeds, you’re set. Rename the credential to something specific, like ‘Airtable — My Workspace.’ If you manage multiple Airtable accounts, descriptive credential names prevent you from pointing a workflow at the wrong base.
The n8n Airtable Native Node: 8 Actions
The n8n airtable node documentation shows 8 actions in the native node — including the n8n airtable node upsert operation (Create or Update Record): Create Record, Create or Update Record, Delete Record, Get a Record, Search Records, Update Record, Get Many Bases, and Get Base Schema. These cover standard CRUD operations for most common workflows.
Create a Record
The n8n airtable node create record action adds a new row to an Airtable table. In the node settings, select your base (workspace), then your table, then map the fields you want to populate.
Fields are mapped by dragging and dropping values from earlier nodes in the workflow, or by setting them manually. Fields you don’t include will remain blank in Airtable. You only need to fill the fields that matter for that particular record.
Search Records with filterByFormula
Search Records retrieves records that match a formula filter. In the Filter By Formula field, enter an Airtable formula to narrow the results. Example: amount >= 4500 returns only records where the Amount field is 4,500 or higher.
Airtable formula syntax is similar to Excel/Sheets. Some useful patterns: NOT({fieldName} = ‘’) returns all non-empty rows. IS_AFTER({Created}, DATEADD(TODAY(), -7, ‘days’)) returns records from the last 7 days. AND({Status} = ‘Active’, {Amount} > 1000) combines multiple conditions.
Search Records is more practical than Get a Record for most workflows because it returns multiple results based on criteria rather than requiring a specific record ID.
Update and Delete Records
Both Create or Update Record and Update Record modify existing records’ fields. You need the record ID — find it in the Airtable URL when you open a specific record in full-screen view. Everything before the ? in the URL is the record ID.
Delete Record removes a record permanently (not to trash). In automated workflows, you typically get the record ID from a Search Records step earlier in the workflow, then pass it to the Delete step.
Using HTTP Request for Advanced Airtable API Calls
The n8n airtable node docs cover the native operations, but Airtable’s full API includes field management, bulk updates, webhook setup, table creation, and more. To access these, use the HTTP request node.
The HTTP request node also future-proofs your workflows. When Airtable releases new API features, you can use them immediately via HTTP request without waiting for the n8n Airtable node to be updated.
Import Curl Directly from Airtable Docs
The fastest way to configure an HTTP request for Airtable is to copy the curl example directly from Airtable’s API documentation at airtable.com/developers/web/api/introduction. Each endpoint shows a curl example.
In n8n, add an HTTP Request node. Click the Import from Curl button. Paste in the curl string and click Import. n8n fills in the method, URL, headers, and body fields automatically based on the curl.
You’ll need to edit the URL to replace the placeholder base ID and table name with your actual values. The URL format is: https://api.airtable.com/v0/{baseId}/{tableIdOrName}. Find your base ID and table ID in the Airtable URL: the part starting with ‘app’ is the base ID, and the part starting with ‘tbl’ is the table ID.
Setting Up Airtable Authentication in HTTP Request (Do This Right)
When you import a curl, n8n may hardcode the bearer token directly in the Authorization header. This is not secure. If you ever share this workflow or export it as JSON, anyone who receives it can see your Airtable token.
Instead, save your Airtable token as a generic credential in n8n. In the HTTP request node, go to Authentication > Generic Credential Type > Header Auth. Create a new credential and set the Name to ‘Authorization’ and the Value to ‘Bearer YOUR_TOKEN_HERE’.
Now your token is stored securely in n8n’s credential vault rather than hardcoded in the workflow. Any future HTTP request nodes can select this credential — you won’t need to paste the token again.
Need Help Building AI Automations?
n8n Airtable Trigger: Polling for New Records
The n8n airtable trigger node uses polling, not webhooks. It checks Airtable on a schedule (every minute, every hour, or custom cron) to see if new records have been added or changed. When it detects a new event, it starts the workflow.
Add an Airtable Trigger node, select your base and table, choose what field triggers the event, and set the poll interval. For workflows that need to run on a time delay (like a daily summary), a polling trigger checking once per day works well. For near-real-time responses, set it to every minute.
Note: Airtable supports native webhooks but requires additional setup through the Airtable API. For most workflows, the n8n polling trigger is sufficient.
See also: n8n beginner guide
Example Workflow: Poll, Filter, and Update Airtable Records
Here’s a practical workflow pattern using the Airtable trigger: poll for new rows, check a condition, then update the record based on the result.
Node setup: Airtable Trigger (polls for new records) → If Node (check a condition on the new record, like whether the ‘Active’ field is checked) → Airtable: Update Record (true branch — update the record with new data) → end.
A real use case: you add a record to Airtable manually or via a form. The trigger picks it up, checks if it meets certain criteria, and automatically fills in additional fields — like setting a ‘Status’ to ‘Processed’ or updating an amount to zero. This removes the need for manual follow-up after data entry.
Using Airtable as a Tool in an n8n AI Agent
You can attach Airtable to an AI agent as a tool, letting the model query and update records based on conversational input or dynamic conditions.
In the AI Agent node, click the Tools + icon and search for Airtable. Select the resource (Record) and operation (Search, Create, Update, or Delete). The Search operation with filterByFormula is especially powerful — you can let the model decide what formula to apply based on the user’s request.
For filterByFormula, enable the expression toggle on that field. This lets the AI agent generate the formula string dynamically. For example, a user says ‘show me all records with amount over 5000’ and the agent constructs the formula AND({Amount} > 5000) automatically.
Two things matter for Airtable tool quality: set a clear tool description explaining what the tool does and when to use it. And in the agent’s system prompt, explicitly tell the agent when it should query Airtable vs. answer from memory. Without these, the model may call the tool unnecessarily or miss cases where it should use it. See the n8n AI agent guide for full agent setup details.
Frequently Asked Questions
How do I connect Airtable to n8n?
Go to airtable.com/create/tokens, create a personal access token with the required scopes and base access, then add a new Airtable credential in n8n by pasting the token. n8n tests the connection automatically. The whole process takes about 2 minutes.
Why should I use HTTP request instead of the native Airtable node in n8n?
The n8n airtable node docs list 8 actions. Airtable’s full API supports dozens more, including field management, bulk operations, webhook setup, and table creation. Use the HTTP request node when you need an operation that isn’t in the native node. You can import the curl example directly from Airtable’s API docs into the n8n HTTP request node.
What is filterByFormula in n8n Airtable?
filterByFormula is an Airtable API parameter that filters records returned by a search. In the n8n Airtable Search Records node, enter a formula like {Amount} >= 4500 to return only records matching that condition. Formula syntax follows Airtable’s formula language, similar to Excel: you can use AND(), OR(), NOT(), DATEADD(), and comparison operators.
How does the Airtable trigger work in n8n?
The Airtable trigger polls your Airtable base on a schedule (every minute, hour, day, or custom cron) and fires the workflow when it detects new records or changes. It’s a polling trigger, not a true webhook — there’s a delay equal to the poll interval. Configure the trigger by selecting the base, table, and the field that determines what counts as a ‘new’ event.
Is it safe to hardcode my Airtable token in an HTTP request node?
Never hardcode the bearer token in the Authorization header of an HTTP request node. Anyone who sees or shares that workflow can access your Airtable account. Instead, store the token as a Generic Header Auth credential in n8n and reference it in the Authentication field. This keeps the token encrypted in n8n’s credential store and out of the workflow JSON.
Next Steps: Build Your Airtable + n8n Workflow
The n8n Airtable integration has two layers: the native node handles 80% of use cases (create, search, update, delete), and the HTTP request node handles everything else. The credential setup is the same for both — one personal access token, stored as a generic header auth credential.
The challenge for this tutorial is a good place to start: use the Airtable trigger to find all records added in the last 7 days, pass them to an AI agent to write a summary, then send the summary as an email. It combines the Airtable polling trigger, filterByFormula, the AI agent, and the Gmail node.
The JSON workflow file and sample Airtable CSV are available in the Skool community. See the n8n Gmail integration guide to set up the email step.
