Enriching HubSpot with Clay (Part 4: Company Names)

HubSpot recently sunset its free Company Insights enrichment feature—leaving many users with incomplete company records and blank names in their CRM. In this post, Harris Kenny, founder of OutboundSync, walks through how to rebuild that enrichment layer using Clay.

By combining HubSpot lists, a structured waterfall of enrichment providers, and thoughtful logic to prevent unnecessary overwrites, you’ll learn how to maintain clean, consistent company names using a scalable and conservative approach.

Whether you’re replacing HubSpot Insights or future-proofing your enrichment stack, this guide shows one way to do it—with zero AI-induced hallucinations.

Watch

Transcript

00:00 Hey there, my name is Harris Kenny, I'm the founder of OutboundSync, and I'm picking back up our series on enriching HubSpot with Clay.
00:07 Now, I first started this series about nine months ago, and what really inspired it was Clay's new job tracking feature.
00:14 But I found that in order to take full advantage of that, there was some other CRM enrichment and CRM hygiene things that we wanted to do first.
00:22 So, I covered that in the first few videos. How to do contact name, contact phone number, contact LinkedIn profile inside of HubSpot.
00:31 However, a few things have changed since then. First, Clay has made a lot of progress on that job change tracking feature.
00:42 When I was testing at the beginning, it just was a little buggy, and so I didn't want to continue this series until I felt like we were ready to go.
00:48 Fortunately, it's working really well now, and Clay has also significantly increased its support for HubSpot, and so I am still gonna finish this series in the final video, which is coming up next.
00:58 We will talk about that. The other thing that's changed is that HubSpot has discontinued their company Insights feature. This is where HubSpot was enriching company records for free.
01:09 They're not doing this anymore. So, if you haven't noticed yet, There are gonna be a lot of company records in HubSpot that do not have a name anymore.
01:17 And I thought it would be really useful to show how to make up for this using Clay. And we're gonna adopt the same techniques that we used previously.
01:27 Everything we have done in this series so far in the first videos still applies. So, I'm gonna walk you through that with a little refresher on how that works.
01:34 And by the end of this video, you're gonna know how to use, Play to get the company names from across multiple different data providers inside of HubSpot.
01:43 Let's jump right in with our HubSpot list. Now, I've done two things here with this active list in HubSpot. The first thing is, I have a consistent naming convention.
01:55 So, you'll notice that in all of my videos here, we've got a very similar naming convention that we've got here.
02:00 I'm just gonna show you an, green. This naming convention is consistent across our videos and across all our lists. So, I can very quickly, in HubSpot, search to see which lists are being used for this enrichment project.
02:13 And you'll notice that it's modular. So, I have six different lists for the six different properties or fields that I am dynamically updating with Clay.
02:22 So, that if I want to change that or use different provider, It's very easy to see what's going in and out of HubSpot.
02:28 I really highly recommend this over doing a large sort of heavy table that's updating lots of things all at once.
02:37 This gives you just a lot more control over what's going on. Especially as your organization grows. Smaller workflows, tighter automations that are easier to audit and easier to manage.
02:46 I think, I think we're really glad you do it that way. you Second, is I have two different criteria here for company names that I want to go.
02:54 Enrich. The first is that the company name is unknown. That's an obvious one. You can see that here. We've got these dashes.
03:01 But I've also got companies where it contains a dot. And there's a lot of companies where the domain is basically sitting in the place of the company name.
03:09 And in situations like that, uh, it then may be the right name. One, two, the company may include, uh, their TLD inside of their company name.
03:16 Uh, like for a long time, uh, close. The CRM was close.io. And then they bought the dot.com and they became just close.
03:24 But for a long time, that was the company's name. Close.io. And so there are situations where that is correct. However, there are other situations where that's not correct. It's just the domain being used.
03:28 And so we can find a proper name. And we would prefer it used to. So what I'm gonna do in this video is I'm gonna show you how to check for that.
03:42 And if there's a change, we can override it. And if not, we'll leave it as is. Now that our list is built, let's go over to Clay.
03:50 Now, inside of Clay, we are using HubSpot. And specifically that HubSpot list as our source for the Clay table. This is gonna run once a day.
04:01 Let me see if I can find the settings on this table. Let's see. This Clay, oh, here we go. Um, sources, import object.
04:14 Okay, great. So this is running on a schedule. It's gonna run once a day. Gonna look for names to be updated.
04:19 And I could manually push an update if I need to. But once a day is fine, as far as I'm concerned.
04:25 I don't need to run more frequently than that. You can see the list of companies here that were also found in that previous HubSpot list.
04:33 I've got the ID. I've got the name. I've got the domain. And now I have a series of enrichments that are running.
04:39 The first one I'm using is Clay's Enrich Company. And so basically, as we move from left to right, in this table, you're gonna see we're using increasingly expensive providers.
04:48 So this is- This a classic and a very conventional waterfall approach. There's nothing too interesting here. I'm using one credit, then two, then three, then eight, and then finally a ten credit enrichment in Euler.
05:00 And you can see that as we go, I actually am able to find some with this more expensive provider. Uh, and as is the case in almost every enrichment in Clay, maybe all of them now, I'm not sure.
05:12 But if- if- if- a- an enrichment provider doesn't locate the source, you're not gonna get charged for it. You can get refunded.
05:19 And you can see that little refunded thing here. Right? So I'm not getting charged if Clay's enriched company doesn't find something.
05:26 I'm not getting charged if Datagma doesn't find something. Don't get charged by Rocket Reach. Don't get charged by ClearBit. Don't get charged by Owler.
05:33 So if- if they have the data, basically they get paid more for it. Okay? Now I have run conditions set for each of these columns.
05:40 I'm just gonna give you one example. Where if the Clay column here is empty, has no results, then run the next column.
05:53 Run Datagma. Conversely, if it has results, don't run it. Right? I don't need to be checking the same one over and over and over again.
06:00 So we've got five providers- and then finally we have a merge column that's pulling them together in order. And it's going in order of the enrichments.
06:08 This is pretty cool. I have a checkbox column that's basically saying if the discovered name, if there is a discovered name, and it's not the same as the existing name.
06:21 In other words, we found a new one. Mark that as true. Now, I did this in a checkbox column just to make it visual.
06:27 Technically, you don't need to do this. You could do this as a run condition in a subsequent or a later column.
06:32 But I just, I thought it was a nice clean way to show, hey, we're finding new data. You could filter that way if you wanted to using the filters inside of clay.
06:38 Umm, found a new name and you could do that as a checkbox filter if you want. Um, here, let's, let's do that.
06:47 So, for 224 of these, we found a new. Name. So, what does that mean? Like, why do I do that?
06:54 Well, basically, if it's the same as before, there's no reason in updating the record, right? So, leadoff.ai, the name that was found on LinkedIn, which is the source for this enriched company record, is the same as what's already in HubSpot.
07:07 So, I'm not going to rewrite it. Finally, I'm using the normal- Normal. Now, this is just using, I think, some logic that's coded in, some red jacks, regular expressions.
07:21 I actually played around with quite a few different ways of doing this using AI. Including Claygent, including just a regular API call into OpenAI.
07:30 Um. I didn't want to introduce new errors, and I was finding that that was happening a night. Enough that I didn't really feel like it was necessary to include AI in this case.
07:42 Excuse me. If we can find the company name, great, let's use it. If we can't, that's fine. We'll just leave it as is.
07:49 And. Here you can see what that cleanup looks like. So if we can find a good example here, this is, let's see.
08:01 A lot of these are pretty straightforward. Mm-hmm. Trying to find a good one for you. You know, e-cha-bot, l-t-d, just shortened it to e-cha-bot.
08:17 Sorry if there's a different way of saying that. I'm not sure what language that is. Um, but, you know, it just cleans it up a little bit.
08:23 Perhaps a lot, which is nice. And then finally, we're gonna run it enrichment. Here in HubSpot, we're gonna be updating the company record.
08:28 We're looking up the ID from our original list. We're taking our clean and ready domain name, and we're only gonna run it as long as it's a new name that was discovered.
08:43 And once we run this, it's gonna be pretty straightforward. It's gonna update the company names in HubSpot. And, uh, and we're-we're s stacking.
08:50 If you look at the previous videos in the series, you'll see that we're stacking enrichment upon enrichment upon enrichment. Finally, we're gonna have job tracking so that when this job changed from an existing contact in our CRM, we go to see what's going on.
09:01 We're gonna have just a nice clean environment to work in to see what has changed since we were in clay last.
09:07 So remember, this is no longer supported by HubSpot's company Insights. HubSpot does have a Breeze AI enrichment that does a lot of other things.
09:13 And frankly, that might be a good fit for what you're looking for. But if you just need company name, you can use clay to do that in the way that I've shown you here. If you've got ideas for how you would do this differently, definitely let me know.
09:25 I would love to see them, love to hear it, I would love to know if there's different providers that you use that you like more.
09:30 I tested quite a few different providers beyond what you see in the video and I played around with AI quite a bit.
09:36 Ultimately, I felt like this was, the do-no-harm, right? Precautionary principle. This is gonna give us a really solid, uh, low-risk, small-c conservative name that we can have inside of HubSpot, um, without introducing errors unnecessarily.
09:53 So, there you go. Try it out. Let me know what you think. And in the final video, we are going to finally look at how to track job changes, using clay for your contacts that are inside of half-spot.
10:06 And I'll give you a little sneak peek. We're gonna be using the lead object, because that's what we use internally.
10:11 And so I'll show you how to use the lead object to create a new lead when a job change is detected.
10:16 There are gonna be other ways to do that, like creating tasks. Um, but, I'm gonna show you how to- I'll show you how to do it with the lead object using half-spot.
10:23 And if you're using Breeze AI, you don't need to do any of So if you're not familiar, check out Breeze AI, which is HubSpot's CRM Hygiene Enrichment Product, which is really spurred on by their Clearbit acquisition.
10:35 Uh, and you can see we are actually using Clearbit as a provider here in this waterfall as well. Alright, thanks so much, and we'll see you in the next one.