start for free
start for free

Verified emails and mobiles in your Make scenarios

Call any MoltSets tool from Make’s HTTP app and map the results into the next module: work emails with an A-F risk score, mobiles, LinkedIn profiles and company data, on your own MoltSets plan.

http › make a request

example: linkedin_to_business_email

method
POST
URL
https://api.moltsets.com/api/v1/tools/linkedin_to_business_email
API key keychain
Key
Bearer ms_your_key
Placement
In the header
Parameter name
Authorization
headers
User-Agent
Make
body (JSON string)
{ "linkedin_url": "your mapped LinkedIn URL" }
parse response
Yes

one module per tool · no charge when nothing is found

what it is

MoltSets in Make

Make’s HTTP app can call any REST API with its Make a request module, and every MoltSets tool is a single POST request with the same response shape.

Add one module per tool, map its input from the module before, and turn on Parse response so results can be mapped into the module after. Store your key once in a keychain. Calls run on your MoltSets plan, the same as calling the API yourself.

What you can do

  • / 01Enrich every bundle in a scenario, from a form, a CRM watch module or a sheet
  • / 02Get a work email and its A-F risk score from a LinkedIn URL
  • / 03Filter on status: hits down one route, misses down another, and misses are free
  • / 04Map the results into your CRM, a sheet or Slack in the next module
setup

Connect MoltSets to Make

  1. 01

    Get an API key

    Sign up free at app.moltsets.com and create a key under API keys. Keys start with ms_.

  2. 02

    Add Make a request

    Add the HTTP › Make a request module after the one that has your data. Set Method to POST and URL to the tool’s endpoint from the API reference.

  3. 03

    Add your key

    Set Authentication type to API key and create a keychain with these values. Then add a User-Agent header under Headers, with any value, such as Make.

    Key: Bearer ms_your_key
    API key placement: In the header
    API key parameter name: Authorization
  4. 04

    Send the body

    Set Body content type to application/JSON and Body input method to JSON string. Paste the body, then map your LinkedIn URL from the earlier module into the value:

    { "linkedin_url": "your mapped LinkedIn URL" }
  5. 05

    Parse and map

    Set Parse response to Yes and run the module once. The response fields then show up to map in later modules, and a filter on status splits hits from misses:

    • results.email
    • results.risk_score
    • status
which tool

Pick the tool for the field you have

Each MoltSets tool is its own endpoint, so each gets its own Make a request module. Start from the field you already have. Not sure? I have X, I want Y covers every combination.

you have →you want ↓LinkedIn URLName + company domainEmail(s)Website visitor IP
Work email linkedin_to_business_email search_business_email_by_name · ·
Best email (work, else personal) linkedin_to_best_email · · ·
Mobile number linkedin_to_mobile_phone · · ·
LinkedIn profile · · email_to_linkedin ·
Send-safety grades · · validate_emails ·
Company · · · ip_to_company
example

A work email from a LinkedIn URL

request body · linkedin_to_business_email

{ "linkedin_url": "https://www.linkedin.com/in/jane-smith" } # in Make: map the URL from the earlier module

parsed response → later modules

{ "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": { ... }
}
use cases

What teams use it for

  1. 01

    Enrich new leads as they arrive

    When a form, CRM or sheet module picks up a lead, add the work email and its grade before it’s routed anywhere.

    tool linkedin_to_business_email

  2. 02

    MoltSets first in a waterfall

    Put MoltSets first, then filter so only bundles where status isn’t ok go on to your next provider. Misses on MoltSets don’t cost anything.

    filter on status

  3. 03

    LinkedIn contacts, straight in

    The MoltSets Chrome extension can send every contact you save to a Custom webhook, starting your scenario for each one.

    trigger Custom webhook

  4. 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

  5. 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

  6. 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

good to know

Before you turn the scenario on

  1. 01Keep the key in a keychain

    Don’t: Type your ms_ key into the Headers field, where it travels with the scenario.

    Do: Use the API key authentication type, so the key lives in a keychain you can reuse.

  2. 02User-Agent is required

    Don’t: Leave out the User-Agent header. MoltSets returns 403 Forbidden without one.

    Do: Add User-Agent under Headers with any value, such as Make.

  3. 03Parse the response

    Don’t: Leave Parse response off, and try to map fields out of raw text.

    Do: Set it to Yes and run the module once, so results shows up as fields to map.

  4. 04A miss isn’t an error

    Don’t: Treat a successful module as a hit. A miss still returns HTTP 200, with empty fields.

    Do: Add a filter on status: ok is a hit, not_found is a free miss.

pricing

What it costs

Make calls run on your MoltSets plan, with the same data and limits as the API. A lookup that finds nothing isn’t charged. Make 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

$0to start
Enrichment records1klifetime

Try before you commit, no card required.

get started
  • 1k data calls total
  • 100 search records total
  • Personal email included 

solo

$27/ month
Enrichment records1k/ 5 hours

For solo builders and small lists.

get started
  • Unlimited data
  • 500 search records / 5h
  • Personal email included 

pro MOST POPULAR

$97/ month
Enrichment records15k/ 5 hours

For teams enriching at scale.

get started
  • Unlimited data
  • 7.5k search records / 5h
  • Personal email included 

team

$397/ month
Enrichment records150k/ 5 hours

For teams that have outgrown the $97 limits.

get started
  • Unlimited data
  • 75k search records / 5h
  • Personal email: 75k / week 
help

Questions & answers about MoltSets in Make

Every step is in the moltsets api reference.

There isn’t a dedicated app. The built-in HTTP › Make a request module works with every MoltSets tool: set the method, URL, key and body, and parse the response for the next module.

In an API key keychain: the full value Bearer ms_your_key as the Key, placed in the header, with Authorization as the parameter name. Make recommends keeping credentials out of the Headers field.

Check Parse response is set to Yes, then run the module once. Make only shows the response fields to map after it has seen a real response.

Usually a missing User-Agent header. MoltSets needs one on every request; any non-empty value works. Also check the keychain’s Key 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 a filter on status to split hits from misses.

Yes. Make 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 scenario.

Yes. Start a scenario with Webhooks › Custom webhook, copy the webhook address into the MoltSets Chrome extension, and every contact you send arrives as the same flat JSON.

other ways to connect

Not using Make?

MoltSets Console - SIGN UP
SYS: ACCESS GRANTED

Get your API key

1,000 API calls, no card. Sign up and start calling the API today.