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
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.
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 Lusha to Claude in three steps
- 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.
- 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.
- 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.
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
Tools index
- contacts_search
- companies_search
- prospecting_contact_search
- prospecting_contact_enrich
- prospecting_company_search
- prospecting_company_enrich
- prospecting_contact_filters
- prospecting_company_filters
- account_usage
- lookalike_companies
- lookalike_contacts
- signals_contacts_get
- signals_contacts_search
- signals_contact_filters
- signals_companies_get
- signals_companies_search
- signals_company_filters
- purchase_options
- recommendations_companies
- recommendations_companies_filters
- recommendations_contacts
- recommendations_contacts_filters
- website_visits_search
What Claude reads (23)
23 toolsTwenty-three tools that look up data and leave your account as it is. Some of them spend Lusha credits.
contacts_search
Enriches a known person from an email, a LinkedIn URL or a name plus company, and returns the contact data Lusha holds on them.
companies_search
Retrieves company data from a domain or a company name, so Claude can describe an account before anyone opens a browser tab.
prospecting_contact_search
Searches Lusha's database for people matching criteria such as job title, seniority, location or department, returning candidates rather than full contact details.
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.
prospecting_company_search
Finds companies matching firmographic and technographic filters, such as industry, headcount or the tools they run, and returns a list Claude can sort or shorten with you.
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.
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.
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.
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.
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.
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.
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.
signals_contacts_search
Searches for people based on trigger events such as promotions or job switches, rather than on a static profile, so the list follows what just changed for each person.
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.
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.
signals_companies_search
Finds accounts through trigger events such as funding rounds, hiring surges or headcount growth, instead of searching on fixed company attributes alone.
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.
purchase_options
Displays the Lusha plans and credit packs on offer, so Claude can tell you what topping up would look like.
recommendations_companies
Returns paginated, scored company recommendations with the signals behind them and the Target Profile each one matches.
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.
recommendations_contacts
Delivers paginated, scored people recommendations, each with its signals and the Target Profile it fits.
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.
website_visits_search
Shows which companies are visiting your website, turning anonymous traffic into named accounts that Claude can then research with the other lookup tools.
Undocumented (1)
1 toolThe directory publishes this name and nothing more. No official text says what it does, and we will not guess it from its name.
decision_makers_search
This name sits in the directory's tool list, but Lusha's tool reference does not include it and no Claude page describes it, so this page says nothing about what it does.
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.
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.
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 connecting Lusha to Claude?
A person reads every message.

