> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Lusha in Deepline

> Use for B2B email + direct dial enrichment by LinkedIn URL, email, or name+company. Includes inputs, outputs, SDK V2 examples, and Deepline cost.

[Human guide: work with your agent →](https://deepline.com/docs/human/providers/lusha/guide.md)
Inspect one Lusha action before starting provider-backed work. Your first result is a verified input and output contract.

## Provider-specific requirements

### When to use

Lusha for B2B email + direct dial enrichment. Strong North American and European coverage with intent signal data. Good for sales prospecting workflows where direct dials matter. Cost-competitive per enriched contact.

Connect the workspace's own Lusha API key in Dashboard → Integrations before calling a Lusha tool. Lusha bills the connected account. Deepline does not charge credits for these calls.

**Key strength**: Direct dials (not just HQ numbers). Lusha often surfaces mobile and desk direct numbers that other providers miss.

### Provider characteristics

* **Input required**: LinkedIn URL (best), email, or first\_name+last\_name+(company\_name or company\_domain)
* **Geographic coverage**: Global, strongest in North America + Europe
* **Cost profile**: billed per person enrich, company enrich, or contact returned from search
* **LinkedIn URL requirement**: Must contain "linkedin.com/in/". Sales Navigator URLs not supported.

### Key operations

#### lusha\_enrich\_person

Enriches a person by LinkedIn URL (preferred), email, or name+company. Returns emails at `emails[].email` and phones at `phones[].number`.

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "linkedin_url": "https://www.linkedin.com/in/johndoe"
}
```

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "first_name": "Jane",
  "last_name": "Smith",
  "company_domain": "acme.com"
}
```

Optional flags:

* `reveal_emails: true` — include email addresses in response (default: true)
* `reveal_phones: true` — include phone numbers (default: true)
* `signals: true` — include intent signal data

For an email-only lookup, set `reveal_phones: false`. Lusha reveals phones by default. Omitting the flag can incur unwanted phone-reveal usage on your connected account:

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "linkedin_url": "https://www.linkedin.com/in/johndoe",
  "reveal_emails": true,
  "reveal_phones": false
}
```

#### lusha\_enrich\_company

Enriches a company from domain, name, or Lusha company ID. Returns size, revenue, industry, technologies.

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "domain": "salesforce.com"
}
```

#### lusha\_search\_contacts

Prospecting search with rich filters: department, seniority, company size, industry, job title, location, and tech stack.

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "filters": {
    "seniority": ["director", "vp", "c_suite"],
    "companySize": ["201-500", "501-1000"],
    "department": ["sales"]
  },
  "pageSize": 25
}
```

### Output shape

`lusha_enrich_person` returns a flat profile. Email at `emails[0].email` or `email`. Phone at `phones[0].number` or `phone`.

`lusha_enrich_company` returns a flat company object with `name`, `domain`, `size`, `industry`, `technologies[]`.

`lusha_search_contacts` returns `{ contacts: [...], pagination: { page, pageSize, total, totalPages } }`.

### Anti-patterns

* Don't use Sales Navigator or Recruiter LinkedIn URLs — they'll fail
* Don't include "http\://" or "[www](http://www)." in domain values for company enrichment
* Don't pass `company_name` alone without `first_name` + `last_name` for person lookup — name+company is the minimum combo
* Don't assume `phone` (top-level) is always populated — check `phones[]` array first for the most complete list

## Find an applicable action

Confirm your effective workspace, then search the live catalog:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline auth status --json
deepline search "Lusha" --type tools --json
```

Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

## Inspect the selected contract

Replace `<returned-tool-id>` with the identifier returned by discovery:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline describe <returned-tool-id> --json
```

These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits.

A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

## Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept.

Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects.

For reusable logic, follow [Write Plays](https://deepline.com/docs/sdk-v2/plays.md). For direct-call recovery, use [Tool execution recovery](https://deepline.com/docs/sdk-v2/tool-execution-recovery.md).

> [!TIP]
>
> Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.