Monthly champion job change sweep with LeadMagic

Build a code-based workflow that runs on a cron schedule at 6am on the 1st of every month and sweeps our HubSpot champions for job changes using LeadMagic.

Step 1. Pull the audience. Use HubSpot Search Contacts to fetch every contact that is either tagged as a champion (champion property = true, or a champion list ID) or associated with a closed-won deal in the past 24 months. Page through results until done.

Step 2. For each contact, call LeadMagic Job Change Detector with their name, current email, and current company. If the response says they are still at the same company, skip them.

Step 3. When a job change is detected, call LeadMagic Email Finder with the contact's name and the new company to get a verified work email at the new employer. Then call LeadMagic Company Search on the new company to pull firmographics (industry, employee count, revenue band, headquarters, website).

Step 4. Write the move back to HubSpot. Use HubSpot Update Contact to set the new job title, new company name, and new verified email on the existing contact record. Use HubSpot Create Note to attach a note titled "Job change detected" that includes the previous title and company, the new title and company, tenure at previous employer, detected date, and the new company firmographics. Associate the note with the contact and, if available, the original account. Use HubSpot Create Task to create a task titled "Outreach: champion changed jobs" assigned to the original account owner with a due date of 2 business days out and high priority.

Step 5. After all contacts are processed, post a single digest message via Slack Send a Message to a sales channel (configurable, e.g. #champion-moves). The digest should list every detected move with: champion name, previous company and title, new company and title, the original account owner's name, and a deep link to the HubSpot contact record. If no moves were detected, post a one-line "No champion moves this month" message so the team knows the job ran.

Implementation notes: handle LeadMagic rate limits with backoff; treat "no email found" and "no firmographics" as non-fatal (write whatever was found and continue); deduplicate against a stored cursor so the same move is never written twice if the job is re-run; log each move into a run summary that is included in the Slack digest.