n8n - 💡(How to fix) Fix [Bug] Deleting a field in "Map Each Column Manually" in Google Sheets node doesn't trigger workflow save state

Describe the problem/error/question

There is a UI state/saving bug in the Google Sheets node when using the Append or Update Row operation with the mapping mode set to Map Each Column Manually. This issue started occurring after upgrading our instance to version >= 2.18.

If a user maps multiple columns under the "Values to Send" section, and then later decides to delete one of those columns by clicking the trash can ("Remove column") icon, the field disappears from the UI. However, the workflow does not register this as a change, and the deletion is not saved.

If you navigate away or close the node, the removed column reappears. It is impossible to permanently remove a mapped column once it has been added unless you make an unrelated change elsewhere in the node to force a save state, or delete the entire node.

What is the error message (if any)?

No error message. This is a UI state and saving issue.

Please share your workflow/screenshots/recording

<img width="1265" height="856" alt="Image" src="https://github.com/user-attachments/assets/040cdf0a-2e80-43b2-a1a5-5639e74f6633" />

Debug info

core

• n8nVersion: 2.19.5
• platform: docker (self-hosted)
• nodeJsVersion: 24.14.1
• nodeEnv: production
• database: postgres
• executionMode: regular
• concurrency: -1
• license: enterprise (production)

storage

• success: all
• error: all
• progress: false
• manual: false
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 168 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2026-05-08T11:49:35.000Z