Ops

Job-change reactivation workflow

Build a workflow that pulls your past qualified inbound leads, batches them, checks job-change signals via Lusha’s Signals API, then syncs the enriched results back into your CRM. All so Sales can re-engage with the right message at the right time.

Job-change reactivation workflow video thumbnail
Built by: Lusha
Time to build: 10 min
Difficulty: Medium
Tools: Lushan8nSalesforceWorkato

Why this works

Inbound intent is real, but timing moves. People switch roles, land new budgets, and suddenly the same problem matters again. 

Most teams don’t catch that shift because their “qualified inbound” list is static. This play turns historical intent into a renewable audience by re-scoring it with job-change signals.

What you get

A refreshed, prioritized audience of past qualified leads, enriched with:

  • New role
  • New company
  • Date of change

…and organized into tables so you can route, sequence, retarget, and re-activate fast.

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 shouldn’t be to wait for past buyers to come back. Catch them the moment they’re ready again. 

No FAQ items available at this time.

Ready to build this?

Get started with Lusha and set up this play in minutes.