Catch HubSpot champion job changes every Monday

Every Monday at 8am ET, run this workflow as an autonomous agent.

Step 1. Pull every HubSpot contact flagged as a champion using HubSpot Search Contacts. The champion signal is a custom property like is_champion equals true. If that property does not exist, fall back to lifecyclestage equals customer with a specific tag, or membership in a 'Champions' static list. Page through all results so no contact is missed. For each contact, capture the HubSpot contact id, full name, email, current company, current job title, and the account owner id.

Step 2. For each champion, call Waterfall.io Job Change Detection with their email and current company. This endpoint is synchronous and returns a status of moved, left, no_change, or unknown plus an updated profile snapshot with the new company and title when applicable.

Step 3. For contacts whose status comes back as moved, do all three of the following: (a) Update the HubSpot contact record using HubSpot Update Contact, setting the company field to the new company name and jobtitle to the new title. Do not overwrite any other fields. (b) Create a follow-up task using HubSpot Create Task. Assign it to the original account owner (hubspot_owner_id) captured in step 1. Subject: 'Reach out, champion moved to {new_company}'. Due date one business day from now. Associate it with the contact. (c) Add the mover to an in-memory digest buffer with: name, old company, new company, new title, and a HubSpot deep link to the contact record (https://app.hubspot.com/contacts/<portalId>/contact/<contactId>).

Step 4. For contacts whose status is no_change or unknown, skip them entirely. Do not write back to HubSpot, do not create a task, do not add them to the digest.

Step 5. After processing every champion, post ONE grouped digest message to the #champion-moves Slack channel using Slack Send a Message. The digest should: lead with a one-line header showing total champions checked and number of movers found; list each mover on its own line with name, old company arrow new company, new title, and the HubSpot deep link; order movers by likely value (use agent judgment, for example champions moving into ICP-fit companies, larger orgs, or named target accounts go to the top); be written in plain English with a friendly tone, not a robotic table.

Step 6. If zero movers are found, skip the Slack post entirely. Do not send an empty digest.

Make the champion-identifier signal, the Slack channel, and the ICP-fit criteria configurable inputs at setup time so a non-technical user can tune them without editing the workflow.