Lusha ACTION
Search Single Contact
Search for a single contact using various filters. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Lusha account once, then configure and run Search Single Contact from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "lusha-single-contact-search",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
lusha: { authProvisionId: "apn_xxxxxxx" },
firstName: "First Name",
lastName: "Last Name",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "lusha-single-contact-search",
"configured_props": {
"lusha": { "authProvisionId": "apn_xxxxxxx" },
"firstName": "First Name",
"lastName": "Last Name"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "lusha",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "lusha-single-contact-search",
arguments: {
firstName: "First Name",
lastName: "Last Name",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
firstName First Name | string | First name of the person Optional |
lastName Last Name | string | Last name of the person Optional |
companyName Company Name | string | The name of the company the person works at Optional |
companyDomain Company Domain | string | The domain name of the company Optional |
email Email | string | The email address of the person Optional |
linkedinUrl LinkedIn URL | string | The LinkedIn URL of the person Optional |
refreshJobInfo Refresh Job Info | boolean | Set to true to refresh and update the job details for the person. This ensures that outdated job information is replaced with the most recent data Optional |
filterBy Filter By | string | Filters results based on specific contact details. By default, results will include contacts with at least one contact detail Optional |
revealEmails Reveal Emails | boolean | Whether to reveal email addresses in the response Optional |
revealPhones Reveal Phones | boolean | Whether to reveal phone numbers in the response Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- lusha-single-contact-search
- Version
- 0.0.1
- App
- Lusha
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗