Hi there - getting this error trying to run an upsert back to Airtable….
.png){kind=logo}
{"error":{"type":"INVALID_VALUE_FOR_COLUMN","message":"Record must include columns to merge on"}}have got it using the URL field to merge on.
When performing an upsert operation with Airtable, you need to explicitly specify the Match Criteria fields that will be used to determine whether to insert or update a record. While you're using the URL field, you need to make sure it's properly set as a match criteria field in the upsert configuration.To resolve this error: 1. Make sure you've specified the URL field in the "Match Criteria" section of the upsert configuration 2. Ensure you've also included the fields you want to include/update in the "Fields to Include/Update" section Source: Airtable integration overview | Documentation | Clay University
Ok thanks. I’ve switched to using update record, and now it’s saying- value is not an array of record IDs. Any suggestions what that means?
This error typically occurs when the Update Records action isn't receiving the correct format for the Record ID field. When updating records in Airtable, you need to provide a valid Record ID for the specific record you want to update. Make sure you have: 1. Included the required Record ID field in your update configuration 2. Provided a valid Record ID value for the specific record you want to modify 3. Specified the fields you want to update in the "Fields to Update" section Source: Airtable integration overview | Documentation | Clay University
Am taking the ID that comes from Zapier, and putting it in a Clay ID table. is this not correct? How do i know what the valid Record ID is?
When updating records in Airtable, you need to use Airtable's own unique Record ID, not an ID from Zapier. To find the correct Record ID, I recommend using the "Lookup records" action first to find the specific record in Airtable that you want to update. This will return the valid Airtable Record ID that you can then use in the "Update records" action. Source: Airtable integration overview | Documentation | Clay University
Yes this is the Airtable ID, not a Zapier ID - Zapier just happens to be forwarding it along.
I'm glad we could clarify that for you. I'm here if you have any more questions about Clay.
Hi Stephen J.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Do you have to do any other formatting to it?
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Like, add quotes or something?
This record ID looks like this: reccV82T2MXWlcmIs
No, you don't need to add any special formatting to the Airtable Record ID. You can use it as is ('reccV82T2MXWlcmIs') in the Update Records action. Just make sure you're using the correct Base ID along with it. Sources: Airtable integration overview | Documentation | Clay University Update Record with Airtable
it all seems to be correct - Base ID and Table ID…
Great! I'm glad everything appears to be correct. I'm here if you need any further assistance.
Hi Stephen J.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
No, the Base ID is correct, and it’s still not working
Based on the information provided, I can't determine the exact reason why the update action isn't working, as there could be several factors involved. Here are the key requirements for the Update Records action to work: 1. Base ID (required) 2. Record ID (required) 3. Fields to Update (you need to specify which fields and values you want to modify) 4. Proper API permissions (ensure you have the necessary API key and permissions)Since you've confirmed the Base ID and Record ID are correct, please verify: ** You've specified the fields you want to update ** You have the proper API permissions set up * The API key is correctly configuredIf you're still experiencing issues after checking these elements, please request human support for further troubleshooting. Sources: Airtable integration overview | Documentation | Clay University Update Record with Airtable
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
ok thanks - here or by email?
Hi Stephen! Feel free to drop all info here :) We'll look at it right away. If there's anything else I can assist you with, please let me know! 😊 Have a great Monday, Daniel
Hi Daniel - should be all there above - can’t get the People enrichment to send the enriched record back to Airtable
Stephen - Do you mind sending the link to the table so we can take a look? https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1736154900&signature=55d614043e96c80d1dd2ceb8a07186d0c5df28c1e6d6980f6cdf82bd9315c8ff&req=dSEgF85%2FmohWX%2FMW1HO4zYTywS39A5Mf2BKsam%2FhVPu%2B9w%3D%3D%0A
Hey Stephan, thanks for your patience on this. We can see that at least one of the fields you’re trying to update is expecting an array of record IDs (typical for a linked-record field in Airtable), but the update request is sending a value that’s not in the correct format. In other words, instead of sending something like:
"Linked Field": ["recXXXXXXXXXXXXXX", "recYYYYYYYYYYYYYY"]
a non-array or non-ID value was passed—causing Airtable to reject the request with INVALID_VALUE_FOR_COLUMN. It seems you're trying to update linked records in Airtable. Instead of pushing strings you need to put the record IDs from the other Airtbale. From the logs alone, Airtable doesn’t explicitly name which field caused the error. Chatgpt gave me that as a potential solution. https://downloads.intercomcdn.com/i/o/w28k1kwz/1322652085/6690e202b895976611c68505b2a4/Arc_PttPItr9D8.png?expires=1736158500&signature=f2281af924fb9037f67df4f7919d0dbe82d66d08c02b41c2b9c240e7211ee03c&req=dSMlFM97n4FXXPMW1HO4zTY6BQK16hl%2FVInMs7rFR82wh%2F8MdJTk0jmO%2FqKw%0AjW2D%0A https://downloads.intercomcdn.com/i/o/w28k1kwz/1322652822/32cde44d8b665b883a9c5e2e0317/Arc_ecQ1iEQrYW.png?expires=1736158500&signature=90ac1122a7a52c88622e5d3507232aef175a2c465d27b99e2aecfa87045de30f&req=dSMlFM97n4ldW%2FMW1HO4zdXuxDeT%2BhkwsCoO9gQ8JnuHvEqvZ46hMEhQ2Dt8%0ArLJ4%0A
Ah interesting, thanks. No reason to keep a Linked field in there, so will review the fields and remove any that are linked.
I wasn’t aware that it’s possible to add Linked field entries - presumably that would just duplicate an entry that’s already there if it doesn’t have a lookup step?
Totally get where you're coming from with the "easy for now" solution of removing linked entries. I'm not entirely certain about how Airtable would handle it either. My best guess is that you might need an extra lookup step from the other Airtable to update linked records. It shouldn't result in duplicates. Maybe give it a test run on a test Airtable to be sure?
Thanks. Yes, for a full enrichment from a LinkedIn URL it would make sense to figure out a solution for a linked record of the org. Have removed the org for now and it works fine. Shame the error messages between Airtable and Clay are so obscure!
I’ll now try and figure out how to get the linked field (Org) working for the update. May need to make another post to the forum!
Hi Stephen J.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
