--- title: "n8n lead enrichment with Leadsets: HTTP node setup" description: "Use Leadsets in n8n for lead enrichment: call the REST API from an HTTP node to search, enrich and verify B2B contacts. Setup steps, limits and an example." canonical: https://www.leadsets.ai/integrations/n8n updated: 2026-11-09 --- # n8n lead enrichment with Leadsets Leadsets connects to n8n through its REST API. An n8n HTTP node calls https://api.leadsets.ai/v1 with a bearer API key to search people and companies, enrich contacts and verify work emails. A free, open-source skill describes an inbound lead enrichment recipe. Plans are flat monthly from $29 with 1,000 free records to start. Leadsets has no phone numbers yet. n8n is a workflow automation tool. Leadsets works with it through the Leadsets REST API: the Leadsets integrations page lists n8n under automation, connected with an **HTTP node and a recipe**. This page covers what a workflow can do, how to connect it, one example and what to watch for. ## What you can do with Leadsets in n8n Every Leadsets tool is also a REST endpoint, so a workflow can call any of them from an HTTP request: - `POST /v1/people/search`: find people by title, function, seniority, location, company size and industry. Every result says why it matched. - `POST /v1/companies/search`: find accounts by industry, headcount band, technology and location. - `POST /v1/people/enrich`: current role, company and a verified work email when one exists. - `POST /v1/companies/enrich`: firmographics for a domain, with source and freshness on every field. - `POST /v1/emails/verify`: the verification waterfall on one address or a batch. - `POST /v1/scrape/company` and `POST /v1/scrape/jobs`: a homepage or careers page as structured data (scrape units, paid plans only). - `GET /v1/usage`: every meter and reset time, at no cost. - `GET /v1/jobs/{id}`: status of an async batch or scrape. Typical uses are enriching inbound leads as they arrive, backfilling missing emails, cleaning a list before it goes to a sequencer, and flagging target accounts that are hiring. ## How to connect Leadsets to n8n The Leadsets site does not document n8n-specific screens or settings. The steps below are the generic REST setup from the Leadsets docs, applied to an HTTP request. Use n8n's own documentation for where each value goes in the node. 1. **Get an API key.** Create a free Leadsets account and copy the key from the dashboard. Keys start with `ls_live_`, and the docs say to keep them server-side. 2. **Set the URL.** Use the base URL `https://api.leadsets.ai/v1` plus the route you need: POST for search, enrich, verify and scrape, GET for usage and jobs. 3. **Authenticate.** Send the header `Authorization: Bearer ls_live_…`. 4. **Send a JSON body.** For example, a people search: `{"title": ["VP Sales"], "country": ["US"], "employees": "50-200", "has_verified_email": true, "limit": 25}`. The [quickstart](https://www.leadsets.ai/docs/quickstart) has more examples. 5. **Make retries safe.** Add an `Idempotency-Key` header on paid calls. A retry with the same key returns the first result and never counts records twice. Keys last 24 hours. 6. **Read the response.** Each response returns `items`, `next_cursor` for the next page, a `usage` object with what was counted and what is left, and a `request_id` to send to support if something goes wrong. **Skill.** For a ready-made recipe, the free "n8n inbound lead enrichment" skill in the [skills library](https://www.leadsets.ai/skills/all) enriches every new form fill in n8n with `enrich_person` and `enrich_company` and routes good-fit leads to sales. Skills are MIT-licensed SKILL.md playbooks; clone them with `git clone github.com/leadsets/leadsets-skills`. **MCP.** Leadsets also runs a remote MCP server at `https://mcp.leadsets.ai`, but the integrations page lists n8n under the REST API, not MCP. MCP is the route for agents such as Claude (Customize, Connectors, + Add, Add custom connector, name it Leadsets, paste the URL, sign in with OAuth), Cursor or ChatGPT. **CSV.** Leadsets supports CSV and Excel import and export, and any sequencer can take a CSV export. ## Example: enriching inbound form fills Maya Chen runs revenue operations at Northwind Analytics (northwind.co). She wants every demo request enriched before a rep sees it. Her workflow follows the shape of the inbound lead enrichment skill: 1. A new form fill starts the workflow with the submitter's name, company and email. 2. An HTTP request calls `POST /v1/people/enrich` for current role, company and a verified work email when one exists. Leadsets skills describe enriching from a name plus company or from a LinkedIn profile URL. 3. A second request calls `POST /v1/companies/enrich` with the company domain for industry, headcount band, location and stack. 4. A branch reads the email status: **verified** goes to sales, **catch-all** goes to a lower-volume queue, **unknown** is held as unconfirmed. 5. Good-fit leads route to sales in whatever system the team already uses. When a submitter from Stackfold returns nothing, the API answers `404 not_found`. That uses no records, and the workflow should move on rather than retry. On Solo, each lead that returns both a person and a company uses two enrichment records, against 1,000 per five hours and 5,000 per week. ## What to watch for - **Records and requests.** Records count only when data comes back; every call counts as a request, hit or miss. The request limit is five times the record allowance. - **Windows.** Search and enrichment each have a rolling five-hour window and a weekly limit. Enrichment per five hours: Solo 1k, Pro 15k, Team 150k, Max 225k. Full numbers are on the [pricing page](https://www.leadsets.ai/pricing) and in [limits and costs](https://www.leadsets.ai/docs/limits). - **429 responses.** `window_full` and `too_many_concurrent` mean wait for `Retry-After`, then retry. `weekly_limit` means resume after `resets_at` or use an async job. Concurrent searches are 3 on Solo, 5 on Pro and 8 on Team and Max. Do not retry 400, 401, 402, 403, 404 or 409; see [errors and retries](https://www.leadsets.ai/docs/errors). - **Free plan.** 1,000 records, one time, shared across search and enrichment. When they run out the API returns `402 free_records_exhausted`. Scraping is not on Free. - **Verification.** Emails from `enrich_person` are already verified at no extra charge, so a separate verify call is not needed. Standalone `verify_email` counts toward enrichment. Labels are verified, catch-all, unknown or invalid, and invalid emails are never served as contacts; see [email verification](https://www.leadsets.ai/verify). ## What this integration does not do - **No phone numbers.** Leadsets returns work emails, US personal emails on paid plans, roles and company data. - **Not a CRM or sending tool.** Leadsets feeds the CRM or sequencer you already use. - **Business data only.** No consumer data, sensitive categories or personal home addresses. - **No dedicated node described.** The Leadsets site describes the n8n connection as an HTTP node plus a recipe. - **SOC 2 not yet.** SOC 2 Type I is planned, with readiness underway and a target of Q3 2027. - **One account per company.** Sharing one key across separate companies or customers is not allowed under the fair use policy. ## Questions and answers ### How do I connect Leadsets to n8n? Call the Leadsets REST API at https://api.leadsets.ai/v1 from an n8n HTTP node, with your API key in an Authorization: Bearer header. Keys start with ls_live_ and come from the Leadsets dashboard after a free signup. The Leadsets site does not document n8n-specific settings, so configure the node with n8n's own documentation. ### Is there a ready-made n8n recipe for lead enrichment? Yes. Leadsets publishes a free, MIT-licensed skill called n8n inbound lead enrichment that enriches every new form fill in n8n with enrich_person and enrich_company and routes good-fit leads to sales. It is part of the 50-skill library at github.com/leadsets/leadsets-skills. ### How much does it cost to enrich leads in n8n with Leadsets? Leadsets has a free plan with 1,000 one-time records and no card, then flat monthly plans in USD: Solo $29, Pro $99, Team $399 and Max $999. There are no credits; each plan has fair-use limits per five hours and per week, and records only count when data comes back. ### Do I pay extra to verify emails in an n8n workflow? Not for emails returned by enrich_person, which are already verified with no second bill. Standalone verify_email calls count toward the enrichment limit. Every email is labelled verified, catch-all, unknown or invalid. ### What happens when an n8n workflow hits a Leadsets limit? Leadsets returns a 429 with a Retry-After time and a machine-readable error type, and the blocked call counts against nothing. The workflow can call GET /v1/usage, which is free, before a large run to check what is left. ### Can n8n use the Leadsets MCP server? The Leadsets integrations page lists n8n under the REST API with an HTTP node, not under MCP. The remote MCP server at https://mcp.leadsets.ai is the route for agents such as Claude, Cursor and ChatGPT. Both expose the same eight tools. --- Leadsets · https://www.leadsets.ai · Site index: https://www.leadsets.ai/llms.txt