Google Sheets node ignores custom header row setting during column mapping in n8n

Based on the documentation and current behavior, it appears that while the Data Location on Sheet options let you specify which rows contain the headers (and where the data starts), the automatic mapping mode’s column list retrieval still uses the default (first row) as the header reference. This means that even if you set the Header row to 5, n8n continues to fetch the column list from row 1.

What’s Happening

• Data Location on Sheet: This option is meant to control operations—such as appending or updating rows—by letting you specify where your headers and data are located.
• Column Mapping Extraction: In the Map Automatically mode, n8n currently does not adjust the column list based on a custom header row setting. It continues to retrieve headers based on the first row in the sheet.

Workarounds

• Map Each Column Manually: Instead of relying on the automatic mapping, you can switch to Map Each Column Manually. This approach allows you to explicitly specify the columns from your header row that starts on row 5.
• Adjusting the Sheet: If it’s possible to reformat your Google Sheet so that your header row is at the top (row 1), the automatic mapping mode will work as expected.

Summary

The behavior you’re experiencing—where the column list isn’t updated when using a header row other than row 1—is known, as the current column mapping extraction doesn’t take the Header row setting into account. Switching the mapping mode or adjusting the sheet format are the main options until an update addresses this limitation.

If you’re looking for a persistent solution or a fix in future releases, consider checking the n8n issue tracker or community forum for updates and potential patches related to this behavior.