Airtable Update resets unmapped numeric field to 0 — works in one branch but not the other

[Hubspot] Webhook Deal Properties Change (copy from Make) (1).json (3.7 MB)

I’m seeing inconsistent behavior with the Airtable Update node when working with numeric fields, and I’d appreciate some insight.

Describe the problem/error/question

Trigger: HubSpot Deal update → n8n → Update matching Airtable record 
I have two branches in the workflow:
  1. Branch 1 – Deal Found Immediately
    Search Airtable
    If found → Update record
    Originally, I had an issue where:
    If a numeric field (e.g., deal_probability) was NOT mapped in the Airtable node
    Airtable would reset the value from (for example) 50 → 0
    To fix this, I added an Edit Fields (Set) node before the Airtable node and used it to explicitly map only some of the fields I wanted updated (not all fields in the record).
    After doing this:
  • The issue was resolved (seemed like it)
  • Unmapped numeric fields (like deal_probability) remained untouched
  • Only the explicitly mapped fields were updated in Airtable
Branch 2 – Deal Not Found Initially

- Wait node (5 minutes)
- Retry logic
- Then Update Airtable

I applied the exact same fix:
- Added an Edit Fields node
- Mapped only the intended fields

However, in this branch:

- deal_probability still gets reset to 0`, even though:
- It is NOT mapped
- The Airtable node configuration is identical to Branch 1

What is the error message (if any)?

Please share your workflow

I have uploaded my workflow here, would appreciate if anyone can help take a look? thank you so much!

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Self-Host on Hostinger

Hi @suetyiw Welcome!
You can try adding a set node in your 2nd branch directly before the airtable node and with keep only set fields enabled, with this that field would not be 0.

1 Like