Fixing Duplicate Company Records in Clay-HubSpot Integration | Clay

Fixing Duplicate Company Records in Clay-HubSpot Integration

Hey could someone help me out with this? Running into an issue with Clay-HubSpot integration. The Problem: I have a Clay table with multiple leads, some from the same company When I run "Create Company in HubSpot", Clay creates duplicate companies - one for each lead from the same company So if I have 3 leads from Apple, Clay creates 3 separate Apple company records in HubSpot What I've Tried:

"Lookup Company" action (this checks existing HubSpot records, not duplicates within Clay)
Conditional logic on the create action
Multiple formula approaches to count occurrences
AI actions to identify first occurrences
Clay's formula builder with different prompts

None of these work What I Need: A way to make Clay only create ONE company record per unique company during a single table run, regardless of how many contacts work there. Has anyone solved this before? Thanks

10 comments

Clay
APP
·
·
Use Clay's Auto-dedupe feature to prevent duplicate company creation within your table: 1. Click the Auto-dedupe button at the bottom-right of your table 2. Toggle on "Enable automatic deduplication" 3. Under "Dedupe via column," select your company domain or company name column as the unique identifier 4. Click "Save changes" This automatically removes duplicate companies before running your HubSpot integration. For additional protection, use the "Lookup Company" action first to check existing HubSpot records, then set up conditional logic to only create companies that don't exist in either Clay or HubSpot. The auto-dedupe ensures only one row per unique company remains in your Clay table, preventing multiple company creation attempts.
Sources: Auto-update and Auto-dedupe Table Push Data To Your CRM [Clay 101] - Clay University Push Data To Your CRM [Clay 101] - Clay University
Matteo C.
·
·
Auto-dedupe will remove some leads from the table, I just tried.. That is not a solution
Asher
·
·
Hey Matteo C., have you tried doing this. I ran into this issue early on when I was using Clay as well. This might help.
1.
Push all the leads into another table (Literally duplicate them)
2.
On the new table, dedupe using domain name.
This way, you will have 2 separate tables. One for companies only. One for leads. Then create companies in HubSpot using the company table.
Matteo C.
·
·
Hey Asher, thanks for the help. I'm trying to push leads to another table, but can't find the way to do it. I saw there are multiple actions such as "Write to Other table", but only pushes certain columns, not the whole table itself. How did you do that? On the other hand, if I "Create Companies" in one table and "Create Contacts" in another, I will not be able to use the "Associate Objects in HubSpot" action to make sure the new company and contact records are correctly associated. Hope you understand what I mean..😅 Do you know any other practices that can solve this? Thanks, and I appreciate your help!
Asher
·
·
Hey Matteo C., did a quick video to share with you my thinking process. Doing this video with limited understanding of your current setup, but hope it shows you how my process would look like 🙂 https://www.tella.tv/video/for-matteo-a4qg
Matteo C.
·
·
Hey Asher, thanks a lot for the vid! I understand the process you are following and it could work (altough its adding extra steps to a already long process). My concern after the video is the Object associations. Since you can't call a variable from another table into an action, when using the associate objects in Hubspot, I am not able to link the contact record id with the company record id, due to the fact that they are in different tables. Would it maybe be easier to hop on a quick call so I can show you what I mean? If that's ok with you clearly. Let me know:)
Asher
·
·
Hey Matteo C. , sure man! Happy to jump on a call and figure this out 👍🏻 Wil drop you a DM!
Clay
APP
·
·
Hello! Thanks for reaching out. Do you mind sending over the table link URL for me to take a look?
Matteo C.
·
·
Was able to solve it in the end, so no worries. Thanks for the help!
Clay
APP
·
·
Hey Matteo! Glad you figured it out. Going to go ahead and close this out now. Do reach out if you need anything else! :)