Say you have a People table with many thousands of rows. Many of these people work at the same Company. You want to enrich Company data, but don't want to spend unnecessary credits on duplicative enrichments. What's the most efficient way to only enrich each Company only once in a People table?
The most efficient approach is to use Clay's linked tables feature. Instead of enriching company data directly in your People table, create a separate Company table and enrich company data there once per company. Clay automatically links your Find Companies table to your Find People table, allowing you to extract company attributes directly into your People table without paying credits multiple times for the same company. For example, if you have 10 people at AirBnB, you'd enrich the company data once at the company level and pull it into your people data for all contacts. To pull company data into your People table, simply rerun the lookup column that's linked to your company table. This pulls enriched company data into your people table while saving credits and creating a more integrated dataset.
Sources: Find People [Clay 101] - Clay University Find People [Clay 101] - Clay University Enrich People (Waterfalls) [CRM Enrichment] - Clay University Enrich People (Waterfalls) [Automated Inbound] - Clay University Enrich People (Waterfalls) [Automated Outbound] - Clay University Enrich People (Waterfalls) [Automated Outbound] - Clay University Enrich People (Waterfalls) [Automated Inbound] - Clay University
How should I structure the new Companies table
Structure your Companies table with these essential columns: Core identifiers: ** Company name ** Company domain (required for most enrichments) ** Company LinkedIn URL (for highest accuracy) Enrichment columns to add: ** Headcount/employee count ** Headquarters location ** Industry ** Company description ** Funding stage ** Revenue data ** Tech stack information Start with company domain as your primary identifier, then add enrichment columns based on your specific needs. Once enriched, you can pull this data into your People table by rerunning the lookup column that links to your company table.
Sources: Enrich People (Waterfalls) [Automated Inbound] - Clay University Enrich People (Waterfalls) [Automated Outbound] - Clay University Enrich People (Waterfalls) [CRM Enrichment] - Clay University Enrich People (Waterfalls) [Automated Inbound] - Clay University Enrich People (Waterfalls) [Automated Outbound] - Clay University Jigsaw Framework - Clay University
The Company enrichment column will be performed by Claygent
Perfect! Using Claygent for company enrichment in your separate Companies table is an excellent approach. Once Claygent enriches the company data in your Companies table, you can pull that enriched information into your People table by rerunning the lookup column that links to your company table. This ensures you only pay for Claygent enrichment once per company, regardless of how many employees from that company are in your People table, while still having access to all the enriched company data across all your contacts.
Would the first step be Lookup Multiple Rows in Other Table?
No, "Lookup Multiple Rows in Other Table" is typically used from your Companies table to search your People table, not the other way around. For your workflow, you'd first create a separate Companies table with unique company domains, then use Claygent to enrich company data there once per company. After enrichment, you'd use a lookup column in your People table to pull the enriched company data back in. The "Lookup Multiple Rows" action is more useful for counting prospects per company or finding multiple matching records.
So I need to manually copy the company data from the People table and paste it into a new Companies table
Is there an enrichment that allows me to push only one unique company to a new Companies table
No, you don't need to manually copy and paste. Use the "write to table" feature instead. Click "Add Enrichment" → search for "Write to Table" → select your company data columns from the People table → choose to create a new Companies table. This automatically transfers your company data and creates the structure you need for efficient enrichment.
Yes, use the "write to table" feature. Click "Add enrichment" → search for "Write to Table" → select your company data columns from the People table → choose to create a new Companies table. This automatically transfers unique company data and creates the structure you need for efficient enrichment.
So I write all of the data from the People table to the new Companies table, then deduplicate the Companies data in the Companies table?
Yes, exactly! Use "write to table" to transfer company data from your People table to create a new Companies table, then deduplicate the Companies table. To deduplicate: click the company column header in your Companies table → select "Dedupe" → confirm which duplicates to remove. Alternatively, enable auto-dedupe by clicking the auto-dedupe icon at the bottom-right → toggle on "Enable automatic deduplication" → select your company identifier column (like domain).
What's the difference between using Write to Table and Send table data here
"Send table data" is our newer feature for transferring data between tables, available in the Actions dropdown. The legacy "write to table" columns are still available through the "Add Enrichment" button and will remain until the new routing features rollout is complete. "Send table data" offers two methods: "Send row" (transfers each row as-is) and "Send row for each item in a list" (flattens lists into separate rows). Both features accomplish similar goals but "Send table data" is the updated approach.
Hi! Did this answer your question or do you need more help here?
Send Table Data is pretty neat. When was it launched / how long has it existed?
Hi - great question! Send Table Data is actually a pretty recent feature - it launched to all users in April 2025, so it’s been around for about 3 months. It was built as part of Clay’s updated routing system to eventually replace the older Write to Table action.
Key Differences ** Write to Table is mainly used to organize enriched data into a brand-new table — especially helpful when an enrichment returns lots of data that would clutter your main table. ** Send Table Data is built for routing data between existing tables, often used for filtering, branching logic, or flattening lists. With Send Table Data, you can: ** Choose specific columns to send with a cleaner UI ** Automatically update existing rows when re-running * Handle list-based data (e.g. sending one row per person at a company) It's quickly become the default for multi-table workflows thanks to better performance and usability. Let me know if that makes sense or if you have any other questions on this!
Can I piggyback off Joe's question as I am trying to do the same thing. I have 50,000 individual contacts from 18,500 companies - i.e. 2+ contacts for most companies. To the first step, i have the company name and domain, but not the company linkedIn url. do i lose a lot of accuracy by not having it? could i seek to add the company linkedin url as an enrichment column?
Hey there Brad, thanks for reaching out, to clarify you won't lose a lot of accuracy if you don't have the company LinkedIn URL. What's going to happen here, is it's going to use a process that would look for this data point anyway, so all you really would have done by having the LinkedIn URL is save yourself a couple steps in this process
.png){kind=logo}
