How to automate Lusha: 4 plays for outbound teams

Lusha is a fine product. The problem is how most teams use it.

An SDR opens LinkedIn, hits reveal on the Chrome extension, copies the number into Outreach, fires a sequence, and moves on. Multiply that by 30 reps and you have a tool doing a tenth of what it could be doing. The credits get spent, the data lands in the CRM in pieces, and the buying signals Lusha already knows about never make it into a workflow.

The teams getting outsized return from Lusha treat it as an API, not an extension. The contact reveal is the surface layer. Underneath that sits intent data, job-change events, technographics, and a webhook system that can talk to anything in your stack. This post is about the four plays that move Lusha from a per-rep utility to an outbound engine. We build versions of these for clients, so the examples are specific.

The Underuse Problem Most Lusha Customers Have

Symptoms we see when we audit a stack:

• Reps reveal contacts one at a time and copy fields into the CRM by hand.
• Lusha credits run out by the 20th of every month and no one knows where they went.
• Intent and signal data sits inside Lusha Workspace and never reaches the SDR's daily queue.
• Job-change alerts get emailed to a shared inbox no one checks.
• Half the CRM contacts are missing phone, title, or company size because nobody enriched them on entry.

Every one of those is a workflow problem, not a Lusha problem. The data is in there. It just is not wired to anything.

Automation Plays We Build with Lusha

1. Real-time CRM enrichment on contact creation

Trigger: a new contact lands in HubSpot or Salesforce from a form, a webinar, a Calendly booking, or a manual entry.

Workflow: an n8n flow catches the create event, sends the work email or LinkedIn URL to Lusha's enrichment API, and writes back phone, mobile, title, seniority, department, headcount, and industry. If Lusha returns nothing, the flow falls through to a secondary provider so the record never sits empty.

Outcome: every contact entering the CRM is dial-ready in seconds. The SDR opens the record and sees a mobile number, not a blank phone field. The data-quality ticket queue inside RevOps shrinks, because the cause of the tickets (incomplete records) is gone.

2. ICP list-build feeding Clay and Smartlead

Trigger: a scheduled job (weekly or on demand) pulls a fresh ICP list out of Lusha by job title, company size, geography, and tech stack.

Workflow: the list flows into Clay for further enrichment (recent funding, hiring trends, scraped company news, AI-generated icebreakers). Deduping checks against the CRM so no one gets sequenced twice. The cleaned list is split across Smartlead inboxes or Outreach sequences with the icebreaker prefilled. Domains with known unsubscribes or live deals are stripped out before send.

Outcome: reps stop building lists. They run sequences. A team of three SDRs we worked with replaced four hours a day of list work with sequence review, and weekly first-meeting volume roughly doubled within a quarter.

3. Job-change reactivation pipeline

Trigger: Lusha flags a known buyer (a champion, a closed-lost contact, or any tagged persona in your CRM) moving to a new company.

Workflow: the signal fires a webhook into n8n. The old contact gets routed to the CS team with a churn-risk flag. A new company record is created at the new employer (firmographics enriched, owner assigned by territory rules), and a deal is opened with a personalised opener drafted from prior interactions. The AE gets pinged in Slack with a one-line summary and a link to the deal.

Outcome: every champion in motion becomes a warm outbound opportunity instead of disappearing into a new logo. Conversion from job-change touchpoints typically lands several multiples higher than cold outbound to the same persona.

4. Intent-triggered cold-call power list

Trigger: Lusha intent data surfaces accounts researching the topics your product solves.

Workflow: a nightly job intersects intent-positive accounts with ICP fit, deduplicates against active opportunities, and generates the next morning's dial list for each SDR. Each row carries the company, the contact, the verified mobile, the intent topic, and a one-line talking point pulled from the company's recent press releases or LinkedIn posts. The list lands in Aircall, Orum, or whichever dialler the team uses, ready to power-dial.

Outcome: SDRs spend their morning on the 50 highest-intent accounts in the database, not the first 50 they pulled from Sales Navigator. Connect rates typically lift because the right people are picking up, and conversation quality lifts because the rep already knows why the account cares.

How Lusha Should Integrate With Your Stack

The shape of a properly wired Lusha setup:

• CRM (HubSpot, Salesforce, Pipedrive): bidirectional enrichment on contact and company create, plus property updates when Lusha gets fresh data.
• Enrichment hub (Clay): Lusha as one input among several, with waterfall logic so credits go to records the cheaper providers miss.
• Sending stack (Smartlead, Outreach, Salesloft): pre-loaded sequences with personalised first lines built off Lusha + Clay data.
• Workflow engine (n8n, Make, Workato): the glue that catches Lusha webhooks, runs the routing logic, and writes results back into the CRM.
• Dialler (Aircall, Orum, JustCall): daily power-dial lists generated from intent + verified mobiles.
• Notification layer (Slack): job-change alerts, intent spikes, and high-priority leads pushed to the AE who owns the account.

What ROI Actually Looks Like

Numbers below are indicative ranges from outbound teams we have built for, not promises. Your mileage depends on ICP definition, sender reputation, and how good the offer is in the first place.

• Rep time on list-building: typically drops from 8-12 hours per rep per week to under 2. That time goes back into calls and conversations.
• Connect rates on power-dial lists: usually lift 30-60% when intent is layered on top of verified mobiles, versus cold dialling raw lists.
• Credit efficiency: teams that run a waterfall (Lusha plus a secondary provider) usually cut Lusha spend by 20-40% while keeping coverage flat.
• Job-change reactivation: warm reach-outs to former champions typically book meetings at 4-8x the rate of cold outbound to the same role.
• Data quality tickets in RevOps: real-time enrichment usually cuts the queue by half or more inside the first month.

Where Teams Go Wrong

• Buying Lusha and stopping at the Chrome extension. The extension is the demo, not the product. The API is the product.
• Routing all credits through reps instead of through a workflow. Reps reveal duplicates, reveal low-fit contacts, and burn the monthly budget on accounts you would never sequence.
• Treating Lusha as the only data source. A waterfall with one or two backups protects coverage when Lusha does not have a number for a given contact.
• Ignoring intent and signal data. The job-change feed and intent topics are usually the highest-ROI parts of the contract, and the part most teams never plug in.
• No usage reporting. If RevOps cannot see which reps burn the most credits and which workflows generate the highest-converting reveals, the spend optimisation never happens.

Where Moonira Comes In

We build outbound systems for mid-market B2B teams that need more pipeline without hiring more SDRs. Lusha is often a piece of that build, sitting alongside Clay, Smartlead, HubSpot or Salesforce, n8n, and the rep's dialler of choice. The brief from the COO or CRO is usually the same: more conversations with the right people, less time spent on list work, no extra headcount. The plays above are the shape of how we deliver that.

If your team already has Lusha and uses it like a Chrome extension, there is a 10x build sitting in your contract. If you are picking a provider and weighing Lusha against ZoomInfo or Apollo, the right question is not which database is biggest. It is which one your stack can act on.

Picking the Right Play to Start With

You will not build all four of these on day one. Order matters. The play that pays off fastest depends on where your stack is weakest right now.

• If your CRM is full of half-filled records, start with real-time enrichment on contact creation. It is the cheapest play to build and the one your sales team will feel within a week.
• If reps are spending half their day in Sales Navigator and the other half pasting into spreadsheets, the ICP list-build pipeline is the unlock. You will reclaim the working day for actual selling.
• If your CS team has watched former champions leave for new companies without a single follow-up, job-change reactivation is sitting on real pipeline. Plug it in before the next quarter starts.
• If outbound connect rates have flatlined and you are paying for Lusha intent already, the intent-triggered power list is the highest-leverage play of the four. It pays back in connect-rate lift inside a quarter.

The honest answer for most teams: start with enrichment on creation, then layer in the list-build pipeline once the CRM is clean. The other two assume your data foundation is already solid.

What This Looks Like in n8n

We build the orchestration layer in n8n because it stays cheap, runs the long-tail of edge cases, and gives RevOps visibility into every step. A typical Lusha enrichment workflow looks like this:

• Webhook trigger fires on HubSpot or Salesforce contact create.
• A filter node checks whether the contact is already complete (skips the lookup if Lusha already provided this email last month).
• HTTP request to Lusha's person enrichment endpoint with the email or LinkedIn URL.
• If Lusha returns a match, the workflow writes the fields back into the CRM and logs the credit spend.
• If Lusha returns nothing, the flow tries a second provider, then a third, and only flags the record as unenriched if all three fail.
• All credit usage and match rates write to a Supabase table that powers a weekly Slack report for RevOps.

The whole thing runs in a few seconds per contact and costs roughly the price of a coffee per month in infrastructure. The Lusha credits are the only meaningful spend, and the waterfall logic makes them go further than they would running through the extension.