I sell small n8n workflows, and before selling one I test it end to end against a real Google Sheet. The first real-sheet test of my order workflow failed on every valid order, even though the same workflow had looked fine while I built it. This post explains why, so you don't ship the same bug.
The symptom
- The Google Sheets node (v4.5, "Append Row", mapping mode "Map Each Column Manually") is in the JSON with all column mappings filled in.
- After importing the workflow on another instance, every append fails or writes nothing. My error branch caught it, so the order was emailed to me as "ACTION NEEDED" instead of disappearing, but no row was ever written.
The cause
In "Map Each Column Manually" mode the node stores two things:
"columns": {
"mappingMode": "defineBelow",
"value": { "Order ID": "={{ $json.order_id }}", "...": "..." },
"schema": [ ... ]
}
value holds your expressions. schema holds the list of sheet columns the node fetched from the sheet while you were editing. If you build or edit the JSON by hand, or export it before the node ever loaded the sheet, schema can be empty. With an empty schema, the mapped values have no columns to go to.
The fix
Put one entry per column into schema, matching your header row exactly:
{"id": "Order ID", "displayName": "Order ID", "required": false, "defaultMatch": false,
"display": true, "type": "string", "canBeUsedToMatch": true}
Alternatively, open the node once in the editor with the real sheet selected, so n8n fills the schema, then export again.
A second one from the same test: "+44..." becomes #ERROR!
The same test turned the phone number +44 7700 900123 into #ERROR!. Google Sheets parses values starting with + (or =) as formulas when they're written "as the user would type them". Set the node's Options → Cell Format to RAW ("options": {"cellFormat": "RAW"}) and the value is stored as plain text.
How I test now
For every workflow I keep a test copy that points at a throwaway Google Sheet (shared with a service account) and a local mail catcher (Mailpit). A script posts the valid, invalid and broken cases and then reads the sheet back through the Sheets API. Both bugs above were invisible until the row was read back.
Disclosure: I sell tested n8n workflow kits, including the order workflow where I found these bugs: Order Intake Kit for n8n. Everything you need to fix the bug yourself is in this post.
Top comments (0)