I've noticed that Clay often fails to pull Linkedin data specifically when it comes to the "Enrich company" enrichment. It'll say no company found but I'll be able to manually find the company's linkedin. How can I improve the results for this query? I can also provide a sample table where I see this happening.
Hi there, thanks so much for sharing this! We’ll be passing your feedback along to our product team, and any additional context you can provide will help us prioritize with your needs in mind as we shape the roadmap.
Want to chat with someone on the team? Feel free to hit the button below!
Yashar clicked 'Talk with the team!'
Sir, this happens sometimes What i do is I add add extra Column clay agent and use gpt 4.0 mini which takes 0.20 credits per search This has been helpful for me till now.
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

Hey Yashar, as a first step I recommend using a clean format for the domain like this: https://naviaenergy.com/ or just the isolated domain (naviaenergy.com for example) To do so you can use the normalize a domain enrichment or use a free formula column. If that does not improve results I recommend using a claygent search to return the missing LinkedIn profiles. I hope this helps :)
Part of the issue is, even if a claygent returns the linkedin domains, the enrichment fails because "company not found" which then leaves me with a bunch of empty columns and downstream effects.
What you need to do to avoid this is to extract the linkedin from your enrich company column as its own column, do the same for your claygent column and then use a merge column enrichment to merge those two columns. Once those columns are merged you can use the resulting column as your input for downstream enrichments :)
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!
Thanks! We will check and get back to you!
