Resources · Claude connector

Claude Lusha connectorWhat Claude can do in your Lusha account.

The Claude Lusha connector exposes 24 tools. 23 of them read B2B data from Lusha, 0 change your account on the directory sheet, and 1 has no description anywhere. Below: what Claude can look up, what burns credits, and who keeps control.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes once Claude can query Lusha

Sales and RevOps teams jump between a prospecting database, a CRM and a chat window all day. With this connector, you ask Claude in plain words for the people or accounts you need, and it queries Lusha itself: contact and company data, prospect searches, buying signals, lookalikes and scored recommendations, all brought back into the conversation.

Prepare a call in one message. Before a discovery call, an account executive asks who the contact is and what the company does: Claude runs contacts_search and companies_search, then checks recent moves with signals_companies_get.

Build a prospect list from criteria. Claude first reads the filter values with prospecting_contact_filters, which costs no credits, then searches with prospecting_contact_search and reveals emails and phones only for the people you keep, through prospecting_contact_enrich.

Find more accounts like your best one. lookalike_companies starts from a seed company and returns similar ones, while website_visits_search shows which companies are visiting your site.

What it will not do from this sheet: by default, every documented tool reads, and none pushes records into a CRM or edits your Lusha lists. Enrichment spends credits from the same pool as Lusha's API. One tool on the sheet is described nowhere. For scheduled enrichment in the background, the Lusha Make integration covers a different job: running a scenario without you.

Vocabulary

Five words before you connect

The vocabulary Claude uses around this connector, quickly.

Connector
The link you set up once between Claude and an account you already own, so Claude can work in that account while it answers.
Tool
One named action a connector lets Claude take. Claude chooses the tools it needs by itself, and the directory lists each one by name.
Authorization
The login screen of the service itself, where you give Claude the access it will use. Granted once per person, and revocable.
Approval
The confirmation Claude waits for before doing something that changes your account, shown in the conversation when it matters.
MCP
The shared standard connectors are built on, which is what lets an assistant such as Claude talk to an outside service like Lusha.
Connect

Connect Lusha to Claude in three steps

  1. 01

    Find Lusha in Claude

    Open Claude's settings, go to Customize and then Connectors, and look for Lusha in the list. On a Team or Enterprise workspace, an Owner or Primary Owner switches the connector on before each member can sign in.

  2. 02

    Start the connection

    Click Connect on its row, then sign in to Lusha in the window Lusha opens. No key to paste: the login handles access. If the link breaks later, use Disconnect and connect again.

  3. 03

    Review the authorization screen

    Read the authorization screen before you accept. It belongs to Lusha, not to Claude, and it sets what the access covers. Lusha also shows a starter prompt there that you can copy for a first query.

Tools

The 24 tools, split by what they do

Lusha gives Claude 24 tools: 23 that read your account, 0 that change something in it, and 1 no official source describes.

Two groups here: what Claude reads from Lusha, and the one tool no official source describes. Tool names stay exactly as Claude displays them.

  • 23 read
  • 1 not documented

What Claude reads (23)

23 tools

Twenty-three tools that look up data and leave your account as it is. Some of them spend Lusha credits.

prospecting_contact_enrich

Takes contacts found by ID during prospecting and reveals their emails and phone numbers. Lusha states plainly that this step consumes credits.

When it helps
out of forty candidates, you keep eight and want their direct lines.
Watch out
ask Claude to confirm the shortlist first, since every reveal draws on your balance.

Sourcedocs.lusha.com · September 30, 2026 ↗

prospecting_company_enrich

Enriches companies already found during prospecting, by ID, with detailed firmographic data that the search results left out, so each account on a shortlist gets a fuller profile.

When it helps
ten accounts made your shortlist and you want the detailed firmographic profile of each before the call list is final.
Watch out
like other lookups, matched results can draw on credits.

Sourcedocs.lusha.com · September 30, 2026 ↗

prospecting_contact_filters

Lists the values available for contact prospecting filters, so Claude uses the exact seniority or department labels Lusha expects. No credits are charged for this call, whatever the number of values returned.

When it helps
Claude checks how Lusha names a VP level before running a search.

Sourcedocs.lusha.com · September 30, 2026 ↗

prospecting_company_filters

Returns the accepted values for company prospecting filters, free of credits, which keeps searches from failing on a misspelled industry or region.

When it helps
you ask for fintechs in the Nordics and Claude needs Lusha's own wording for both.

Sourcedocs.lusha.com · September 30, 2026 ↗

account_usage

Shows your credit balance, rate-limit status and plan information on the Lusha side, and it consumes no credits itself. Rate limits follow your Lusha plan, the same as for the API.

When it helps
before a large enrichment run, you want to know how many credits remain and how much headroom you have.

Sourcedocs.lusha.com · September 30, 2026 ↗

lookalike_companies

Starts from one seed company and returns others that look like it, a quick way to widen a target list from an account that already converted.

When it helps
your best customer is a regional retailer and you want ten more like it.

Sourcedocs.lusha.com · September 30, 2026 ↗

lookalike_contacts

Finds people who resemble a seed contact, useful when one profile keeps saying yes and you want more of the same kind of buyer in other companies.

When it helps
a certain kind of operations manager signs fast and you want others in comparable roles.

Sourcedocs.lusha.com · September 30, 2026 ↗

signals_contacts_get

Pulls the signals Lusha tracks for contacts you already hold, by ID, so Claude can tell you what is new about each person on a list you are working.

When it helps
checking whether anyone on your follow-up list recently took a new role or got promoted.
Watch out
it needs Lusha IDs, usually from an earlier search.

Sourcedocs.lusha.com · September 30, 2026 ↗

signals_contact_filters

Gives the filter values available for contact signals, with no credits charged, so Claude frames a signal search in Lusha's terms.

When it helps
you want to know which career events Lusha can filter on before asking for a list.

Sourcedocs.lusha.com · September 30, 2026 ↗

signals_companies_get

Returns the signals Lusha holds for companies you already know, by ID, so Claude can summarise what happened recently at each account on your list.

When it helps
a quick scan of your top accounts before the quarterly pipeline review.
Watch out
it works from IDs, not from company names.

Sourcedocs.lusha.com · September 30, 2026 ↗

signals_company_filters

Gives Claude the values usable in company signal searches, such as the kinds of events Lusha recognises, and charges no credits for it.

When it helps
Claude needs Lusha's exact label for a hiring surge before searching for accounts that show one.

Sourcedocs.lusha.com · September 30, 2026 ↗

purchase_options

Displays the Lusha plans and credit packs on offer, so Claude can tell you what topping up would look like.

When it helps
your balance is running low mid-campaign and you want the options in the chat.
Watch out
it shows options; no source says it buys anything.

Sourcedocs.lusha.com · September 30, 2026 ↗

recommendations_companies

Returns paginated, scored company recommendations with the signals behind them and the Target Profile each one matches.

When it helps
Monday planning, when you want the accounts Lusha ranks highest this week.
Watch out
it relies on Target Profiles set up in Lusha's ICP Hub.

Sourcedocs.lusha.com · September 30, 2026 ↗

recommendations_companies_filters

Returns the valid signal types and Target Profiles you can use to narrow company recommendations, so Claude filters on options that really exist in your account.

When it helps
you keep two ideal customer profiles and want recommendations for only one of them.

Sourcedocs.lusha.com · September 30, 2026 ↗

recommendations_contacts

Delivers paginated, scored people recommendations, each with its signals and the Target Profile it fits.

When it helps
an SDR wants a ready list of people to reach this week, ranked by fit.
Watch out
Lusha refreshes recommendations daily, so tomorrow's list may differ.

Sourcedocs.lusha.com · September 30, 2026 ↗

recommendations_contacts_filters

Provides the signal types and Target Profiles accepted when filtering people recommendations, which lets Claude narrow a ranked list without guessing labels.

When it helps
you only want contacts flagged by a new job within your mid-market profile.
Watch out
the profiles come from your own ICP Hub setup.

Sourcedocs.lusha.com · September 30, 2026 ↗

Undocumented (1)

1 tool

The directory publishes this name and nothing more. No official text says what it does, and we will not guess it from its name.

Approvals

What Claude checks with you first

By default, Claude stops and asks before each action it takes on an account on someone's behalf, with the prompt shown in the conversation.

On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked every time. They can also restrict what a connector does for the whole organization, for instance keeping reading and closing writing, and nobody lifts that from a personal account. Claude works with the rights of the person who connected, nothing more. With Lusha, the practical risk is not a changed record but spent credits, so ask Claude to show a shortlist before any enrichment.

Plans

Which plans include it

None of the 819 sheets in the official directory shows plan availability, so the answer for Lusha is published nowhere.

Anthropic publishes the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector before members connect one by one. For the live state of Lusha on your account, open its sheet in the official directory.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you, so nothing is enriched on its own when a lead arrives.

This connector is documented by its publisher only: no page of Claude's help center covers it. A reading-only list is an observed floor, not a guarantee, since an administrator can open actions that no public sheet shows. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose the tools a publisher exposes nor guarantee how they behave. Lusha itself warns that its tool names and behaviour can shift as it ships new capabilities. The Integrations hub lists other ways to plug Lusha into your stack.

Need help

Need help connecting Lusha to Claude?

A person reads every message.

FAQ

Questions about the Claude Lusha connector

01What can Claude do with the Lusha connector?
Claude can look up and qualify B2B contacts and companies in Lusha from a conversation. Its tools cover direct lookups by email, domain or name, prospect searches with filters, enrichment that reveals emails and phones, buying signals, lookalikes, scored recommendations, website visitors, and your credit balance. Twenty-three tools are documented by Lusha, all on the reading side, and one more on the sheet has no description anywhere. Enrichment and some searches consume Lusha credits.
02Can Claude change anything in my Lusha account?
Not with the documented tools on the directory sheet: by default, all of them read data. None pushes contacts to a CRM or edits a list. What does change is your credit balance, because enrichment consumes credits from the same pool as Lusha's API. Lusha also warns that tool names and behaviour can change as it ships new capabilities, and a reading-only list remains a floor rather than a guarantee.
03Does Claude ask before it spends Lusha credits?
By default, Claude asks for confirmation before each action it takes on an account for someone. No source describes a confirmation specific to the enrichment tools, so that general rule is what applies. In practice, ask Claude to show the shortlist and check your balance with the usage tool before revealing contact details. On Team and Enterprise workspaces, owners can also narrow what the connector does for the whole organization.
04Which Claude plans can use the Lusha connector?
No official source publishes plan availability connector by connector, and none of the directory's sheets shows it. Anthropic's general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise. On the Lusha side, the plan must include API access. The directory sheet on your account shows the current state. Check it there.
05Does Claude see all of our Lusha data?
It works with the rights of the connected person. Recommendations, for instance, are drawn from that user's own Target Profiles plus any shared account-level ones, with identity taken from the session rather than typed in. A colleague with other profiles gets other rankings. On top of that, an owner of a Team or Enterprise workspace can restrict the connector for the whole organization, and members cannot lift that restriction themselves.
06Why do my recommendations look empty or generic?
Most likely because no Target Profile is set up yet. Lusha draws recommendations from your Target Profiles in its ICP Hub and nudges you to create one with each request until you do. Once a profile exists, recommendations refresh daily and recalculate within minutes of a profile change. You can then use the filter tools to pick which profile and which signal types Claude should rank against. That is when the ranking becomes useful.
07Should I use Claude or an automation tool with Lusha?
They serve different needs, so choose by the job. Claude works inside a conversation: you describe who you are looking for, it searches and enriches, and nothing happens once you stop. It does not enrich new leads automatically as they arrive. If you want every new signup enriched in the background, that is an automation tool's job. For research before a call or building a list on demand, the connector fits.