This workflow runs on a daily scheduled cadence. It checks every key contact in your Salesforce org against Lusha’s verified database, detects departures and role changes, updates the contact record, and alerts the owning rep before the situation affects a deal.
1
Trigger — Scheduled Flow runs daily
A Scheduled Flow runs every morning and queries for Contact and Lead records that meet your monitoring criteria — contacts on open opportunities, contacts tagged as champions or economic buyers, or all contacts last verified more than 30 days ago.
2
Action — Call Lusha API to verify each contact
For each contact in the batch, the Flow calls Lusha’s /v2/contacts/search endpoint with the contact’s email address. Lusha returns their current verified status — still in seat, promoted, or departed — along with their current title and company.
3
Action — Detect departure or role change
The Flow compares Lusha’s response against the existing Salesforce record. If the company has changed — departure detected. If the title has changed — promotion or role change detected. If neither has changed — contact confirmed in seat, verification date updated.
4
Action — Update contact record and create task
For departures: the contact record is flagged as departed, the new company is noted if Lusha has it, and a high-priority task is created for the owning rep. For role changes: the title is updated and a standard task is created noting the promotion. For confirmed contacts: the verification date is updated, no task created.
5
Action — Fire Slack notification (optional)
If a departure is detected on a contact linked to an open opportunity, an optional Slack notification fires to the rep and their manager with the contact name, company, departure date, and a link to the Salesforce record. High-value deals get an immediate alert — not a task that sits unread.
6
Output — Rep alerted within 24 hours of any change
The rep opens Salesforce to a flagged contact record, a high-priority task, and the full context of what changed. They know who left, where they went, and what to do next — before the deal is affected.
What you’ll get back
When a departure is detected, the rep sees this in Salesforce:
Contact record — after departure detected
| Salesforce field | Value |
|---|
| Contact name | R.M. |
| Previous title | VP of Sales |
| Previous company | [Company A] |
| Lusha status | ⚠ Departed |
| New company | [New Company] — if Lusha has it |
| Departure detected | [date] |
| Last verified | [date] |
| Open opportunities | [Deal name] — Stage 3 — $42K |
Task created for rep
| Field | Value |
|---|
| Priority | High |
| Subject | ⚠ Champion departed — [Company A] — action required |
| Due date | Today |
| Description | R.M. (VP of Sales) has left [Company A]. They are linked to [Deal name] at Stage 3. Find the new owner of this deal at [Company A] before the opportunity goes cold. Use Lusha to identify the new VP of Sales or interim contact. |
| Related to | [Deal name] opportunity |
Slack notification (if configured)
⚠ Champion departure detected — action requiredContact: R.M. — VP of Sales
Account: [Company A]
Open deal: [Deal name] — Stage 3 — $42K
Departed: [date]
New company: [New Company] (if known)
Find the new owner at [Company A] before this deal goes cold.
View opportunity in Salesforce →
Contact record — after role change detected
| Salesforce field | Value |
|---|
| Contact name | J.K. |
| Previous title | Director of Sales |
| New title | VP of Sales ⚑ promoted |
| Lusha status | ✓ In seat — promoted |
| Promotion detected | [date] |
| Last verified | [date] |
| Task created | Re-engage J.K. — promoted to VP, expanded scope and budget authority |
Build it
Step 1 — Add contact monitoring fields to the Contact object
In Salesforce Setup, go to Object Manager → Contact → Fields & Relationships. Add the following custom fields:
| Field label | Field type | API name |
|---|
| Lusha — Contact status | Picklist (Active / Departed / Promoted / Unverified) | Lusha_Contact_Status__c |
| Lusha — Previous company | Text | Lusha_Previous_Company__c |
| Lusha — New company | Text | Lusha_New_Company__c |
| Lusha — Previous title | Text | Lusha_Previous_Title__c |
| Lusha — Departure date | Date | Lusha_Departure_Date__c |
| Lusha — Last verified | Date/Time | Lusha_Last_Verified__c |
| Lusha — Monitor contact | Checkbox | Lusha_Monitor__c |
Step 2 — Tag contacts to monitor
Check the Lusha_Monitor__c checkbox on any contact you want this workflow to watch — champions, economic buyers, primary contacts on open deals. You can also build a Flow rule that automatically tags all contacts linked to open opportunities above a specified ACV threshold.
Step 3 — Build the Scheduled Flow
In Salesforce Flow Builder, create a new Scheduled Flow:
- Schedule: Daily — recommended 6am in the rep’s timezone so alerts are ready when the day starts
- Start: query Contact records where Lusha_Monitor__c = true
- Loop: iterate through each contact in the batch
- For each contact: HTTP Callout to Lusha
/v2/contacts/search with the contact email - Decision element: compare returned company to Contact.Account.Name
- Company changed → departure detected
- Title changed, company same → promotion detected
- No change → update Lusha_Last_Verified__c only
- Departure path: update Lusha_Contact_Status__c to Departed, log previous company, log new company if returned, create high-priority Task, fire Slack notification if linked to open opportunity
- Promotion path: update Title, log previous title, update Lusha_Contact_Status__c to Promoted, create standard Task
- Save and activate
Step 4 — Configure Slack notification (optional)
In Salesforce Setup, go to Notifications → Slack Notifications. Connect your Slack workspace and configure a notification template using the departure fields. Alternatively, use a Salesforce-to-Slack integration via Zapier or n8n if your org doesn’t have native Slack connectivity. Fire notifications only for contacts linked to open opportunities above your minimum ACV threshold to avoid alert fatigue.
Step 5 — Test with a known contact change
Identify a contact in your Salesforce org who you know has recently changed companies or been promoted. Tag them with Lusha_Monitor__c = true and manually trigger the Flow from the debug panel. Confirm the departure or promotion is detected, the record is updated correctly, and the task is created with the right priority and description. 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.
