This post walks through the Lusha templates available on Make and how teams use them in practice.
You’ll see how Ops teams:
Enrich contacts as they enter HubSpot or Salesforce
Keep company records accurate over time
React to role changes and company signals
Generate new accounts and contacts based on closed-won data
The goal isn’t more automation — it’s GTM systems that stay usable without constant cleanup.
A messy GTM stack usually starts clean enough: a CRM that mostly reflects reality, a few enrichment steps, maybe some light automation to save time. Then the team grows, lead sources multiply, and the edge cases start piling up. Contacts arrive without enough context, company records stop matching what’s actually happening, and signals exist somewhere in the stack but don’t quite connect to anything actionable.
None of this breaks the system outright. It just adds friction. Teams work around it with manual enrichment, exports to Sheets, and periodic cleanup projects, until the system becomes heavier to operate than it needs to be.
The workflows below show how teams use Lusha with Make to deal with those issues closer to where they start. Not by redesigning the stack or adding process, but by handling enrichment and updates inside the same flows the team already relies on.
These are the Lusha templates that are live on Make today.
Contact enrichment
Auto-enrich HubSpot contacts
Template: Auto-enrich HubSpot contacts→ View Make template
This workflow enriches new or updated HubSpot contacts with missing email, phone, and company fields using Lusha.
Teams usually add this when leads arrive from multiple sources and downstream logic already assumes those fields exist. Scoring, routing, and reporting all work better when records are complete, and fixing that at the point of entry is simpler than chasing gaps later.
Prospecting pipeline for Salesforce
Templates:
- Prospecting Pipeline for Salesforce→ View Make template
- Auto Prospecting Pipeline for Salesforce→ View Make template
These workflows search for contacts using Lusha, enrich them, and create Salesforce leads.
They’re commonly used when prospecting happens directly in Salesforce and enrichment is expected to be part of lead creation, not a separate task someone has to remember to run.
Prospecting via Google Sheets
Template: Automated Lusha Prospecting Pipeline to Google Sheets→ View Make template
Runs Lusha searches and writes enriched contacts into Google Sheets.
Teams tend to use this when Sheets act as a staging layer — validating ICP logic, reviewing output, or sharing lists internally — before anything is pushed into CRM.
Company enrichment
Keep HubSpot company data current
Templates:
These workflows update HubSpot company records based on Lusha company data and signals.
They’re useful when company-level fields are relied on for segmentation, reporting, or ownership, and “enrich once and forget” has already proven unreliable.
Signals
Track contact role changes
Template: Auto-Track All Contact Signals→ View Make template
Detects role changes and promotions and updates HubSpot records automatically.
Teams usually connect this when ownership rules, territories, or follow-up sequences depend on seniority, and manual checks don’t scale.
Capture company signals and trigger workflows
Template: Capture Company Signals & Broadcast Alerts→ View Make template
Pulls Lusha company signals and passes them into downstream workflows.
This is used when signals are meant to drive actions like updates, alerts, or reprioritization rather than sit in dashboards waiting for someone to notice them.
Prospecting from existing data
Create similar accounts from closed-won deals
Template: Create Similar Accounts on Wins→ View Make template
Uses closed-won deals to find similar companies and create new Salesforce accounts.
Teams rely on this when targeting is based on what has already converted, and expansion logic should be grounded in CRM data rather than assumptions.
Expand target account lists
Template: Expand Target Accounts with Recs→ View Make template
Enriches existing accounts, finds similar companies, and exports an expanded list.
This is typically used when account lists need to evolve over time and TAM work isn’t a one-off exercise.
Find similar contacts
Template: Contact Recs From Lusha Records→ View Make template
Uses Lusha IDs to recommend similar contacts and create them automatically.
Useful when account expansion matters and teams want a more structured way to think about buying committees, instead of relying on manual searches.
The pattern behind these workflows
Across all of these templates, the approach is consistent.
- Data is completed when it enters the system.
- Real-world changes update records instead of relying on reminders.
- Closed-won data feeds future targeting decisions.
- CRMs stay usable without recurring cleanup cycles.
Nothing here is flashy. It’s just systems behaving the way teams already expect them to.
If you’re building with Make
These templates are starting points. Most teams adjust field mappings, add conditions, or connect additional steps based on how their stack is set up.
The division of responsibility stays simple: Lusha supplies current contact and company data. Make handles the logic around when and how it’s used.
That’s usually enough to keep GTM systems stable as volume and complexity increase.
FAQs
Lusha is used as the data source inside Make workflows to enrich contacts and companies, detect real-world changes like role moves or company growth, and feed that data into CRM, prospecting, and targeting flows.
These are live templates available on Make today. Teams typically copy them and then adjust field mappings, conditions, or downstream steps based on their stack.
Yes. Several templates use Google Sheets as a staging or output layer, which teams often use to validate logic or share data before pushing anything into CRM.
Lusha signals reflect real changes, like contact promotions or company updates. In Make, those signals are used to trigger updates, alerts, or follow-up workflows instead of just sitting in a dashboard.
Both. Sales teams usually focus on prospecting and enrichment flows. RevOps teams tend to own company enrichment, signals, and workflows that keep CRM data consistent over time.
