Update existing contact record when using 'Create a Contact' action in workflow

We are going to be syncing transactions from another platform into Hubspot. When the transation data is received into Hubspot, a new deal is created and also includes some personal information which would usually be found on a contact rather than deal record. We will then use workflows to distribute this information to the right properties.

I have created a deal-based workflow and used the “Create a Contact Record” action, to create a new contact record with the synced data and associate the two objects.

If a contact does not exist with the email listed on the deal, a new contact record is created and the two objects are associated - great.

However, if a contact already exisits using the email listed on the deal, I believe the workflow action will simply fail. I would prefer the existing contact record to be updated and also become associated with the deal in the workflow.

Is this possible?

Hi @FMontgomery,
Thank you for reaching out to the Community!
I found the solution from @karstenkoehler on this similar post “Workflow to create a deal…if it doesn’t already exist” that might help you!
I also wanted to invite a couple of subject matter experts to this conversation @danmoyle, @deepikaverma and @Franci do you know if there is a way to put in place the use case above to help @FMontgomery to check if a contact record already exists via workflow, please?
Also, if anybody else has anything to add and/or share, please feel free to join in the conversation :slightly_smiling_face:
Thanks and have a great day!
Best,
Bérangère

Hi @FMontgomery.

When the integration moves data into HubSpot Deals, do you have properties like “Contact Email” that will push into the Contact record email? If that’s the case, and that’s what gets pushed to create the Contact associated to the Deal, would this work?

First step is a branch that checks if a Contact exists (you could check for create date).

If it does exist, update the properties you want updated.

If the contact does NOT exist, you create the Contact record.

Here’s what that could look like:

From there, you move the data you need moved in each branch. Thoughts?

Thanks for the tag @BérangèreL - you’re awesome.

Hi Dan, thanks for responding.

This would be an ideal solution. I wasn’t aware you could populate both a deal an associated contact property (email) during the data sync. It sounds this is possible, based on your answer above?

I do hope so!

I believe it’s possible indeed. :blush: Would love to hear an update after you implement this, @FMontgomery!