TL;DR: Lusha is now a connector in Claude. Research accounts, find decision makers, and enrich contacts directly inside your Claude conversations — no more switching tabs between the AI helping you write and the database holding the data.
We’re announcing that Lusha is now available as a connector in Claude.
A lot of GTM work already happens in Claude — account research, ICP analysis, outbound drafts, call summaries, positioning tests. But AI has always had a data problem. It can write a sharp cold email; it just didn’t know who to send it to.
Contact data lived in a different tab, a different tool, a different workflow. You’d pull a list in one place, research the company in another, then come back to Claude to draft the outreach.
With the Lusha connector, that whole loop now runs inside one conversation.
Bring verified Lusha data into Claude
The connector gives Claude direct access to Lusha’s B2B dataset — built from community contributions, proprietary collection systems, and vendor partnerships, not scraping.
- 300M+ verified business contacts
- 30M+ company profiles worldwide
- 1.2B+ data points processed every day
- 7M+ new signals added every week (hiring, funding, job changes, growth)
Every record runs through continuous validation. Email verification reaches 98% in North America, 97% in EMEA, 96% in APAC, and 95% in LATAM. 90%+ of direct dials are validated before delivery.
Compliance travels with the data: GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
Learn more about Lusha’s data →
From fifteen tabs to one conversation
Research shows reps spend up to 40% of their week just finding someone to call. The standard loop looks like this:
Open database → set filters → export CSV → clean list → switch to LinkedIn → cross-reference → open AI tool → paste context → draft email
With Lusha in Claude, the loop collapses:
Ask Claude → Lusha returns verified data → Claude drafts, scores, or summarizes in the same thread
No API keys in prompts. No exports. No context-switching. The connector runs as a native tool Claude can reach for whenever your question needs real B2B data instead of a guess.
Discover companies that match your ICP
Lusha in Claude lets you describe the companies you want to reach — in plain English — and get back a real list.
Prompt example:
“Find 25 Series B-to-C fintech companies in the UK with 100–500 employees that have raised funding in the last 12 months.”
Claude interprets the request, the Lusha connector applies firmographic and funding filters, and you get back companies you can act on without opening a separate prospecting tool.
Find decision makers with verified contact data
Once the accounts are identified, the next step is the people.
Lusha enriches contacts with:
- Verified work emails
- Direct phone numbers
- Role and seniority
- Company firmographics and tech stack
Prompt example:
“For each of these 10 companies, find the VP of Revenue Operations. Return verified work email, direct dial, LinkedIn, and tenure.”
One prompt → a list of reachable decision makers, validated at query time.
Prioritize outreach with real-world signals
Lusha doesn’t just return static profiles. The connector brings company-level context into the conversation so Claude can help prioritize — not just list.
Prompt example:
“Pull the last 90 days of hiring, funding, and leadership changes for these 15 accounts. Rank them by signal density and tell me which three I should reach out to this week.”
Claude uses the Lusha data to score, sort, and explain the reasoning — so outreach happens when there’s a clear reason to engage, not on a Tuesday because your sequence said so.
Real workflows you can run with Lusha in Claude
Example 1: Research → prospect → draft in one thread
“Find 10 Heads of Data at Series B SaaS companies in New York that use Snowflake. Return verified emails and direct dials. Then draft a 4-line cold email to each, referencing their company’s most recent hiring activity.”
List building + enrichment + personalized drafting — one prompt, one thread.
Example 2: Signal-triggered personalization
“Acme just announced a Series B. Use Lusha to find their VP of Sales. Based on their past company and the raise, draft an outbound email about the scaling problems they likely face now.”
The signal drives the timing. Lusha delivers the contact. Claude writes with context.
Example 3: Inbound list enrichment
“Here are 25 company domains from yesterday’s webinar signups. Enrich with headcount, industry, revenue range, and tech stack. Flag the ones that match our ICP and draft follow-up emails for the top 5.”
Raw signup list → scored pipeline → ready-to-send outreach, without opening a spreadsheet.
Example 4: Lookalike + ICP analysis
“Look up these 5 closed-won accounts. What firmographic patterns do they share? Then find 20 companies with similar profiles and enrich the top decision maker at each.”
Start from your best customers, end with a prospect list — all in one chat.
Who this is for
- SDRs doing account research before a call
- AEs prepping for discovery without eight open tabs
- RevOps teams running ad hoc enrichment and ICP analysis
- Marketers scoring and enriching inbound leads
- Founders doing early ICP discovery without buying a full prospecting stack
If you already use Claude for GTM work, the connector plugs into the workflow you have. If you’re new to Lusha, this is the lowest-friction way to see what verified B2B data does to an AI conversation.
Start using Lusha in Claude
The connector is live now in Claude (web and desktop).
- Existing Lusha customers with API access: turn it on in Claude’s connector settings.
- New to Lusha: start a free trial and connect it once you have API access.
Connect Lusha in Claude → · Full setup guide →
Read more
Search and enrich companies, search and enrich contacts, and run prospecting queries with firmographic and role-based filters — all through natural language in a Claude conversation.
The native connector authorizes once inside Claude and stays available across your chats — no local config file, no API key pasted into JSON, no npx install. If you already set up the Desktop MCP path, the connector replaces it with a one-click setup.
Yes. The connector uses the same credit pool as the Lusha API. Search queries are low-cost discovery; enrichment (revealing an email or phone) is charged per data point revealed — same model you already use.
Yes. All Lusha data meets GDPR, CCPA, and SOC 2, with ISO 27701 and ISO 31700 certifications. Geographic restrictions on your Lusha account carry through — restricted fields return null rather than unverified data.
No. The connector pulls directly from Lusha’s verified database. Claude doesn’t generate, invent, or modify the records — what you see in the chat is what exists in Lusha.
Lusha API access is required. That’s available on the Scale plan and above — see pricing.
