Best Practices for Enriching Company Info without Duplication

Joe H. · 2025-12-18T21:09:03.266Z

I have a list of contacts in a table and want to enrich company information for the company the contact works at. multiple contacts can work at the same company, and i don't want to enrich the same company info twice. what's the best way to manage this

Best Practices for Enriching Company Info without Duplication | Clay

Clay Support
APP
·
·
Use linked tables! Clay automatically links your Find Companies table to your Find People table. [1]
Enrich company data once at the company level, then pull it into your people table for all contacts from that company. This saves credits since you're not enriching the same company multiple times. [2]
When you add new company data later, just rerun the lookup column in your people table to sync the updated information.
Clay Support
APP
·
·
Is that what you were looking for?
Joe H.
·
·
What's the specific name of enrichment I should use. Send table data? or something else
Clay Support
APP
·
·
"Send table data" is the current action to use - it's found under Actions → Send table data in your table. [1]
The old "Write to Other Table" enrichment is deprecated, so stick with "Send table data" for moving rows between tables. This lets you choose which columns to send and keeps your company enrichments in one place while pulling that data into your contacts table. [2]
Clay Support
APP
·
·
Did that answer your question?
Joe H.
·
·
yep just making sure cause you said "used linked tables" but recommended the send table data enrichment. just wanna make sure i'm using the best enrichment for this use-case
Clay Support
APP
·
·
You're using the right approach! "Send table data" is correct for your use case. [1]
The "linked tables" concept refers to the overall workflow - you create separate company and people tables that connect to each other. "Send table data" is the specific action that makes this connection work by moving data between those tables. [2]
This setup lets you enrich company data once in your company table, then use "Send table data" to pull that enriched info into your people table for all contacts from the same company - avoiding duplicate enrichments and saving credits. [3]
Clay Support
APP
·
·
Does this help clarify?
Clay Support
APP
·
·
If you need any more help with managing your company and contact data enrichment, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any challenges you’re facing?
Saad A.
·
·
Hi Joe H. - just wanted to check in, if this issue resolved or not? If not so I can help you and guide you end to end, what you have to do!
Clay Support
APP
·
·
You're all set with the right approach! "Send table data" is exactly what you need for your use case. [1]
The workflow is: create separate company and people tables, enrich company data once in the company table, then use "Send table data" to pull that enriched info into your people table for all contacts from the same company. [2] This avoids duplicate enrichments and saves credits.
The old "Write to Other Table" enrichment is deprecated, so "Send table data" under Actions is the current recommended method.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need any help with managing your company and contact data enrichment, I’m here to assist. Would you like to share more about what you’re trying to achieve or any challenges you’re facing?
Taimoor A.
·
·
take the compay data to other table then use enrichment for company enrich after that go to your main take and use lookup method it will help you out
Clay Support
APP
·
·
Exactly right! That's the optimal workflow:
1. Use "Send table data" (Actions → Send table data) to move company data to a separate company table [1]
2. Run company enrichments once in that dedicated company table
3. Use "Lookup Multiple Rows in Other Table" or "Lookup Single Row in Other Table" to pull the enriched company data back into your main contacts table [2]
This approach saves credits by enriching each company only once, regardless of how many contacts work there. The lookup method pulls the enriched data without duplicating enrichment runs.
Note: "Write to Other Table" is deprecated, so stick with "Send table data" for moving data between tables.

17 comments