Pipedrive lead enrichment with Leadsets

Leadsets works with Pipedrive through free skills and its REST API. An agent in Claude, Cursor or any MCP client, or a workflow calling https://api.leadsets.ai/v1, can enrich Pipedrive leads with current role, company and a verified work email, add company firmographics and flag stale records. Plans are flat monthly prices from $29, with 1,000 free records to start and no card.

What Leadsets does with Pipedrive

Pipedrive is a sales CRM. Leadsets lists it on its integrations page as a CRM it works with through skills and the API. That means an agent or workflow uses Leadsets data to fill and refresh the records you keep in Pipedrive:

Enrich new leads. The free Pipedrive lead enrichment skill enriches new Pipedrive leads with role, company and a verified email, using enrich_person and enrich_company.
Flag stale records. The Stale record audit skill flags contacts whose title or company is out of date before reps waste a sequence on them. It uses enrich_person and lists HubSpot, Salesforce and Pipedrive as connections.
Backfill emails and enrich companies. Leadsets says an agent can backfill missing emails, enrich companies and flag stale records in HubSpot, Salesforce, Pipedrive and Attio.
Check addresses before a sequence. verify_email returns verified, catch-all, unknown or invalid with a confidence score.

Every field Leadsets returns carries its source, the date it was last checked and a confidence level, so the agent (and you) can decide what to write into the CRM.

How to connect it

The Leadsets site does not document Pipedrive-specific setup steps, menus or settings, so the steps below are the generic MCP, REST, skill and CSV setup from the Leadsets docs. How your agent or workflow reads from and writes to Pipedrive depends on your own setup.

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. The free plan gives 1,000 records once, with no card.
Connect your agent over MCP. In Claude on the web or desktop, open Customize, Connectors, click + Add, then Add custom connector. Name it Leadsets, paste https://mcp.leadsets.ai as the MCP server URL, click Continue, choose Sign in now, click Add and sign in. It uses OAuth, so there is no key to paste. In a chat, click +, Connectors and switch Leadsets on. In Claude Code, run:

claude mcp add --transport http leadsets https://mcp.leadsets.ai

In Cursor, add a server named leadsets with the URL https://mcp.leadsets.ai and an Authorization: Bearer header containing your key. The full steps are in the MCP docs. 3. Check the connection. Ask your agent "What's my Leadsets usage?" If it calls get_usage and answers with your remaining balance, you are connected. 4. Add the skill. Download the Pipedrive lead enrichment skill folder and upload it in Claude, Settings, Skills, or clone the whole library with git clone github.com/leadsets/leadsets-skills. It sits with the other CRM hygiene playbooks in the full skills list. 5. Or call REST from a workflow. From your own code, an n8n HTTP node or a Make HTTP module, call POST /v1/people/enrich and POST /v1/companies/enrich on https://api.leadsets.ai/v1 with your key as a bearer token. The TypeScript and Python SDKs install with npm i @leadsets/sdk or pip install leadsets and retry 429s for you. 6. Or work from a file. Leadsets imports and exports CSV and Excel, and the Bulk enrich a CSV skill enriches a whole file as an async job, checking your limits before each batch.

Example: new leads at Northwind Analytics

Maya Chen runs revenue operations at Northwind Analytics (northwind.co). Her team keeps inbound leads in Pipedrive, and each week about 200 arrive with a name and company but no title or verified email. With Leadsets connected to Claude and the skill installed, she asks:

"Enrich this week's new Pipedrive leads with current role, company and a verified work email. Put catch-alls in a separate list."

The agent, following the skill:

Calls get_usage, which is free, to confirm the run fits the current window.
Calls enrich_company once per distinct domain, such as the leads from Stackfold and Parcelry, adding firmographics with source and freshness on every field.
Calls enrich_person for each lead. Emails it returns are already verified, so there is no second tool and no second bill.
Returns the results split by label: verified, catch-all and unknown. Invalid addresses are never served as contact emails.

On the Solo plan, 200 people plus, say, 120 company domains is at most 320 enrichment records, inside Solo's 1,000 per five hours and 5,000 per week. Leads with nothing to enrich come back as 404 not_found, use no records, and the agent moves on. These numbers are illustrative.

What to watch for

Records and requests. A record counts only when data comes back; every call counts as one request, hit or miss. The request limit is five times the record allowance. See limits and costs.
Enrichment limits. enrich_person, enrich_company, standalone verify_email and US personal email lookups all count toward enrichment. Solo allows 1,000 per five hours and 5,000 per week; Pro 15,000 and 75,000; Team 150,000 and 750,000; Max 225,000 and 1,125,000. Compare plans on the pricing page.
Hitting a limit. Leadsets returns 429 window_full with a Retry-After time, or weekly_limit with a reset time, and the blocked call counts against nothing. When free records run out you get 402 free_records_exhausted, which should not be retried.
Retries. Send an Idempotency-Key on every paid call so a retry never counts records twice. Keys last 24 hours.
Verification labels. Verified means the mailbox accepts mail. Catch-all means the domain accepts everything, so send at lower volume; read more on catch-all emails. Unknown means the server gave no clear answer, so treat it as unconfirmed. Leadsets never rounds either up to valid.
Outreach law. You remain responsible for the laws that apply to your outreach, such as CAN-SPAM, GDPR and CASL, and for honouring unsubscribes.

What it does not do

No phone numbers. Leadsets returns work emails, US personal emails on paid plans, roles and company data. Phone numbers are not offered yet.
Not a CRM or a sending tool. Leadsets feeds Pipedrive and your sequencer; it does not replace them.
No documented Pipedrive-specific setup. The site describes the connection as skills plus API and does not document Pipedrive screens, field mappings or a sync schedule.
Business data only. No consumer data, sensitive categories or personal home addresses.
No accuracy guarantee. Leadsets publishes its benchmark method and does not promise 100%.
Scraping is separate. scrape_company and scrape_jobs are a paid add-on in units and are not on the free plan.

Questions and answers

Does Leadsets integrate with Pipedrive?

Yes. Leadsets lists Pipedrive as a CRM it works with through free skills and its REST API. An agent can enrich new leads, backfill missing emails, enrich companies and flag stale records.

What does the Leadsets Pipedrive lead enrichment skill do?

It enriches new Pipedrive leads with role, company and a verified email. It calls enrich_person and enrich_company, and it is free, open source and MIT licensed.

How many Leadsets records does enriching a Pipedrive lead use?

One enrichment record per person or company returned with data, and empty results use no records. Every call still counts as one request, and emails from enrich_person are already verified at no extra charge.

Does Leadsets add phone numbers to Pipedrive contacts?

No. Leadsets does not offer phone numbers yet. It returns work emails, US personal emails on paid plans, roles and company data.

How do I install the Pipedrive lead enrichment skill?

Download the skill folder and upload it in Claude, Settings, Skills, or clone the library with git clone github.com/leadsets/leadsets-skills. The skills work on the free Leadsets key with its 1,000 one-time records.

Should I add catch-all emails to Pipedrive?

Leadsets labels catch-all addresses separately and suggests sending to them at lower volume rather than dropping them. Unknown addresses should be treated as unconfirmed, and invalid ones are never served as contact emails.

Go deeper

More integrations