Verified emails and mobiles in your Clay tables
Call any MoltSets tool from a Clay HTTP API column and map the results into your table: work emails with an A-F risk score, mobiles, LinkedIn profiles and company data, on your own MoltSets plan.
paste into your http api column
example: linkedin_to_business_email
- Content-Type
- application/json
- Authorization
- Bearer ms_your_key
- User-Agent
- Clay
one column per tool · no charge when nothing is found
MoltSets in Clay
Clay doesn’t have a built-in MoltSets enrichment. It doesn’t need one: Clay’s HTTP API column can call any REST API, and every MoltSets tool is a single POST request with the same response shape.
Add one HTTP API column per MoltSets tool, point its body at your table’s columns, and pull the fields you want into their own columns with formulas. Calls run on your MoltSets API key, so they count against your MoltSets plan, the same as calling the API yourself.
What you can do
- / 01Get a work email and its A-F risk score from a LinkedIn URL column
- / 02Find work emails from a name and company domain, with no LinkedIn URL
- / 03Add mobiles, personal emails (US) and company data to the same rows
- / 04Split hits from misses on
status; a miss costs nothing
Connect MoltSets to Clay
-
01
Get an API key
Sign up free at app.moltsets.com and create a key under API keys. Keys start with
ms_. -
02
Add an HTTP API column
In your Clay table, click + Add column and choose HTTP API.
-
03
Set the request
Method
POST, and the tool’s endpoint from the API reference. Add three headers:Content-Type: application/json Authorization: Bearer ms_your_key User-Agent: Clay -
04
Map the body
Paste the request body from the tool’s reference page, then use Clay’s
/shortcut to swap each value for one of your columns. -
05
Pull out the fields
Set Response values to return to
results. Then add a Formula column for each field you want:results.emailresults.risk_scoreresults.last_validated_at
Pick the tool for the column you have
Each MoltSets tool is its own endpoint, so each gets its own HTTP API column. Start from the column you already have. Not sure? I have X, I want Y covers every combination.
| you have →you want ↓ | LinkedIn URL | Name + company domain | Email(s) | Website visitor IP |
|---|---|---|---|---|
| Work email | linkedin_ |
search_ |
· | · |
| Best email (work, else personal) | linkedin_ |
· | · | · |
| Mobile number | linkedin_ |
· | · | · |
| LinkedIn profile | · | · | email_ |
· |
| Send-safety grades | · | · | validate_ |
· |
| Company | · | · | · | ip_ |
A work email from a LinkedIn URL
request body · linkedin_to_business_email
{ "linkedin_url": "https://www.linkedin.com/in/jane-smith" } # in Clay: / → your LinkedIn columnresponse → your columns
{ "results": {
"email": "jane.smith@acme.com",→results.email Work email
"risk_score": "A",→results.risk_score A-F send grade
"last_validated_at": "2026-10-28"→results.last_validated_at Latest evidence
},
"status": "ok",→filter on this not_found = no charge
"metadata": { ... }
}
What teams use it for
-
01
Work emails for a LinkedIn list
Import LinkedIn URLs and add the tool. Every email comes back with a risk score, so you know which are safe before they reach a sequence.
tool
linkedin_to_business_email -
02
MoltSets first in a waterfall
Run MoltSets as the first email column, then run your next provider only where
statusisn’tok. Misses on MoltSets don’t cost anything.filter on
status -
03
Clean before you send
Send A and B, never send D, and put C and F in a slower, smaller campaign. The same grades come back for emails you already have.
tool
validate_emails -
04
Names and domains, no LinkedIn
Event lists and CRM exports often have a name and a company but no profile. One call finds the work email and the LinkedIn URL.
tool
search_business_email_by_name -
05
Mobiles for call lists
Add it for the rows your reps will call. Only mobiles come back, never landlines, and every number has passed a carrier check.
tool
linkedin_to_mobile_phone -
06
Accounts from website traffic
Got visitor IPs in a table? Turn each one into the company behind it, ready for people search.
tool
ip_to_company
Before you run a whole table
-
01Return results, then use formulas
Don’t: Put
results.emailin Response values to return. Clay only reads one level in, so it won’t work.Do: Return
results, then add one Formula column per field. -
02A miss isn’t an error
Don’t: Filter on the HTTP code. A miss still returns 200, with empty fields.
Do: Filter on
status. Rows with"not_found"cost no tokens. -
03User-Agent is required
Don’t: Leave out the User-Agent header. You’ll get
403 Forbidden.Do: Add
User-Agent: Clay. Any value works. -
04Test on a few rows first
Don’t: Run the column on the whole table straight away.
Do: Run it on ten rows. A wrong field name or mapping is cheap to fix there.
What it costs
Clay calls run on your MoltSets plan, with the same data and limits as the API. A lookup that finds nothing isn’t charged. Clay bills for its own usage separately, under your Clay plan.
Start free with 1,000 calls, then move to a flat-rate unlimited plan. Full detail on the pricing page.
free
Try before you commit, no card required.
get started- 1k data calls total
- 100 search records total
- Personal email included
solo
For solo builders and small lists.
get started- Unlimited data
- 500 search records / 5h
- Personal email included
pro MOST POPULAR
For teams enriching at scale.
get started- Unlimited data
- 7.5k search records / 5h
- Personal email included
team
For teams that have outgrown the $97 limits.
get started- Unlimited data
- 75k search records / 5h
- Personal email: 75k / week
Questions & answers about MoltSets in Clay
Every step is in the clay setup guide.
Not a built-in enrichment. You connect MoltSets through Clay’s HTTP API column, which works with every MoltSets tool and takes a few minutes per tool to set up. The Clay setup guide walks through it.
Yes. Clay calls MoltSets with your own API key, so you need a MoltSets account and a key. The free plan includes 1,000 calls with no card, which is enough to set up and test your columns.
Clay’s HTTP API only reads one level into the response. Set Response values to return to results, then add a Formula column that references the HTTP API column and picks results.email.
The call returns HTTP 200 with status set to not_found and the fields in results empty or null. No tokens are charged. Filter on status to split hits from misses, or to run a fallback only on the misses.
Usually a missing User-Agent header. MoltSets needs one on every request; any non-empty value works. Also check the Authorization header is Bearer followed by a space and your key.
Start from the column you have. From a LinkedIn URL, linkedin_to_business_email for a work email or linkedin_to_best_email to fall back to a personal one. From a name and domain, search_business_email_by_name. I have X, I want Y covers the rest.
A is validated deliverable; B has a known open, click or order and no bounce; C is a catch-all server, where deliverability can’t be known; D is invalid, bounced, a complaint or a trap; F has no signal either way. Never send to D. How the grades work.
It can. Each row is one request, and every plan has a fair use window. When you reach it, the API returns 429 with the number of seconds until you can carry on. See rate limits.
Not using Clay?
I use an AI agent
I write code
I prospect on LinkedIn
Something else? See every integration.
Get your API key
1,000 API calls, no card. Sign up and start calling the API today.