Make.com lead enrichment with the Leadsets API

For lead enrichment in Make.com with Leadsets, call the Leadsets REST API from Make's HTTP module with a bearer API key. A workflow can search people and companies, enrich a person with a verified work email when one exists, enrich a company domain and verify emails. Leadsets is flat priced from $29 a month, with 1,000 free records to start and no phone numbers yet.

What you can do with Leadsets in Make

Make is a workflow automation platform. The Leadsets integrations page lists Make as connecting through its HTTP module, which calls the Leadsets REST API at https://api.leadsets.ai/v1. The site does not describe a separate Leadsets app for Make, so everything on this page uses plain HTTP requests.

Through those requests a workflow can use the same tools an agent gets over MCP:

POST /v1/people/search and POST /v1/companies/search to find people and accounts by title, seniority, function, company size, industry and country. Every result says why it matched.
POST /v1/people/enrich for current role, company and a verified work email when one exists.
POST /v1/companies/enrich for firmographics on a domain, with source and freshness on every field.
POST /v1/emails/verify to check one address or a batch. Each comes back verified, catch-all, unknown or invalid with a confidence score.
POST /v1/scrape/company and POST /v1/scrape/jobs to turn a homepage or careers page into structured fields. Scraping is a units add-on on paid plans and is not on Free.
GET /v1/usage to read every meter and reset time before a run. It costs nothing.

How to connect Leadsets to Make

The Leadsets site gives no Make-specific setup beyond naming the HTTP module, so these are the generic REST steps from the Leadsets docs. Check Make's own documentation for where each setting goes.

Get a key. Create a free Leadsets account and copy your API key from the dashboard. Keys start with ls_live_ and should be kept server-side, so treat it as a secret. The free plan gives 1,000 records once, with no card.
Build the request. Method POST, the endpoint URL you need (for example https://api.leadsets.ai/v1/people/search), the header Authorization: Bearer ls_live_… and a JSON body.
Add an idempotency key. Send an Idempotency-Key header on paid calls, built from something stable such as a row ID. A retry with the same key returns the first result and never counts records twice. Keys last 24 hours.
Read the response. Every response is JSON with items, next_cursor for the next page, a usage object showing what was counted and what is left, and a request_id to send to support if something looks wrong.
Test small. Start with limit set low, then raise it (1 to 100, default 25). The quickstart shows a first call and response.

A people search body, as documented in the API reference:

{
  "title": ["VP Sales"],
  "country": ["US"],
  "employees": "50-200",
  "has_verified_email": true,
  "limit": 25
}

MCP and skills. The remote MCP server at https://mcp.leadsets.ai and the 50 free SKILL.md skills are built for agents such as Claude, ChatGPT and Cursor; the site lists Make under the REST API, not MCP. If part of your process runs in an agent, a skill such as Build an outbound prospect list can export a verified list to CSV or Google Sheets for a later workflow to use.

CSV. Leadsets supports CSV and Excel import and export, so you can also move lists between Leadsets and your workflows as files instead of live calls.

Example: routing inbound demo requests at Northwind Analytics

Maya Chen runs revenue operations at Northwind Analytics (northwind.co). Demo requests arrive with a name and a company, and she wants each one enriched and routed before a rep sees it.

Her Make workflow, step by step:

A new demo request starts the workflow, from the source her team already uses.
An HTTP request to /v1/people/enrich sends the person's details. On a match, Leadsets returns current role, company and a work email that has already been through the verification waterfall, so no separate verify call is needed.
An HTTP request to /v1/companies/enrich sends the company domain and adds firmographics such as industry and headcount band.
The workflow routes on the email status: verified goes to sales, catch-all goes to a lower-volume sequence, unknown is held for review. A 404 not_found means there was nothing to enrich, so the lead moves on unenriched without using records.

On Solo ($29 a month), each lead uses up to two enrichment records (one person, one company) against 1,000 per five hours and 5,000 per week. The same pattern works for outbound: a scheduled search for VP Sales at 50 to 200 person US companies with has_verified_email set to true, paged with next_cursor.

What to watch for

Records and requests. A record counts only when data comes back; an empty search uses none. Every call counts as one request, and the request limit is five times the record allowance. See limits and costs for each plan.
Five-hour and weekly windows. Over a limit, Leadsets returns 429 with a Retry-After header, and the blocked call counts against nothing. Retry window_full and too_many_concurrent after waiting; resume weekly_limit after resets_at. Do not retry 400, 401, 402, 403, 404 or 409. The errors guide covers each type.
Concurrency. Solo allows 3 concurrent searches, Pro 5, Team and Max 8. Workflows that fan out many searches at once will see 429 too_many_concurrent.
Free records. When the 1,000 free records are used, calls return 402 free_records_exhausted.
Verification labels. Verified means the mailbox accepts mail. Catch-all means the domain accepts everything, so send at lower volume; read what a catch-all email is. Unknown is unconfirmed. Invalid emails are never served as contact emails.
Avoid double verification. Emails from enrich_person are already verified. Standalone verify_email calls count toward the enrichment limit.
Big lists. Bulk verification runs as an async job on paid plans: you get a job ID, check GET /v1/jobs/{id}, and webhooks can deliver results.

What this integration does not do

No phone numbers. Leadsets returns work emails, US personal emails on paid plans, roles and company data. If phone numbers are essential, use a provider that offers them.
Not a CRM or sending tool. Leadsets feeds HubSpot, Salesforce, Pipedrive, Attio and sequencers such as Instantly and Smartlead; it does not send email itself.
Business data only. No consumer data, sensitive categories or home addresses.
No Make-specific app or templates are described on the Leadsets site. If you want a documented recipe, the n8n integration has one.
Fair use applies. One account per company, no sharing a key across separate companies or customers, and embedding Leadsets data in a product you sell needs a written agreement.
SOC 2 is planned, not done. SOC 2 Type I readiness is underway with a target of Q3 2027.

Questions and answers

Is there a native Leadsets app for Make?

The Leadsets site lists Make as connecting through its HTTP module, which calls the Leadsets REST API. No separate Leadsets app or template for Make is described, so setup uses standard HTTP requests with a bearer key.

How do I authenticate Leadsets requests from Make?

Send your Leadsets API key as a bearer token in the Authorization header, for example Authorization: Bearer ls_live_…. Keys come from the Leadsets dashboard after creating a free account and should be kept server-side.

How many Leadsets records does a Make workflow use?

One record per person or company returned with data, so an empty search or a 404 not_found uses none. Every call still counts as one request, and the request limit is five times the record allowance.

Can Make use the Leadsets MCP server?

The Leadsets site lists Make under the REST API, not MCP. The remote MCP server at https://mcp.leadsets.ai is for MCP clients such as Claude, ChatGPT and Cursor, and exposes the same eight tools.

What happens when a Make workflow hits a Leadsets limit?

Leadsets returns a 429 with a Retry-After header and a machine-readable error type, and the blocked call counts against nothing. Wait and retry for window_full or too_many_concurrent, and resume weekly_limit after the reset time.

Does Leadsets return phone numbers to Make workflows?

No. Leadsets does not offer phone numbers yet; it returns work emails, US personal emails on paid plans, roles and company data. It will only add phone numbers once sourcing rights and costs are clear.

Go deeper

More integrations