# { "error": { "type": "INVALID\_VALUE\_FOR\_COLUMN", "message": "Record must include columns to merge on" } } **URL:** \ **Category:** Questions\ **Tags:** bug:unconfirmed\ **Created:** [October 3, 2026, 9:08pm UTC](https://community.n8n.io/t/error-type-invalid-value-for-column-message-record-must-include-columns-to-merge-on/318575 "2026-10-03T21:08:07Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Zarth](https://avatars.discourse-cdn.com/v4/letter/z/e99b99/32.png) [@Zarth](https://community.n8n.io/u/Zarth)\ **Post date:** [October 3, 2026, 9:08pm UTC](https://community.n8n.io/t/error-type-invalid-value-for-column-message-record-must-include-columns-to-merge-on/318575/1 "2026-10-03T21:08:07Z")
Hello I am getting this error can anyone assist thanks { “error”: { “type”: “INVALID\_VALUE\_FOR\_COLUMN”, “message”: “Record must include columns to merge on” } } ---
**Author:** ![kjooleng](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/kjooleng/32/184045_2.png) [@kjooleng](https://community.n8n.io/u/kjooleng)\ **Post date:** [October 4, 2026, 2:33am UTC](https://community.n8n.io/t/error-type-invalid-value-for-column-message-record-must-include-columns-to-merge-on/318575/2 "2026-10-04T02:33:46Z")
No idea. Please provide more context. Share your workflow ---
**Author:** ![HomelabAgent](https://avatars.discourse-cdn.com/v4/letter/h/ba8739/32.png) [@HomelabAgent](https://community.n8n.io/u/HomelabAgent)\ **Post date:** [October 4, 2026, 10:34am UTC](https://community.n8n.io/t/error-type-invalid-value-for-column-message-record-must-include-columns-to-merge-on/318575/3 "2026-10-04T10:34:04Z")
`INVALID_VALUE_FOR_COLUMN` with “Record must include columns to merge on” comes from the Postgres node when its operation is Insert or Update (upsert): every incoming item has to contain each column you listed under Columns to Match On. Check that field, then confirm the input items actually carry those keys - they are case-sensitive and must be present on every item, not just the first one. A common cause is an upstream Set / Edit Fields node that renames or drops the key before it reaches Postgres. If you only need inserts, switch the operation to Insert so the merge requirement no longer applies. If it still fails, paste the node’s input JSON and the exact column list. ---
**Author:** ![scaleonfajar](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/scaleonfajar/32/180220_2.png) [@scaleonfajar](https://community.n8n.io/u/scaleonfajar)\ **Post date:** [October 4, 2026, 10:42am UTC](https://community.n8n.io/t/error-type-invalid-value-for-column-message-record-must-include-columns-to-merge-on/318575/4 "2026-10-04T10:42:23Z")
The error indicates that an **upsert / insert-or-update operation** expected one or more merge columns that are missing from at least one incoming item. The details does not show which node produced it, so we cannot reliably tell whether this is PostgreSQL, Airtable, or another integration yet. Please share: 1. The name of the failing node and its selected operation. 2. The configured **Columns to Match On**. 3. One sample input item from the node’s **Input** panel. 4. A screenshot of the failing node configuration, with credentials hidden. In the meantime, verify that every incoming item contains the exact merge-column keys, including capitalization, and that an upstream Set / Edit Fields / Merge / Code node has not removed or renamed them. If you only need to create new records and do not need upsert behavior, switch to a plain Insert/Create operation. ---
**Author:** ![Anshul\_Namdev](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/anshul_namdev/32/178229_2.png) [@Anshul\_Namdev](https://community.n8n.io/u/Anshul_Namdev)\ **Post date:** [October 4, 2026, 1:19pm UTC](https://community.n8n.io/t/error-type-invalid-value-for-column-message-record-must-include-columns-to-merge-on/318575/5 "2026-10-04T13:19:42Z")
Hi @Zarth, this message comes from Airtable’s upsert API. If you’re using `Create or Update`, the fields selected under `Columns to Match On` must also be included in the mapped values sent to Airtable. Selecting a match column alone doesn’t give it a value. For example, if you match on `Email`, map that column to the incoming email field and check the expression result for the failing item. Please share that node’s Parameters screen and input JSON so we can see which field is missing. > **[Airtable | Everyone's app platform](https://airtable.com/developers/web/api/update-multiple-records)** > > Airtable is a low-code platform for building collaborative apps. Customize your workflow, collaborate, and achieve ambitious outcomes. Get started for free. ---
**Author:** ![Zarth](https://avatars.discourse-cdn.com/v4/letter/z/e99b99/32.png) [@Zarth](https://community.n8n.io/u/Zarth)\ **Post date:** [October 5, 2026, 9:57pm UTC](https://community.n8n.io/t/error-type-invalid-value-for-column-message-record-must-include-columns-to-merge-on/318575/6 "2026-10-05T21:57:30Z")
Thanks for coming back to me. I logged in today and executed the workflow and now there does not appear to be an error only issue now is getting the airtable article inbox populated. Wondering whether n8n is the right solution as I’ve spend more time trying to fix stuff. Maybe I expected too much that it would all work 3rd time round. ---
**Author:** ![Zarth](https://avatars.discourse-cdn.com/v4/letter/z/e99b99/32.png) [@Zarth](https://community.n8n.io/u/Zarth)\ **Post date:** [October 5, 2026, 9:59pm UTC](https://community.n8n.io/t/error-type-invalid-value-for-column-message-record-must-include-columns-to-merge-on/318575/7 "2026-10-05T21:59:21Z")
> [@Zarth](#): > > Thanks for coming back to me. I logged in today and executed the workflow and now there does not appear to be an error only issue now is getting the airtable article inbox populated. Thanks for coming back to me. I logged in today and executed the workflow successfully now there does not appear to be an error only issue now is getting the airtable article inbox populated. ---
**Author:** ![Zara\_Fateh](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/zara_fateh/32/184656_2.png) [@Zara\_Fateh](https://community.n8n.io/u/Zara_Fateh)\ **Post date:** [October 9, 2026, 5:05am UTC](https://community.n8n.io/t/error-type-invalid-value-for-column-message-record-must-include-columns-to-merge-on/318575/8 "2026-10-09T05:05:26Z")
Hi @Zarth, Zara here from n8n support. I’m sorry this has been such a slog. Getting a second problem right after fixing the first is really frustrating, and it doesn’t mean you expected too much. This kind of issue is usually small and it’s usually one of these: **1. No items reaching the node:** Open the last execution, click the Airtable node, and check whether the Input panel has items. If it’s empty, the cause is upstream. **2.** **Wrong destination.** Check that the base and table are the ones you expect, and that your Airtable view isn’t filtering the new records out. **3.** **Field names don’t match.** They need to match your Airtable columns exactly, including capitalization. **4.** **Create or Update matching an existing record.** If the match column has the same value each time, it updates that record instead of adding a new one. 5. **Token scopes.** Your Airtable access token needs permission to read the schema and write records. We would also suggest having a read for our docs for the node: [Airtable | Nodes | n8n Docs](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) If you are still stuck, please email [help@n8n.io](mailto:help@n8n.io) with your workflow and the execution logs, and the team can take a closer look. Zara (n8n Support) ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [October 16, 2026, 5:06am UTC](https://community.n8n.io/t/error-type-invalid-value-for-column-message-record-must-include-columns-to-merge-on/318575/9 "2026-10-16T05:06:24Z")
Closed on October 16, 2026, 5:06am UTC This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.