This workflow runs on a weekly scheduled cadence. It processes every account in your Salesforce org in batches, calls Lusha to refresh firmographic data and verify key contacts, flags records that have changed or gone stale, and updates the ICP score based on current data.
1
Trigger — Scheduled Flow runs weekly
A Scheduled Flow runs every Monday morning and queries for Account records that haven’t been enriched by Lusha in the last 30 days — or have never been enriched. Accounts enriched more recently than 30 days are skipped to avoid unnecessary credit consumption.
2
Action — Call Lusha API to refresh firmographics
For each account, the Flow calls Lusha’s /v2/companies/search endpoint with the company domain or name. Lusha returns the current verified profile — industry, employee count, revenue range, funding stage, HQ location, and tech stack — refreshed from Lusha’s database as of today.
3
Action — Detect and flag data changes
The Flow compares Lusha’s response against the existing Salesforce fields. Significant changes — employee count variance above 20%, funding stage change, HQ location change — are flagged on the account record and logged to a change history field. Minor updates are written silently.
4
Action — Verify primary contact for each account
For each account, the Flow verifies the primary contact via Lusha’s /v2/contacts/search endpoint. Departed contacts are flagged. Title changes are logged. The Lusha_Last_Verified__c timestamp is updated on all contacts checked regardless of outcome.
5
Action — Recalculate ICP score with current data
After firmographic refresh, the Flow recalculates the ICP score using the updated data. An account that grew from 80 to 220 employees may have crossed your ICP size threshold and moved from Medium to High fit. The score update is logged with the date so you can see when an account’s fit changed.
6
Output — Current, verified, scored account database
Every account in your Salesforce org reflects current reality. Reps, campaigns, and AI agents running on this data work from verified firmographics — not records that haven’t been touched since the deal first entered the pipeline.
What you’ll get back
After the weekly enrichment run, accounts look like this:
Account record — before weekly enrichment
| Salesforce field | Value |
|---|
| Industry | Technology (manually entered, unverified) |
| Employees | 85 (entered 14 months ago) |
| Revenue range | blank |
| Funding stage | Series A (entered 14 months ago) |
| Lusha ICP score | Medium (scored 14 months ago) |
| Lusha enriched date | 14 months ago |
| Primary contact status | Unknown |
Account record — after weekly enrichment
| Salesforce field | Value |
|---|
| Industry | Revenue Intelligence / SaaS ✓ Lusha verified |
| Employees | 280–320 ⚑ changed from 85 |
| Revenue range | $10M–$50M ✓ Lusha verified |
| Funding stage | Series B ⚑ changed from Series A |
| Tech stack | Salesforce, Outreach, Gong |
| HQ | Austin, TX ✓ Lusha verified |
| Lusha ICP score | High ⚑ upgraded from Medium |
| Lusha change log | Employees 85→280 · Funding A→B · ICP Medium→High · [date] |
| Lusha enriched date | [today] ✓ |
| Primary contact status | ✓ Confirmed in seat |
Weekly enrichment summary
| Metric | This week |
|---|
| Accounts processed | 142 |
| Firmographic updates applied | 38 |
| ICP score changes | 12 — 8 upgraded, 4 downgraded |
| Contacts verified | 142 |
| Departures detected | 6 |
| Title changes detected | 9 |
| Accounts flagged for rep review | 14 |
Build it
Step 1 — Add enrichment tracking fields to the Account object
In Salesforce Setup, go to Object Manager → Account → Fields & Relationships. Add the following custom fields:
| Field label | Field type | API name |
|---|
| Lusha — Enriched date | Date/Time | Lusha_Enriched_Date__c |
| Lusha — Employee count | Number | Lusha_Employee_Count__c |
| Lusha — Revenue range | Text | Lusha_Revenue_Range__c |
| Lusha — Funding stage | Text | Lusha_Funding_Stage__c |
| Lusha — Tech stack | Long Text Area | Lusha_Tech_Stack__c |
| Lusha — ICP score | Picklist (High / Medium / Low) | Lusha_ICP_Score__c |
| Lusha — Change log | Long Text Area | Lusha_Change_Log__c |
| Lusha — Flagged for review | Checkbox | Lusha_Flagged__c |
Step 2 — Build the Scheduled Flow
In Salesforce Flow Builder, create a new Scheduled Flow:
- Schedule: Weekly — Monday at 5am
- Query: Account records where Lusha_Enriched_Date__c is null OR Lusha_Enriched_Date__c less than 30 days ago — use a formula:
TODAY() - 30 - Loop: iterate through each account in batches of 200
- For each account: HTTP Callout to
/v2/companies/search with Account.Website - Compare response fields to existing Salesforce fields — flag significant changes
- Update Records: write refreshed firmographics, update ICP score, append change log
- Second callout:
/v2/contacts/search for primary contact verification - Decision: if significant change detected — set Lusha_Flagged__c = true for rep review
- Save and activate
Step 3 — Build a flagged accounts list view
In Salesforce, create a new Account list view filtered by Lusha_Flagged__c = true. Add the Lusha change log and ICP score fields to the view columns. This gives reps and managers a weekly review queue — accounts where something meaningful changed and human review is warranted before the next outreach or call.
Step 4 — Set up a weekly enrichment summary report
In Salesforce Reports, create a summary report on the Account object grouped by Lusha_ICP_Score__c and filtered by Lusha_Enriched_Date__c in the last 7 days. Add columns for employee count change, funding stage, and flagged status. Schedule the report to run Monday morning after the Flow completes and email it to the RevOps team — a weekly data quality digest without any manual effort.
Step 5 — Test with a sample batch
Before activating at full scale, test the Flow on a filtered subset — accounts in a specific territory or industry. Confirm the enrichment fields populate correctly, the change log appends without overwriting, and the ICP score recalculates based on updated data. Full troubleshooting guidance at 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.
