View as Markdown
Lusha icon

Lusha ACTION

Search Company Signals

Search for company signals using identifiers like domain name or company name. This endpoint combines search and signal enrichment in a single request. 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 Company Signals 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-search-company-signals",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    lusha: { authProvisionId: "apn_xxxxxxx" },
    companies: ["Companies"],
    signals: ["Company Signals"],
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Search Company Signals inputs
Property Type Description
companies Companies string[]
List of company objects to search for. Example: [{ "id": "123321", "domain": "lusha.com", "name": "Lusha" }]. See the documentation for more information.
Required
signals Company Signals string[]
Types of company signals to retrieve
Required
startDate Start Date string
Start date for signal retrieval Format: YYYY-MM-DD
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-search-company-signals
Version
0.0.2
App
Lusha
Authentication
API key
Read-only
Yes
Destructive
No
Open world
Yes