Skip to main content
Question

Airtable API success in n8n but columns remain blank

  • Sep 26, 2026 12:32 PM UTC
  • 4 replies
  • 113 views

M-salman

Hi everyon

e,

 

I have been stuck for over 6 hours trying to get my Airtable "Update Record" node (Node 4) to write data back into my base. The workflow executes completely successfully with 100% green lights, but the rows in Airtable remain completely blank.

 

Here is my exact configuration for Node 4:

1. Base & Table: Correctly connected to my target base and table.

2. Mapping Column Mode: Set to "Map Each Column Manually".

3. Columns to match on: Kept completely empty/cleared out.

4. Values to Update:

   - id (using to match): {{ $json.id }}

   - Article_Status: Done

   - AI_Response: {{ $node["Basic LLM Chain"].json.text }}

 

Both the schema names ("Article_Status" and "AI_Response") match my Airtable column headers exactly with the correct underscores. When I click "Execute step" or run the full workflow, n8n shows a successful run, but nothing updates in rows 15 or 16 of my Airtable sheet. 

 

Since n8n isn't throwing an error code, I am unable to trace why the data payload is silently dropping before reaching the grid. Any guidance on what might be causing this block would be highly appreciated!

4 replies

Forum|alt.badge.img
  • New Participant
  • Sep 27, 2026 2:04 PM UTC

Hi everyon

e,

 

I have been stuck for over 6 hours trying to get my Airtable "Update Record" node (Node 4) to write data back into my base. The workflow executes completely successfully with 100% green lights, but the rows in Airtable remain completely blank.

 

Here is my exact configuration for Node 4:

1. Base & Table: Correctly connected to my target base and table.

2. Mapping Column Mode: Set to "Map Each Column Manually".

3. Columns to match on: Kept completely empty/cleared out.

4. Values to Update:

   - id (using to match): {{ $json.id }}

   - Article_Status: Done

   - AI_Response: {{ $node["Basic LLM Chain"].json.text }}

 

Both the schema names ("Article_Status" and "AI_Response") match my Airtable column headers exactly with the correct underscores. When I click "Execute step" or run the full workflow, n8n shows a successful run, but nothing updates in rows 15 or 16 of my Airtable sheet. 

 

Since n8n isn't throwing an error code, I am unable to trace why the data payload is silently dropping before reaching the grid. Any guidance on what might be causing this block would be highly appreciated!

The first thing I’d isolate is whether {{$json.id}} is the actual Airtable record ID (rec...) or just an id field from an earlier step.

A quick test:

1. Run the step before the Airtable update and inspect its output.
2. Check whether the value you map as the record ID starts with rec.
3. Temporarily hard-code one known Airtable record ID and set only Article_Status = Done.
4. Run the node once.

If that works, the Airtable connection and write permission are fine and the problem is in record targeting/mapping.

If you’re using an operation that matches on columns instead of a direct Record ID, make sure an actual unique match column is configured. Leaving the match field empty while passing a normal id value can give you a workflow that runs cleanly without touching the intended row.

I’d also verify the node’s output contains the Airtable record that was actually updated, rather than treating a green execution as proof of the external result.

If you can share the JSON output immediately before Node 4 (with sensitive values removed), especially the id field, it should be possible to tell which case this is pretty quickly.


00jason
Forum|alt.badge.img
  • New Participant
  • Oct 27, 2026 12:13 PM UTC

The first thing I’d check is the record ID mapping in Node 4. In n8n, a successful execution doesn’t always mean the intended Airtable record was updated.

Make sure {{ $json.id }} contains the actual Airtable record ID (usually starts with rec), not your article’s row number or another ID. Also, check the output of Node 3 to confirm that Article_Status and AI_Response are being passed with the expected values. If the record ID is correct, test updating just one field on a single record, then add the AI response mapping back. This should help narrow down whether the issue is record matching or field mapping.


00jason
Forum|alt.badge.img
  • New Participant
  • Oct 28, 2026 4:48 AM UTC

One thing worth checking here is whether the Airtable node is receiving the correct record ID and whether the update operation is configured to target that record properly. A workflow showing a successful execution doesn't always mean the intended fields were updated, so inspecting the node's input and output can help narrow down the issue.

This kind of problem can be frustrating when you're building automated content workflows. For example, managing video links, processing content, and keeping track of completed tasks becomes much easier when each step is properly organized. I work on Clipzun, a browser-based TikTok video downloader, and I can see how useful reliable automation and clear status tracking would be when managing content-related tasks at scale.


Luc_00
Forum|alt.badge.img+1
  • New Participant
  • Nov 2, 2026 9:39 PM UTC

Adding one check on the Airtable side, since the record ID points above are about the n8n side:

Open row 15 in Airtable, expand the record and look at its revision history.
- If there's an entry from the time of your run, the update did reach Airtable, and the problem is the values: most likely the AI text came through empty.
- If there's no entry at all, the update went to a different record, or to another table or base.

For the first case, click the Basic LLM Chain node after a run and look at its output: if the text isn't under "text" in your version, {{ $node["Basic LLM Chain"].json.text }} resolves to nothing and n8n sends an empty value without any error. Testing with a fixed value like "test" in AI_Response will confirm it in one run.