This workflow takes your past qualified inbound leads, checks which ones changed jobs using the Lusha Signals API, and sends the updated data back to your CRM. Sales gets a fresh list of people who already know you, with a real reason to reach out now.
Job-change reactivation workflow
Why re-engage leads who changed jobs?
A lead that went cold wasn’t necessarily a bad fit. Often the timing was wrong. When that person moves to a new role or a new company, they may have a new budget, a new team, and the same problem you already solve.
Most teams miss that moment because their list of past inbound leads never changes. This workflow checks the list for job changes, so leads with proven intent become a pipeline source you can come back to again and again.
What this workflow does
- Pulls past qualified inbound leads from Salesforce, another CRM, or a spreadsheet
- Checks each lead for job change signals with the Lusha Signals API
- Returns each person’s new role, new company, and date of change
- Organizes the results so you can route, sequence, or retarget leads quickly
- Syncs the updated records back to your CRM
How to set it up
01
Pull a clean list of past qualified inbound leads
Start with people who showed real intent and reached a meaningful stage (Salesforce in the example, but any CRM or sheet works).
02
Process contacts in batches
Batch your list because the Signals API processes 100 contacts per request.
03
Build the request and send it to the Lusha Signals API
For each batch, structure a JSON payload with:
- Contact identifiers
- Requested signal type(s) (Job Change)
- Optional company-level signals
04
Organize results into actionable tables
Turn raw signals into routing-ready outputs:
- Old role → new role
- Previous company → new company
- Date of change
- Movement direction (IC → Manager, etc.)
- Buying context fields you care about
05
Sync the enriched output back into your CRM
Export to CSV and bulk upload/sync back. From there you can update records, create tasks, trigger sequences, and feed scoring models.
What to do next
- Add additional signals: promotions, headcount growth, new job listings
- Add scoring (who gets sequenced vs. who gets retargeted)
- Add routing logic (territory/segment/owner)
- Add cooldown + dedupe rules (so you don’t spam the same person)
The goal: Don’t wait for past buyers to come back. Catch them the moment they’re ready again.
FAQ
Send your list of past leads to the Lusha Signals API and request job change signals. The API returns each contact’s new role, new company, and the date they changed jobs.
A new role often comes with a new budget, new priorities, and fresh problems to solve. Leads who showed interest before already know your product, which makes them easier to re-engage.
Start with past inbound leads who showed real intent and reached a meaningful stage in your funnel, not every contact in your CRM.
The Signals API handles up to 100 contacts per request, so the workflow splits larger lists into batches.
No. Salesforce is used in the example, but the workflow works with any CRM or spreadsheet you can export from and sync back to.
Ready to run this?
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
