Automating Clay to Find Emails from Company LinkedIn URLs via API

Rutger B. · 2026-02-02T12:00:05.484Z

I need to be able to send company linkedin URLs to clay and then have Clay find people working at just these companies, find their email, add to Lemlist. So not a compounding list that Clay always checks for finding people, just for the batch that I sent via API.

Automating Clay to Find Emails from Company LinkedIn URLs via API | Clay

14 comments

· Sorted by Oldest

Clay Support
APP
·
·
You can definitely do this! Here's how to set up a batch workflow:
Step 1: Send company URLs via API
Use our HTTP API to send company data to a Clay table. Set up a POST request to your table's webhook endpoint with the company URLs in the body. [1]
Step 2: Find people at those companies
Once the companies are in your table, use "Find people at these companies" action. Select your company URL column, set search parameters for the types of people you want, and import results to a new table.
Step 3: Find emails
Add email enrichment columns to find contact information for the people you discovered. [2]
Step 4: Send to Lemlist
Use another HTTP API column to send the enriched data (names, emails, company info) to Lemlist's API endpoint. [3]
This creates a one-time batch process rather than an ongoing automated list. Each API call processes just the companies you send, finds people at those specific companies, enriches with emails, then pushes to Lemlist.
Want me to walk through any of these steps in more detail?
CleanShot 2024-08-11 at 14_08_22@2x.png(90 kB)
CleanShot 2024-08-11 at 14_05_26@2x.png(122 kB)
Rutger B.
·
·
so the new table gets made programmatically, each time I do a post?
Clay Support
APP
·
·
No, a new table doesn't get created each time you POST. When you send data to a webhook endpoint, it adds new rows to the existing table that the webhook is connected to. [1]
Each POST request adds data as new rows in the same table. The webhook endpoint belongs to one specific table, so all your company URLs will accumulate in that table rather than creating separate tables. [2]
If you want a fresh table for each batch, you'd need to manually create a new webhook table each time or clear the existing one between batches. [3]
Clay Support
APP
·
·
Is that what you were looking for?
Rutger B.
·
·
I already knew that. But the PEOPLE found as the next step after the row arriving via API
Intercom
APP
·
·
Clay Support is sharing a file with you.
Ah got it! Yes, when you find people at companies, each person gets sent to a new table automatically. Use "Send row for each item in a list" - this flattens the people list so each person becomes their own row in the destination table. [1]
So your flow is: API adds company → find people action runs → people automatically get sent to a new table as individual rows → then you enrich emails and send to Lemlist from that people table. [2]
Intercom
APP
·
·
Clay Support is sharing a file with you.
Ah got it! Yes, when you find people at companies, each person gets sent to a new table automatically. Use "Send row for each item in a list" - this flattens the people list so each person becomes their own row in the destination table. [1]
So your flow is: API adds company → find people action runs → people automatically get sent to a new table as individual rows → then you enrich emails and send to Lemlist from that people table. [2]
Clay Support
APP
·
·
Did that answer your question?
Intercom
APP
·
·
Clay Support is sharing a file with you.
Perfect! You've got the right setup. In your screenshot, you'd select the column containing your people list (like "Results Returned C" if that has the people data from your company search). [1]
The "Send row for each item in a list" method will automatically create individual rows in your destination table - one row per person found. So if you find 10 people at a company, you get 10 separate rows in the people table. [2]
Then you can add email enrichment columns to that people table and push the enriched data to Lemlist. Each person becomes their own enrichable row rather than staying bundled in a list. [3]
Intercom
APP
·
·
Clay Support is sharing a file with you.
Perfect! You've got the right setup. In your screenshot, you'd select the column containing your people list (like "Results Returned C" if that has the people data from your company search). [1]
The "Send row for each item in a list" method will automatically create individual rows in your destination table - one row per person found. So if you find 10 people at a company, you get 10 separate rows in the people table. [2]
Then you can add email enrichment columns to that people table and push the enriched data to Lemlist. Each person becomes their own enrichable row rather than staying bundled in a list. [3]
Clay Support
APP
·
·
Does this clarify things?
Intercom
APP
·
·
Clay Support is sharing a file with you.
You need to select the column with your people list in that empty input field. In your case, that would be "Results Returned C" since it contains the people data from your company search. [1]
Once you select that column, each person in the list becomes a separate row in your destination table - so if "Results Returned C" has 5 people, you'll get 5 individual rows. [2] Then you can enrich emails and send to Lemlist from that flattened people table. [3]
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help with setting up your batch workflow or have any other questions, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific issues you’re facing?

Clay Support
APP
·
·
You can definitely do this! Here's how to set up a batch workflow:
Step 1: Send company URLs via API
Use our HTTP API to send company data to a Clay table. Set up a POST request to your table's webhook endpoint with the company URLs in the body. [1]
Step 2: Find people at those companies
Once the companies are in your table, use "Find people at these companies" action. Select your company URL column, set search parameters for the types of people you want, and import results to a new table.
Step 3: Find emails
Add email enrichment columns to find contact information for the people you discovered. [2]
Step 4: Send to Lemlist
Use another HTTP API column to send the enriched data (names, emails, company info) to Lemlist's API endpoint. [3]
This creates a one-time batch process rather than an ongoing automated list. Each API call processes just the companies you send, finds people at those specific companies, enriches with emails, then pushes to Lemlist.
Want me to walk through any of these steps in more detail?
CleanShot 2024-08-11 at 14_08_22@2x.png(90 kB)
CleanShot 2024-08-11 at 14_05_26@2x.png(122 kB)
Rutger B.
·
·
so the new table gets made programmatically, each time I do a post?
Clay Support
APP
·
·
No, a new table doesn't get created each time you POST. When you send data to a webhook endpoint, it adds new rows to the existing table that the webhook is connected to. [1]
Each POST request adds data as new rows in the same table. The webhook endpoint belongs to one specific table, so all your company URLs will accumulate in that table rather than creating separate tables. [2]
If you want a fresh table for each batch, you'd need to manually create a new webhook table each time or clear the existing one between batches. [3]
Clay Support
APP
·
·
Is that what you were looking for?
Rutger B.
·
·
I already knew that. But the PEOPLE found as the next step after the row arriving via API
Intercom
APP
·
·
Clay Support is sharing a file with you.
Ah got it! Yes, when you find people at companies, each person gets sent to a new table automatically. Use "Send row for each item in a list" - this flattens the people list so each person becomes their own row in the destination table. [1]
So your flow is: API adds company → find people action runs → people automatically get sent to a new table as individual rows → then you enrich emails and send to Lemlist from that people table. [2]
Intercom
APP
·
·
Clay Support is sharing a file with you.
Ah got it! Yes, when you find people at companies, each person gets sent to a new table automatically. Use "Send row for each item in a list" - this flattens the people list so each person becomes their own row in the destination table. [1]
So your flow is: API adds company → find people action runs → people automatically get sent to a new table as individual rows → then you enrich emails and send to Lemlist from that people table. [2]
Clay Support
APP
·
·
Did that answer your question?
Intercom
APP
·
·
Clay Support is sharing a file with you.
Perfect! You've got the right setup. In your screenshot, you'd select the column containing your people list (like "Results Returned C" if that has the people data from your company search). [1]
The "Send row for each item in a list" method will automatically create individual rows in your destination table - one row per person found. So if you find 10 people at a company, you get 10 separate rows in the people table. [2]
Then you can add email enrichment columns to that people table and push the enriched data to Lemlist. Each person becomes their own enrichable row rather than staying bundled in a list. [3]
Intercom
APP
·
·
Clay Support is sharing a file with you.
Perfect! You've got the right setup. In your screenshot, you'd select the column containing your people list (like "Results Returned C" if that has the people data from your company search). [1]
The "Send row for each item in a list" method will automatically create individual rows in your destination table - one row per person found. So if you find 10 people at a company, you get 10 separate rows in the people table. [2]
Then you can add email enrichment columns to that people table and push the enriched data to Lemlist. Each person becomes their own enrichable row rather than staying bundled in a list. [3]
Clay Support
APP
·
·
Does this clarify things?
Intercom
APP
·
·
Clay Support is sharing a file with you.
You need to select the column with your people list in that empty input field. In your case, that would be "Results Returned C" since it contains the people data from your company search. [1]
Once you select that column, each person in the list becomes a separate row in your destination table - so if "Results Returned C" has 5 people, you'll get 5 individual rows. [2] Then you can enrich emails and send to Lemlist from that flattened people table. [3]
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help with setting up your batch workflow or have any other questions, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific issues you’re facing?