Verified emails and mobiles in your Zaps
Call any MoltSets tool from a Webhooks by Zapier action and use the results in the next step: work emails with an A-F risk score, mobiles, LinkedIn profiles and company data, on your own MoltSets plan.
webhooks by zapier › post
example: linkedin_to_business_email
- linkedin_url
- LinkedIn URL from an earlier step
- Authorization
- Bearer ms_your_key
- User-Agent
- Zapier
one action per tool · no charge when nothing is found
MoltSets in Zapier
There’s no dedicated MoltSets app in Zapier. Webhooks by Zapier can call any REST API, and every MoltSets tool is a single POST request with the same response shape.
Add one Webhooks action per tool, map its input from an earlier step, and use results in the steps after. Calls run on your MoltSets plan, the same as calling the API yourself.
What you can do
- / 01Enrich every lead that triggers a Zap, from a form, a CRM or a sheet
- / 02Get a work email and its A-F risk score from a LinkedIn URL
- / 03Filter on
statusso only hits carry on, and misses are free - / 04Send the results to your CRM, a sheet or Slack in the next step
Connect MoltSets to Zapier
-
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 a Webhooks action
Add an action step, choose Webhooks by Zapier and pick POST as the event. Set URL to the tool’s endpoint from the API reference.
-
03
Fill in the data
Set Payload Type to
json. Under Data, put the parameter name on the left and map the value from an earlier step on the right:linkedin_url: LinkedIn URL from an earlier step -
04
Add the headers
Under Headers, add your key as a Bearer token and a
User-Agentwith any value:Authorization: Bearer ms_your_key User-Agent: Zapier -
05
Test and use the results
Test the step to see the real response. Its fields, including the email, risk score and
status, are then there to map in later steps. Add a Filter on status so only hits carry on.
Pick the tool for the field you have
Each MoltSets tool is its own endpoint, so each gets its own Webhooks action. Start from the field 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 Zapier: map the URL from an earlier step under Dataresponse → later steps
{ "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
Enrich new leads as they arrive
When a form, CRM or sheet triggers the Zap, add the work email and its grade before the lead goes anywhere else.
tool
linkedin_to_business_email -
02
MoltSets first in a waterfall
Put MoltSets first, then use Paths or a Filter so only leads where
statusisn’tokgo on to your next provider. Misses on MoltSets don’t cost anything.filter on
status -
03
LinkedIn contacts, straight in
The MoltSets Chrome extension can send every contact you save to a Catch Hook trigger, starting the Zap for each one.
trigger
Catch Hook -
04
Clean before you send
Grade the emails you already have and route on the result: send A and B, never send D, and put C and F in a slower campaign.
tool
validate_emails -
05
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 -
06
Accounts from website traffic
Got visitor IPs from your analytics or a form? Turn each one into the company behind it.
tool
ip_to_company
Before you turn the Zap on
-
01Don’t leave Data empty
Don’t: Leave the Data section blank. Zapier then sends every field from the previous step as the body.
Do: Add just the parameters the tool needs, such as
linkedin_url, under Data. -
02User-Agent is required
Don’t: Send the request with only the Authorization header. MoltSets returns
403 Forbiddenwithout a User-Agent.Do: Add
User-Agentunder Headers with any value, such asZapier. -
03A miss isn’t an error
Don’t: Assume the step found something because it ran. A miss still returns HTTP
200, with empty fields.Do: Add a Filter on
status:okis a hit,not_foundis a free miss. -
04Test on one record first
Don’t: Turn the Zap on and let it run on every new lead straight away.
Do: Test the step on one record, check the fields you map are right, then turn the Zap on.
What it costs
Zapier calls run on your MoltSets plan, with the same data and limits as the API. A lookup that finds nothing isn’t charged. Zapier bills for its own usage separately, under your Zapier 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 Zapier
Every step is in the moltsets api reference.
There isn’t a dedicated app. A Webhooks by Zapier POST action works with every MoltSets tool: set the URL, data and headers, and the response fields are there for the next step.
POST, for most Zaps. You fill in the Data section field by field and Zapier builds the JSON. Custom Request sends raw JSON exactly as you type it, with no checks, which is easier to get wrong.
Under Headers, as Authorization with the value Bearer ms_your_key. Add a User-Agent header next to it.
Usually a missing User-Agent header. MoltSets needs one on every request; any non-empty value works. Also check the Authorization value is Bearer, a space, then your key.
The call returns HTTP 200 with status set to not_found and empty results. No tokens are charged. Add a Filter on status so only hits carry on.
Yes. Zapier calls MoltSets with your own API key, so you need an account and a key. The free plan includes 1,000 calls with no card, which is enough to build and test a Zap.
Yes. Start a Zap with Webhooks by Zapier and the Catch Hook event, copy the webhook URL into the MoltSets Chrome extension, and turn the Zap on. Every contact you send arrives as the same flat JSON.
Not using Zapier?
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.