Lusha
Sales IntelligenceEnrich leads and accounts with Lusha's verified B2B data. Agents append work emails, direct dials, titles, and firmographics to people and companies, bulk-enrich lists, and search the prospecting database to build targeted contact and company lists.
What This Integration Enables
Lusha's API has a shape worth respecting: searching is free, revealing costs credits. That split is a budgeting mechanism, and FlowRunner agents are built to honor it. Agents search the prospecting database as widely as the ideal customer profile demands, score and filter the lightweight matches, and spend credits only on the contacts that survive the filter. Meanwhile inbound enrichment runs as pure pipeline: every form fill and signup gets its work email, direct dial, title, and firmographics appended before a rep ever opens the record. - Enrich a person from whatever identifiers exist: name plus company, a LinkedIn URL, or an email - Bulk-enrich whole lists in one request, with per-contact IDs to correlate results back - Resolve a company's firmographics from just a domain: industry, size band, revenue range, location - Search contacts by title, seniority, department, and company attributes without spending credits - Reveal full details only for chosen contact IDs, keeping spend proportional to intent - Discover companies by firmographic filters for account-based campaigns
Without FlowRunner
With FlowRunner
Use Case Scenarios
The inbound lead that arrives already dressed
A [Typeform](/integrations/typeform) signup lands with a name and company domain. The agent calls Enrich Person with both identifiers to maximize the match, then Enrich Company on the domain. The record that reaches [HubSpot](/integrations/hubspot) carries a verified work email, direct dial, title, seniority, and the company's size and revenue bands. Routing rules fire on real firmographics instead of guesses: enterprise-band companies go to the enterprise queue, and the rep's first look at the lead is the complete picture.
List rescue before the quarter's first campaign
Marketing inherits a conference list of 600 names and companies in [Google Sheets](/integrations/google-sheets). The agent assigns each row an ID, batches them through Bulk Enrich Persons, and writes back matches with work emails and titles while flagging the misses. The matched majority flow into the campaign audience; the unmatched rows go to a review tab instead of bouncing their way into a damaged sender score. One request per batch instead of 600 lookups, and the correlation IDs mean no row ever gets someone else's phone number.
Prospecting where credits follow judgment
An agent runs Prospecting Company Search for logistics companies in the 200 to 1,000 employee band in Texas, then Prospecting Contact Search for operations leadership at the matches. It walks the pages and assembles 340 lightweight results, free of charge, scored against the ICP. The top slice goes to the sales lead as a shortlist. Only after approval does Prospecting Enrich Contacts run on the chosen contact IDs with the search's requestId, revealing emails and phones for exactly the people entering the [Salesloft](/integrations/salesloft) cadence. The database was searched exhaustively; the wallet was opened selectively.
Human-in-Loop Highlight
Prospecting Enrich Contacts is the moment this connector spends money: every revealed contact consumes credits from a finite pool, and there is no un-reveal. An unattended loop that auto-reveals every page of a 4,000-match search converts the quarter's enrichment budget into a list nobody asked for, in minutes. So FlowRunner treats the reveal as a purchase order. The agent presents the shortlist it built from free searches: "212 contacts matched VP Operations and Director Supply Chain at target-list accounts. Recommended reveal: the 80 at accounts with open opportunities. Approve?" The sales lead trims or expands the slice, and the agent reveals exactly that set, logging the requestId and count for the credit ledger. The same discipline covers Bulk Enrich Persons on large imports: the batch size is a spending decision, and spending decisions belong to people.
Agent Capabilities
6 actionsEnrichment
3- Enrich Person Enriches a single person and returns work email, direct and mobile phone numbers, job title, seniority, and current company from Lusha's B2B database. Supply as many identifiers as possible, a full name plus company name or domain, a LinkedIn URL, or an email, to maximize the match rate. Consumes credits per successful match.
- Bulk Enrich Persons Enriches multiple people in one request, each contact carrying its own identifiers and an ID for correlating responses back to the input. Returns enriched records for every match. The right choice over repeated single lookups when processing lists. Consumes credits per successful match.
- Enrich Company Enriches a single company and returns firmographics: legal name, website, industry, employee-size range, revenue range, location, social profiles, and description. A website domain matches more reliably than a name. Consumes credits per successful match.
Prospecting
3- Prospecting Contact Search Searches the prospecting database for contacts by job title, seniority, department, and company attributes, returning lightweight matches and a requestId for downstream reveals. Searching consumes no enrichment credits, so agents can search as widely as the ICP demands.
- Prospecting Enrich Contacts Reveals full contact details, work email, phone numbers, and verified attributes, for contacts returned by a prior search, addressed by requestId and contact IDs. The step that consumes credits, and the spend this page's human gate exists for.
- Prospecting Company Search Searches the prospecting database for companies by firmographic filters: name, domain, industry, employee-size range, revenue range, and location. Returns paginated matches with a requestId, without consuming enrichment credits. The account-discovery step behind ABM list builds.
Frequently Asked Questions
What can FlowRunner do with Lusha?
FlowRunner agents can run Enrich Person, Bulk Enrich Persons, and Enrich Company in Lusha, plus 3 more actions.
Does connecting Lusha to FlowRunner require OAuth?
No. Lusha connects to FlowRunner with an API key, no OAuth flow required.
Can Lusha trigger a FlowRunner workflow automatically?
Lusha doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Lusha
$100 in credits. No card required. Connect in minutes.