What this workflow does
When a contact in your Apollo workspace changes jobs to a new company, Apollo automatically detects the change, confirms the new account is one you own, pulls a fresh email at the new company via waterfall enrichment, and adds the contact to a list so your team can act on the signal.
The result: every time someone in your CRM moves to a new role, you get a clean, enriched record at the new account without anyone manually checking LinkedIn.
Why this matters for Qualified
Job changes are one of the highest-intent buying signals in B2B. A former champion at one Salesforce-using account who lands at another Salesforce-using account is already pre-qualified for your ICP. This workflow surfaces those signals automatically and gets you a working email on day one of the new role.
We configured this workflow together on 2026-05-13. It is saved and ready to run. Let it sit for a week, then read the output and tell me what you see. If the filter pulls noise, we'll tighten it.
Why this matters even more now
Post-Salesforce acquisition, you mentioned the strategic shift toward net new prospecting. Job-change signals at Salesforce-using accounts are exactly the lane this workflow lives in. It compounds: every champion who moves into your ICP becomes a warm signal you would otherwise miss.
The workflow we built
Five-stage automation. Each stage fires automatically. No human in the loop until the contact lands in the list.
Configuration we saved
| Component | Setting |
|---|---|
| Trigger | Contact job change detected |
| Filter | Account owner is Angelo Quiambao |
| Action 1 | Waterfall enrich email at new company |
| Action 2 | Add enriched contact to list |
| Optional Action 3 | Slack notification on enrichment success |
The current filter pulls only accounts you own as the AE. If you want the workflow to fire on accounts owned by your BDR partners or other AEs, that filter needs to change. See "Tune & Extend" for the three common variants.
How to verify it is running
Three checks. Each takes under a minute. Do all three within 48 hours of activation.
How to read the output
The list shows:
- Contact name and new company
- New email (waterfall enriched)
- Old company and old role for context
- Date the change was detected
From there your team can:
- Add the contact to a sequence
- Hand the lead to the AE who owns the new account if it is not Angelo
- Trigger your Relevance AI agent to research the new account and draft a first email
What to watch for in the first two weeks
Tune the filter
The current filter fires only on accounts you personally own. Three common variants you may want next. Each is a one-minute change in the workflow editor.
Credit usage expectations
Each enrichment costs credits depending on what gets returned. Rough math:
- A workspace of about 100 active accounts with normal job-change rates triggers a handful of enrichments per week.
- At your team's current weekly cap (1,000 credits per user), this workflow consumes a tiny fraction of available headroom.
- If you scale to all accounts (Variant 03), credit usage rises in proportion to workspace size. We should monitor.
I'm pulling your team's actual usage this week. If anyone is bumping the cap, I'll flag it and make the case for an uplift.
How to extend this workflow
Once this one is stable, the natural next builds are:
- Job change to sequence. Auto-enroll enriched contacts in a job-change sequence in Outreach (or Apollo, when you migrate).
- New company research. Trigger your Relevance AI agent to pull a research brief on the new company the moment the enrichment lands.
- Account ownership routing. If the new company is not currently owned, route to the AE whose territory it falls in.
All three are doable today. We started with the foundation.
Open questions for you
Three things to confirm or decide before we extend.
After a week, tell me how many contacts landed in the list and how many felt like real signal. That single ratio tells us whether the filter is right.