Google sheets keeps on saying coloums has been been changes i have refreshed deleted the node added a new one same isssue

Questions
1

Column names were updated after the node’s setup
Refresh the columns list in the ‘Column to Match On’ parameter. Updated columns: email → user_id, phone → email, channel → phone, last_message → channel, intent → last_message, is_lead_related → intent, status → is_lead_related, last_updated → status i got this error i have refreshed columns and it still hass the issue what do i do

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hi @SAM_M

Please can you share a screenshot of your google sheets node properties. This error generally means that you or someone changed the google sheets columns header in your sheet after you had setup your node. This could be either name changes or changing the order of the columns.

3

did you manage to fix it? I’m having the same issue. even after deleting the node, adding a new one, and remapping everything

4

The node caches column mappings internally, so deleting and re-adding doesn’t always fix it. Open the Google Sheets node, click into the “Column to Match On” dropdown, and use the small refresh icon right next to it. That forces n8n to re-read the actual sheet headers. If it still persists, check if any column header in the sheet has a trailing space or was renamed since you first configured the node.

5

Checking on when this is going to get fixed. Sheets Node v3 does not have this problem. We need columns to be able to be dynamically referenced. This is breaking multiple of my flows that need to be able to put the same data in multiple sheets with different column orders but same column names. Please allow the next version of Google Sheets Node to not cache columns.

6

TylerH, the useful repro is the same column names with different order across two sheets, not the older “rename a header then refresh” case.

Can you post the smallest example with Sheet A headers, Sheet B headers, the exact Google Sheets operation/node version, and whether the same workflow works in v3? That gives the n8n team a clean cache-vs-dynamic-mapping test instead of another refresh-columns loop.

7

One thing that usually fixes the stuck column cache: in the Google Sheets node, switch “Mapping column mode” from “Map automatically” to “Map each column manually”, save, then switch it back to “Map automatically” - this forces n8n to discard the cached schema and reload it fresh from the sheet. If that still doesn’t work, export the workflow JSON, find the Google Sheets node’s parameters, and manually delete the schema and schemaType keys from the JSON, then reimport. That completely clears the embedded column cache regardless of what the UI refresh does.