Weekly Datagma job change watch for HubSpot champions

Every Monday at 8am ET, run this as an autonomous agent that watches my tracked HubSpot contacts for job changes and posts one ranked Slack briefing to my account team.

Step 1. Use HubSpot Search Contacts to pull every contact I track. The tracked signal is configurable at setup, typical options are a custom boolean property like is_champion equals true, membership in a static list such as Champions or Decision Makers, or lifecyclestage equals customer. Page through all results. For each contact capture the HubSpot contact id, full name, email, LinkedIn URL if present, the company and job title currently stored on the record, and the hubspot_owner_id.

Step 2. For each contact, call Datagma Enrich Person or Company to read their current employer and title. Prefer the LinkedIn URL as the lookup input when available, otherwise fall back to email. Use the global Enrich endpoint, not the regional Detect Job Change endpoint, so coverage is not limited to France, Spain, Italy, and Germany. From the response, read the current company name, current job title, and any company signals you can use later for ranking such as employee count, industry, and domain.

Step 3. Compare Datagma's current employer and title against what HubSpot has on file. Treat the contact as a mover only when the current company differs from the stored company, or the current title differs in a meaningful way (a real role change, not just a capitalization or punctuation diff). Skip contacts whose company and title still match. Skip contacts that Datagma could not match (Datagma signals this with code 5 in the response body, even on a 200 OK).

Step 4. For each mover, call HubSpot Update Contact to set jobtitle to the new title and write the current date into a job_change_detected_at custom property. Do not overwrite the company field automatically, and do not touch any other property. Add the mover to an in-memory briefing buffer with: full name, old company, new company, old title, new title, HubSpot deep link (https://app.hubspot.com/contacts/<portalId>/contact/<contactId>), the account owner, and the company signals from step 2.

Step 5. Use agent judgement to rank movers by likely revenue impact. Higher rank when the new employer looks like a named target account or an ICP-fit company (use industry, headcount, and any target-account list configured at setup). Flag the move as an expansion opportunity when the new employer is itself an active customer. Flag the move as a churn risk when the contact is a decision-maker or champion at an active customer who just left for a new employer. Otherwise treat it as a warm intro opportunity at the new company.

Step 6. Post ONE consolidated message to the configured Slack channel using Slack Send a Message. The briefing should lead with a one-line header (contacts checked, movers found), then list each mover on its own block ranked highest value first, with name, old company arrow new company, new title, the warm intro / expansion / churn-risk flag, a one-sentence why-this-matters note tailored to that move, and the HubSpot deep link. Tag the original account owner inline so it routes naturally. Write in plain, friendly English, not a robotic table.

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

Make the tracked-contact signal, the Slack channel, the named target account list, and the active-customer definition configurable inputs at setup so a non-technical user can tune them without editing the workflow.