This Salesforce Scheduled Flow refreshes your accounts with the Lusha API every week. It updates firmographics, verifies each account’s primary contact, flags meaningful changes, and recalculates the ICP score, so reps, campaigns, and AI agents work from current data.
Requires: Lusha API key · Salesforce Flow Builder · Salesforce admin access
Account data goes stale fast. Companies grow, raise new rounds, and move, and contacts change roles or leave. None of that reaches Salesforce unless someone updates it by hand, and that rarely happens.
This workflow does it on a weekly schedule. Every account gets current firmographics, a verified primary contact, and an up-to-date ICP score, and your team only reviews the accounts where something important changed.
These example outputs are illustrative. They follow the structure and fields of real Lusha API output, but weren’t pulled from a live session.
| 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 |
| 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 |
| 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 |
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 |
On the Contact object, also add Lusha — Last verified (Date/Time, Lusha_Last_Verified__c).
In Salesforce Setup, create a Named Credential for https://api.lusha.com and send your Lusha API key in the api_key header. The Flow’s HTTP Callout actions use it to call Lusha.
In Salesforce Flow Builder, create a new Scheduled Flow:
Lusha_Enriched_Date__c is empty or earlier than 30 days ago (use the formula TODAY() - 30)POST https://api.lusha.com/v3/companies/search-and-enrich with the account’s website domain or company nameLusha_Enriched_Date__c to now. If Lusha finds no match, write “no match” to the change log and still set the date.POST https://api.lusha.com/v3/contacts/search-and-enrich to verify the primary contact, then set Lusha_Last_Verified__c on the contactLusha_Flagged__c = true for rep reviewIn 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.
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.
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.
Use this Salesforce Scheduled Flow. It runs every week, refreshes each account with the Lusha API, flags significant changes, and recalculates the ICP score.
Accounts that have never been enriched by Lusha or were last enriched more than 30 days ago. Accounts enriched more recently are skipped.
You set the thresholds in the Flow Decision element. A good starting point is an employee count change of more than 20%, a new funding stage, a changed ICP score, or a departed primary contact.
The Flow writes “no match” to the change log and updates the enriched date, so the account isn’t retried every week. Existing Salesforce fields aren’t changed.
The 30-day rule skips accounts that were enriched recently. For large databases, run the first pass on accounts with open opportunities, then on named accounts, then on the rest.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
