Enrich Salesforce records for HubSpot
This play connects Salesforce and HubSpot through Zapier, using Lusha Connect to enrich company and contact data as soon as a new Salesforce record appears. It validates enrichment success, finds the right prospecting contacts, enriches the contact record, and then enrolls the enriched contact into a HubSpot workflow—so every new lead enters your lifecycle motions with clean, complete data.
Why this works
Most leads hit Salesforce with partial or inconsistent fields: missing domain, incorrect company name, incomplete firmographics, or no contact intel. That breaks workflow enrollment, segmentation, scoring, and assignment.
This play fixes it upstream. It enriches the company and contact immediately, verifies the output, and only then routes the contact into HubSpot—so automations fire with the right context and teams act on qualified, standardized leads.
What you get
- Real-time enrichment when new records are created in Salesforce
- Company-level context (industry, size, HQ, revenue range, etc., based on availability)
- Contact discovery + enrichment from Lusha (prospecting search + write enrichment)
- Quality control via a filter step so only successful enrichments proceed
HubSpot workflow enrollment to trigger scoring, routing, sequences, or nurtures automatically
How to set it up
Configure the Salesforce trigger
Choose the object you want to watch, typically:
- Lead created
- Contact created
- Account created
- Or a custom object for inbound leads
Best practice: Trigger only on the records you intend to enroll (e.g., “Source = Inbound”, “Lifecycle stage = Lead”, etc.) to reduce noise.
Configure Lusha company enrichment
Map the cleanest identifiers from Salesforce:
- Company domain (preferred)
- Company name (fallback)
- Optional: HQ country/state if you have it (improves match)
Tip: If you’re enriching leads, the email domain is often the fastest path:
Extract domain from email → enrich company → then enrich the right contact
Complete the Filter step
This is the critical guardrail to prevent bad downstream actions.
Recommended filter conditions (choose what your Lusha step outputs):
- Continue only if Lusha enrichment returned a valid company match
Examples:- “Company ID” exists
- OR “Company name” exists
- OR “Matched domain” exists
- Optional: Continue only if enrichment confidence/match quality is acceptable (if available in output)
Optional: Continue only if company is within ICP bounds (employee range, industry, region)
If filter fails:
Route to a fallback path (Zapier Paths) or log to a Google Sheet for manual review.
Configure prospecting contacts search
Use the enriched company results to find the best contact(s) to enrich.
Common approaches:
- Find contacts by job title / function (e.g., Sales, RevOps, IT, Finance)
- Filter by seniority (Manager+)
Limit to 1–3 contacts to control cost and noise
Best practice: Decide whether this play is for:
- enriching the incoming lead contact, or
- enriching target personas at the same company (ABM-style)
If it’s the first one, try to match by email first. If it’s ABM-style, search personas.
Configure contact enrichment write
Map fields you want to standardize downstream, such as:
- Work email (if missing)
- Direct dial / phone (where available)
- Title, department, seniority
Location - LinkedIn URL
Best practice: Only “write” fields that are empty in your CRM to avoid overwriting trusted data.
Configure HubSpot enroll in workflow
You’ll need:
- HubSpot connection authorized in Zapier
- Workflow selection (often by dropdown; sometimes requires a workflow ID)
- Contact mapping: choose the HubSpot contact to enroll
- Usually via email as the unique identifier
- Usually via email as the unique identifier
Important: If the enriched contact doesn’t already exist in HubSpot, you may need an extra step before enrollment:
HubSpot: Create or Update Contact
Then enroll that contact in the workflow.
What to do next
- Segment by enrichment results: Create HubSpot branches based on industry, company size, or region to trigger different nurture tracks or sales motions.
- Add lead scoring: Use enriched firmographics and seniority to assign scores automatically (e.g., ICP fit + decision-maker = higher priority).
- Auto-assign ownership: Route enriched leads to the right SDR or AE based on territory, segment, or account size—without manual Ops work.
- Control credit usage: Add additional filters to skip enrichment if the company or contact was enriched recently or already exists with complete data.
- Create an Ops review queue: Log failed enrichments or partial matches to a Google Sheet or HubSpot list for quick review and cleanup.
Expand to account-based motions: Once the lead is enriched, automatically enrich additional buying committee roles at the same company for multi-threaded outreach. - Track impact: Measure conversion rates and time-to-contact for enriched vs. non-enriched leads to quantify the ROI of automated enrichment.
The goal: New Salesforce records shouldn’t enter your funnel half-empty. This play enriches the company and contact immediately, validates the output, and enrolls the right people into HubSpot workflows—so lifecycle automation runs on clean data, not guesswork.
No FAQ items available at this time.
Ready to build this?
Get started with Lusha and set up this play in minutes.
