Verified emails and mobiles in your n8n workflows
Call any MoltSets tool from an n8n HTTP Request node and use the results in the next one: work emails with an A-F risk score, mobiles, LinkedIn profiles and company data, on your own MoltSets plan.
http request node settings
example: linkedin_to_business_email
- Name
- Authorization
- Value
- Bearer ms_your_key
- User-Agent
- n8n
one node per tool · no charge when nothing is found
MoltSets in n8n
There’s no dedicated MoltSets node to install. n8n’s HTTP Request node can call any REST API, and every MoltSets tool is a single POST request with the same response shape.
Add one HTTP Request node per tool, map its input from the node before, and read results in the node after. Store your key once as an n8n credential. Calls run on your MoltSets plan, the same as calling the API yourself, on n8n Cloud or self-hosted.
What you can do
- / 01Enrich every item that reaches the node, from a form, a CRM trigger or a sheet
- / 02Get a work email and its A-F risk score from a LinkedIn URL
- / 03Branch on
status: hits one way, misses the other, and misses are free - / 04Send the results to your CRM, a sheet or Slack in the next node
Connect MoltSets to n8n
-
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 Request node
Add it after the node that has your data. Set Method to
POSTand URL to the tool’s endpoint from the API reference. -
03
Add your key
Set Authentication to a generic Header Auth credential with these values. Then turn on Send Headers and add a
User-Agentheader with any value, such asn8n.Name: Authorization Value: Bearer ms_your_key -
04
Send the body
Turn on Send Body, set Body Content Type to JSON and Specify Body to Using JSON, then map the input from the previous node:
{ "linkedin_url": "{{ $json.linkedin_url }}" } -
05
Use the results
The node outputs the whole response. Read the fields you need in the next node, and add an If node on
statusto split hits from misses:{{ $json.results.email }}{{ $json.results.risk_score }}{{ $json.status }}
Pick the tool for the field you have
Each MoltSets tool is its own endpoint, so each gets its own HTTP Request node. 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": "{{ $json.linkedin_url }}" } # the LinkedIn URL from the previous noderesponse → the next node
{ "results": {
"email": "jane.smith@acme.com",→{{ $json.results.email }} Work email
"risk_score": "A",→{{ $json.results.risk_score }} A-F send grade
"last_validated_at": "2026-10-28"→{{ $json.results.last_validated_at }} Latest evidence
},
"status": "ok",→If node 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 trigger fires, add the work email and its grade before the lead is routed anywhere.
tool
linkedin_to_business_email -
02
MoltSets first in a waterfall
Put MoltSets first, then send only the items where
statusisn’tokto your next provider. Misses on MoltSets don’t cost anything.if node on
status -
03
LinkedIn contacts, straight in
The MoltSets Chrome extension can send every contact you save to a Webhook node, starting a workflow for each one.
trigger
Webhook -
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 server logs? Turn each one into the company behind it.
tool
ip_to_company
Before you run it on every item
-
01Keep the key in a credential
Don’t: Type your
ms_key into a header field on the node, where it travels with the workflow.Do: Use a Header Auth credential, so the key is stored once and every node reuses it.
-
02User-Agent is required
Don’t: Leave out the User-Agent header. MoltSets returns
403 Forbiddenwithout one.Do: Turn on Send Headers and add
User-Agentwith any value, such asn8n. -
03A miss isn’t an error
Don’t: Route on whether the node succeeded. A miss still succeeds, with HTTP
200and empty fields.Do: Add an If node on
status:okis a hit,not_foundis a free miss. -
04Pace big runs
Don’t: Fire hundreds of items at the node at once and hit the rate limit.
Do: Under Add Option → Batching, set Items per Batch and a Batch Interval.
What it costs
n8n calls run on your MoltSets plan, with the same data and limits as the API. A lookup that finds nothing isn’t charged. n8n bills for its own usage separately.
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 n8n
Every step is in the moltsets api reference.
There isn’t a dedicated node to install. The built-in HTTP Request node works with every MoltSets tool: set the method, URL, key and body, and the response comes out ready for the next node.
Yes. The HTTP Request node is part of n8n itself, so the same setup works on n8n Cloud and on a self-hosted instance.
Yes. n8n 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 workflow.
Usually a missing User-Agent header. MoltSets needs one on every request; any non-empty value works. Also check the credential’s value is Bearer, a space, then your key.
The call returns HTTP 200 with status set to not_found and empty fields in results. No tokens are charged. Add an If node on status to split hits from misses.
Use the HTTP Request node’s Batching option to send items in smaller groups with a pause between them. If you do reach your plan’s fair use window, the API returns 429 with the number of seconds until you can carry on. See rate limits.
Yes. Add a Webhook node set to POST, copy its Production URL into the MoltSets Chrome extension, and activate the workflow. Every contact you send arrives as the same flat JSON.
Not using n8n?
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.