Auto-enrich new Salesforce leads with Lusha using Flow

The workflow runs automatically every time a new Lead record is created in Salesforce. It calls the Lusha API to enrich the contact and company, writes the enriched data back to the Lead record, and logs the enrichment timestamp so you always know when data was last verified.

What you’ll get back

A Lead record that arrives looking like this — before the rep opens it:

Before Lusha enrichment

After Lusha enrichment

Build it

Step 1 — Get your Lusha API key

Log in to your Lusha account, go to Settings → API, and copy your API key. Full API documentation is at docs.lusha.com/guides.

Step 2 — Create a Named Credential in Salesforce

In Salesforce Setup, go to Security → Named Credentials → New. Set the URL to https://api.lusha.com, authentication protocol to “No Authentication” (you’ll pass the API key in the header), and save. This keeps your API key secure and out of the Flow directly.

Step 3 — Add custom fields to the Lead object

In Salesforce Setup, go to Object Manager → Lead → Fields & Relationships. Add the following custom fields to store Lusha data:

Step 4 — Build the Flow in Salesforce Flow Builder

In Salesforce Setup, go to Process Automation → Flows → New Flow → Record-Triggered Flow.

• Object: Lead
• Trigger: A record is created
• Condition: Run always (or add an entry condition if you want to filter by lead source)
• Action: Add an HTTP Callout action — select your Named Credential, set the endpoint to /v3/contacts/search-and-enrich, method POST, and pass the lead email in the request body
• Parse the response: map the returned fields to your Lead custom fields
• Add a second HTTP Callout to /v3/companies/search-and-enrich for company enrichment
• Add an Update Records element to write all enriched values back to the Lead
• Save and activate

Step 5 — Test with a live lead

Create a test Lead record with a known email address. Open the record and confirm the Lusha fields are populated. Check the Flow debug log if fields are empty — the most common issue is an incorrect API key header or a mismatched field API name. Full troubleshooting guidance at docs.lusha.com/guides.

API reference

Contact enrichment endpoint

POST https://api.lusha.com/v3/contacts/search-and-enrich

Headers:
  api_key: YOUR_LUSHA_API_KEY
  Content-Type: application/json

Request body:
{
  "contacts": [
    { "clientReferenceId": "{{Lead.Id}}", "email": "{{Lead.Email}}" }
  ],
  "reveal": ["emails", "phones"]
}

Match the result by clientReferenceId (results[0] is fine for single-item calls).
If results[0].error exists (NOT_FOUND / COMPLIANCE_RESTRICTED / ENRICH_FAILED), skip mapping.

Key response fields to map:
  jobTitle.title                              → Title
  phones[] where type = "direct" → .number    → Lusha_Direct_Dial__c
  phones[] where type = "mobile" → .number    → Lusha_Mobile__c
  emails[] where type = "work" → .email       → Email (if empty)
  jobTitle.seniority                          → Lusha_Seniority__c
  jobTitle.departments[0] (or join array)     → Lusha_Department__c

Company enrichment endpoint

POST https://api.lusha.com/v3/companies/search-and-enrich

Headers:
  api_key: YOUR_LUSHA_API_KEY
  Content-Type: application/json

Request body:
{
  "companies": [
    { "clientReferenceId": "{{Lead.Id}}", "name": "{{Lead.Company}}" }
  ]
}
(Use "domain" instead of "name" when available, since it matches more reliably.
 No "reveal" needed. Base firmographics are returned by default.)

Match the result by clientReferenceId (results[0] is fine for single-item calls).
If results[0].error exists, skip mapping.

Key response fields to map:
  industry                                    → Industry
  employeeCount.exact (fallback: min–max)     → Lusha_Employee_Count__c
  revenueRange.min – revenueRange.max         → Lusha_Revenue_Range__c
  funding.lastRoundType                       → Lusha_Funding_Stage__c
  location.city                               → City
  location.country                            → Country

Full API documentation: docs.lusha.com/guides

Example outputs in this workflow are illustrative — they reflect the structure, fields, and format of real Lusha API output, but were not pulled from a live session. Build this workflow with your own Lusha API key and Salesforce org to see live results.