This Workato recipe runs when a new record is created in Salesforce. It enriches the company with Lusha, runs contact-level prospecting only if company data is missing, and creates an engagement in HubSpot that triggers the right workflow, so HubSpot runs on accurate company data.
When Salesforce and HubSpot don’t share the same company data, teams stop trusting it. Records drift, workflows fire at the wrong time, and reports break.
This recipe enriches each company once and sends that data downstream, so your HubSpot workflows start from the same firmographic data.
Ensure active connections for:
Confirm:
Best practice: Limit triggers to records with a company context to avoid unnecessary enrichment.
Map identifiers:
This step returns verified firmographic data.
If company enrichment succeeds, the recipe skips the prospecting steps. If company data is missing or incomplete, it moves on to contact-level prospecting enrichment. This keeps the workflow efficient.
Map enriched fields to:
Tip: Use engagement type or notes to indicate “Lusha Enriched” for visibility.
Create a test Salesforce record and confirm:
The goal: Company enrichment should happen once—and power every system downstream. This play keeps HubSpot workflows aligned with enriched company data and HubSpot workflows aligned, so teams operate on a single, trusted source of company truth.
Use this Workato recipe. It enriches each new Salesforce record with Lusha and creates a HubSpot engagement that triggers the right workflow.
Industry, company size, HQ, revenue range, and funding stage where available.
Only when company enrichment returns missing or incomplete data. Otherwise, it’s skipped.
New leads, accounts, or custom objects. It works best when you limit it to records with company information.
Not by default. You can add a step that writes the enriched fields back to Salesforce.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
