Inquiry About Create or Update Contact Action for HubSpot

Marc Christiansen · 2025-08-01 03:41:57.00667+00

When I was going through Clay University it looked like they were using a "Create or Update Contact" action for Hubspot. Is that action no longer supported? Context - it'd be great if there was an upsert "Create / update" Hubspot action as we often have workflows where some of our contacts are already in HS and some are not so it's pretty tedious to build out all the logic and conditions to ensure we get new contacts created if they don't exist and existing ones updated instead of doing it all in one action (especially if there is a lot of mapping)

Inquiry About Create or Update Contact Action for HubSpot | Clay

14 comments

· Sorted by Oldest

Clay
APP
·
·
Yes, the "Create or Update Contact" action for HubSpot is still supported. This integration allows you to create or update a HubSpot contact using an email address or existing Contact ID, which handles the upsert functionality you're looking for. The action leverages HubSpot's Contacts API to automatically create new contacts if they don't exist or update existing ones if they do, eliminating the need to build separate logic and conditions. This is exactly what you need for workflows where some contacts already exist in HubSpot and others don't.
Sources: Create or Update Contact with HubSpot Claybooks: Enrich inbound leads from form submissions and automate CRM updates | Clay.com
Marc Christiansen
·
·
Screenshot - it looks like we have a create object and update object but not one for both. Salesforce and other integrations have an upsert action but not seeing the Hubspot one that was in the Clay University Video.
Muhammad
·
·
yeah its no. longer support, that upsert function is gone for some reason
Muhammad
·
·
now you have to lookup contact <> if it exists <> update contact if it does not exists in the lookup <> create contact
Asher (Revenue Journey - Certified Clay Expert)
·
·
Hey Marc Christiansen , how about using a mix of ‘retrieve associated object’ by email and domain, then get that object's ID, then do 'Update Object'. That might work
Hari Kumar
·
·
Hey Marc! Were you able to figure this out? As a community member mentioned, the upsert function is no longer supported.
Marc Christiansen
·
·
Hari Kumar I understand you can use a combination of the create and update objects with conditional logic to accomplish the equivalent but this requires 2X the enrichments and setting up the mappings twice as well for any table that writes back to HS. Do you know why upsert is no longer supported or is there a feature request I can upvote for that? (Seems that the HS integration is not on parity with the others that have the upsert action)
Hari Kumar
·
·
Hey Marc! I definitely understand the frustration - I'll go ahead and flag this as a feature request internally :)
👍1
Channeled
APP
·
·
Arielle Halldin
·
·
Also facing the same issue!
David Riordan
·
·
Appreciate you flagging this Hari Kumar. Does this mean that previous workbooks using Upsert may now no longer operate (or operates as one and not the other)? Is there some sort of monitoring / alerting in the case where a action starts failing like that?
Hari Kumar
·
·
Hey Marc! Generally when we make updates they are only future-looking, so any existing workbooks that already work should continue to do so
David Riordan
·
·
Awesome - though I'm assuming that comes with the very reasonable caveat that since this goes through 3rd party apis, that can't always be the case, but you're gonna try to deprecate responsibly, gosh darnit.
Hari Kumar
·
·
That is correct Marc! Unfortunately, we can't take responsibility for third-party integrations' functionality after being removed as it is generally comes from their end

Clay
APP
·
·
Yes, the "Create or Update Contact" action for HubSpot is still supported. This integration allows you to create or update a HubSpot contact using an email address or existing Contact ID, which handles the upsert functionality you're looking for. The action leverages HubSpot's Contacts API to automatically create new contacts if they don't exist or update existing ones if they do, eliminating the need to build separate logic and conditions. This is exactly what you need for workflows where some contacts already exist in HubSpot and others don't.
Sources: Create or Update Contact with HubSpot Claybooks: Enrich inbound leads from form submissions and automate CRM updates | Clay.com
Marc Christiansen
·
·
Screenshot - it looks like we have a create object and update object but not one for both. Salesforce and other integrations have an upsert action but not seeing the Hubspot one that was in the Clay University Video.
Muhammad
·
·
yeah its no. longer support, that upsert function is gone for some reason
Muhammad
·
·
now you have to lookup contact <> if it exists <> update contact if it does not exists in the lookup <> create contact
Asher (Revenue Journey - Certified Clay Expert)
·
·
Hey Marc Christiansen , how about using a mix of ‘retrieve associated object’ by email and domain, then get that object's ID, then do 'Update Object'. That might work
Hari Kumar
·
·
Hey Marc! Were you able to figure this out? As a community member mentioned, the upsert function is no longer supported.
Marc Christiansen
·
·
Hari Kumar I understand you can use a combination of the create and update objects with conditional logic to accomplish the equivalent but this requires 2X the enrichments and setting up the mappings twice as well for any table that writes back to HS. Do you know why upsert is no longer supported or is there a feature request I can upvote for that? (Seems that the HS integration is not on parity with the others that have the upsert action)
Hari Kumar
·
·
Hey Marc! I definitely understand the frustration - I'll go ahead and flag this as a feature request internally :)
👍1
Channeled
APP
·
·
Arielle Halldin
·
·
Also facing the same issue!
David Riordan
·
·
Appreciate you flagging this Hari Kumar. Does this mean that previous workbooks using Upsert may now no longer operate (or operates as one and not the other)? Is there some sort of monitoring / alerting in the case where a action starts failing like that?
Hari Kumar
·
·
Hey Marc! Generally when we make updates they are only future-looking, so any existing workbooks that already work should continue to do so
David Riordan
·
·
Awesome - though I'm assuming that comes with the very reasonable caveat that since this goes through 3rd party apis, that can't always be the case, but you're gonna try to deprecate responsibly, gosh darnit.
Hari Kumar
·
·
That is correct Marc! Unfortunately, we can't take responsibility for third-party integrations' functionality after being removed as it is generally comes from their end