Track customer job changes from HubSpot with Wiza, Slack digest

Every Monday at 8am, run an agent that watches my top customer-success contacts for job changes. The trigger is a cron schedule on Monday 8am in my local timezone.

Step 1. Pull contacts from HubSpot. Use HubSpot Search Contacts to fetch my top customer-success contacts. Default filter: lifecycle stage equals customer AND (contact owner is in my high-value owner list OR contact is on a named HubSpot list of top accounts). I'll tell you which owners or list to use during setup. Cap the batch at 50 contacts per run, sorted by deal value or last activity date descending so the most important customers get refreshed first. Make sure you pull each contact's id, email, linkedin_url (or website), first name, last name, current company name, deal owner, and any custom email/phone fields I want updated.

Step 2. Re-verify each contact with Wiza. For each contact in the batch, call Wiza Start Individual Reveal using the LinkedIn URL when present, otherwise the email. Use the phone or full enrichment level so you get verified email and phone back. Wiza is async, so for each reveal poll Wiza Get Individual Reveal until the status is finished (or skip the contact after a reasonable timeout). Capture the returned current company, current job title, verified work email, and verified phone.

Step 3. Detect job changes. For each contact, normalize the company name (lowercase, strip Inc/LLC/Ltd, trim whitespace) and compare Wiza's current company against the company stored on the HubSpot contact. If they don't match, treat it as a likely job change. Skip contacts Wiza couldn't enrich. Don't flag mismatches that look cosmetic (e.g. "Acme" vs "Acme, Inc.").

Step 4. Write back to HubSpot for every flagged contact. Use HubSpot Create Task to file a task titled "Re-engage [Contact Name] at [New Company]" assigned to the deal owner on the contact's primary open deal (or the contact owner if no open deal). Set the task due date to two business days out and priority HIGH. Then use HubSpot Update Contact to write Wiza's verified email into my custom field (I'll specify the property name during setup, e.g. wiza_verified_email) and the verified phone into the matching custom phone field. Don't overwrite the standard email/phone fields, only the custom ones.

Step 5. Post the weekly Slack digest. Use Slack Send a Message to post a single message to my customer-success channel (I'll pick the channel during setup). Title it "Customer job changes this week". Then list every flagged contact, ranked by deal value descending, with: full name, old company, new company, new job title, verified work email, verified phone, deal owner, and a link to the HubSpot contact record. If no job changes were detected, post a short "No job changes detected this week across N contacts checked" message instead of skipping entirely.

Notes for the build. Cap the per-run batch at 50 contacts because Wiza reveals consume credits. Surface the cap and the projected credit cost in the run summary. Handle Wiza rate limits and partial misses gracefully. Don't fail the whole run if one contact can't be enriched. If HubSpot returns no contacts matching the filter, just post a quiet "No top customers matched this week" Slack note and exit.

Additional information

What does this prompt do?

Pulls your customer-success contacts from HubSpot every Monday morning and re-verifies each one with Wiza using their email or LinkedIn URL.
Compares the freshly enriched company against the company stored on the HubSpot contact and treats every mismatch as a likely job change.
Files a re-engage task on the deal owner in HubSpot and writes the new email and phone into custom fields so the record stays current.
Posts a ranked Slack digest of the week's job changes with each person's new company, new title, verified email, and phone.

What do I need to use this?

A HubSpot login with access to your customer contacts and the ability to create tasks and edit contact properties.
A Wiza account with enough credits to refresh your customer book each week. Reveals are credit-consuming, so the workflow caps each run at fifty contacts by default.
A Slack workspace and the channel where you want the weekly job-change digest to land.
Custom contact fields in HubSpot for the verified email and phone you want Wiza to write back.

How can I customize it?

Change the schedule. Move it off Monday at 8am, run it twice a month, or trigger it the morning after your QBR prep.
Pick who counts as a top customer. Filter HubSpot by lifecycle stage, owner, list membership, deal value, or any property you already use.
Tune the batch size. Lower the cap if you want to spend fewer Wiza credits per run, or raise it if your customer book is bigger and you want full coverage.
Choose what happens on a hit. Swap the Slack channel, add the AE on the deal as a Slack mention, or send the task to the renewal owner instead of the deal owner.

Frequently asked questions

How does it know someone changed jobs?

It asks Wiza for each contact's current employer and job title, then compares that against the company stored on the HubSpot contact. If they don't match, the contact is flagged for the weekly digest.

Will this burn through my Wiza credits?

Wiza only charges credits when it successfully finds verified data, and the workflow caps each run at fifty contacts so you can predict the cost. You can lower the cap or tighten the HubSpot filter to spend even less.

What gets written back to HubSpot?

For every flagged contact, the workflow creates a re-engage task on the deal owner and updates the contact with the new verified email and phone in the custom fields you pick.

Can I run this for a specific HubSpot list instead of all customers?

Yes. Point the filter at any HubSpot list, owner, lifecycle stage, or property combination. A common setup is the top-tier accounts list or every contact owned by a named CSM.

What if Wiza can't find the contact?

Misses are skipped silently so they don't clutter the digest. Only confirmed company mismatches show up in Slack and trigger a task in HubSpot.