---
title: "Champion job-change alerts: HubSpot, Reverse Contact and Slack"
description: "Detect when a customer contact changes company and turn it into pipeline. A monthly sweep over closed-won contacts, ending in one Slack alert."
url: https://www.reversecontact.com/integrations-hub/workflows/champion-job-change
format: markdown twin of the page above, generated at build time
---

New Unlimited plans are here. Fetch, search and enrich without counting credits. [See plans →](https://www.reversecontact.com/integrations-hub//pricing#plans)

Reverse Contact

### Products

Data

People Data

Company Data

Our Data Quality Standard

Delivery methods

API

Webhooks

CSV Enrichment

MCP

CLI

Integrations

### Use cases

[Sales Product](https://www.reversecontact.com/integrations-hub//use-case/sales-products)[Recruiting Product](https://www.reversecontact.com/integrations-hub//use-case/recruiting-products)[Internal Data Teams](https://www.reversecontact.com/integrations-hub//use-case/internal-data-teams)[AI Products](https://www.reversecontact.com/integrations-hub//use-case/data-for-ai)[CRM Enrichment](https://www.reversecontact.com/integrations-hub//use-case/crm-enrichment)

### Features

[Email Finder API](https://www.reversecontact.com/integrations-hub//feature/email-finder-api)[Phone Number Enrichment](https://www.reversecontact.com/integrations-hub//feature/phone-number-enrichment)[People Search API](https://www.reversecontact.com/integrations-hub//feature/people-search-api)[Agentic Search API](https://www.reversecontact.com/integrations-hub//feature/agentic-search-api)[People Lookalike API](https://www.reversecontact.com/integrations-hub//feature/people-lookalike-api)[Company Search API](https://www.reversecontact.com/integrations-hub//feature/company-search-api)[Person Enrichment API](https://www.reversecontact.com/integrations-hub//feature/person-enrichment-api)[Company Enrichment API](https://www.reversecontact.com/integrations-hub//feature/company-enrichment-api)[Person Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-person-api)[Company Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-company-api)

Security

Pricing

Docs

[Log in](https://app.reversecontact.com/auth/login) [Book a demo](https://www.reversecontact.com/contact?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header) [Start for free](https://app.reversecontact.com/auth/signup?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header)

# Champion job-change alerts

Detect when someone who already bought from you turns up somewhere new, and get there before the competition does.

Built by **Reverse Contact** · Verified 2026-09-18 · 3 tools, hours to build

A contact who championed you at their last company is the warmest lead in your database, and almost nobody watches for them. They already know the product, they already chose it once, and at a new company they have budget and a mandate to change something. The whole play is noticing in time.

This is a monthly sweep rather than a real-time pipeline, and it should be. Job changes do not need detecting within a minute; they need detecting within a month and acting on within a week. That makes this one of the cheapest workflows here to run and one of the easiest to justify, because the output is named accounts rather than an improvement in a field.

The segment that makes this work

Do not sweep your whole database. Sweep the contacts attached to closed-won deals, plus anyone with a meaningful activity history who did not buy. Those are the people whose move is worth an alert. Everyone else generates noise and costs credits, and the alert stops being read within a month.

## The pipeline, step by step

5 steps. The ones in blue are the data layer; everything else is plumbing you already own or can stand up in an afternoon.

01

### Build the champion list

A CRM list of contacts on closed-won deals, plus lost deals where the contact was an advocate. Keep it to hundreds rather than thousands: this is a precision play, not a coverage one.

the segmenthundreds, not thousands

↓

02

### Re-resolve each contact monthly

Reverse Contact returns current role and company against the identity you already hold, with a last-updated timestamp on every response so you can tell fresh data from cached.

1 callper champion, monthly

↓

03

### Compare to what the CRM believes

Company changed, title changed, or both. The comparison is the workflow: the enrichment is only interesting where it disagrees with the record you already have.

the diffis the signal

↓

04

### Confidence decides whether it is real

A low-confidence answer is not a job change, it is a maybe. Set a threshold, and send anything under it to a review queue rather than to a rep. Reverse Contact lets you raise the precision threshold on the request itself.

thresholdnot a guess

↓

05

### Create the new-company record and alert

A new contact at the new company, linked to the old one so the history is visible, and one Slack message to the account owner naming both. This is the part that turns a data point into pipeline.

1 messageper confirmed move

## Build it with an agent

This workflow ships as a skill file: the API surface of every tool in the chain, the build order, the limits that break it, and how to check it worked. Point an agent at it and it has what it needs without reading 3 sets of vendor docs first.

Drop it into Claude Code

mkdir -p .claude/skills/champion-job-change-alerts curl -o .claude/skills/champion-job-change-alerts/SKILL.md https://www.reversecontact.com/integrations-hub/skills/champion-job-change.md

For Codex, Cursor, or anything else that reads a file or fetches a URL, hand it `https://www.reversecontact.com/integrations-hub/skills/champion-job-change.md` directly. It is plain markdown with YAML frontmatter and no tool-specific syntax, so nothing in it depends on which agent is reading it.

3 of the joins in this chain have a full guide behind them, [HubSpot and Reverse Contact](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-reverse-contact-integration) and [HubSpot and Slack](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-slack-integration) among them. The chain crosses 3 of the seven layers a stack splits into, from the [CRM layer](https://www.reversecontact.com/integrations-hub/stack/crm) outward, which is why no single vendor owns it.

## What will bite

Documented by one of the vendors in the chain, and easier to design around than to discover.

- **The old record must not be overwritten** — A job change means creating a record at the new company, not editing the old one. Overwrite the original and you lose the deal history that made this person worth watching, which is the only asset the play depends on.
- **Detection is not instant, and should not be** — Profile data reflects a move when the move becomes public, which is days to weeks after it happens. A monthly sweep catches it in time to act. A daily sweep costs twelve times as much to catch the same moves a fortnight earlier.
- **A low-confidence match is worse than no match** — Alerting a rep that a champion moved, when they did not, burns the credibility of every future alert. Set the threshold high, review the queue monthly, and accept that you will miss a few rather than sending one wrong.
- **Somebody has to own the follow-up** — This workflow produces a small number of high-value alerts, which is exactly the kind that gets admired and not actioned. Assign the alert to a named owner with a next step, or it becomes a monthly report nobody reads.

All four are documented by a vendor rather than observed by us, which is the useful part: a limit you can read is a limit you can design around before it costs you a week.

## What it costs to run

What each component bills on, and which line actually scales with your volume.

| Component | Billing | What drives it |
| --- | --- | --- |
| HubSpot | Any tier | A list, a comparison and a record creation. The sweep runs outside HubSpot, so no Data Hub requirement. |
| Reverse Contact | `Per credit` | One call per champion per month. A 500-person champion list is 500 calls a month, which is the smallest metered line on this site. |
| Orchestration | Free self-hosted | n8n on a monthly cron, or a Clay table with auto-update if a non-engineer owns the segment. |
| Slack | Free plan works | A handful of messages a month by design. |

This is the workflow with the best ratio of cost to outcome on the site, and the reason is the segment. Hundreds of calls a month against a list of people who already bought from you, producing a small number of named, warm accounts.

## [Reverse Contact](https://www.reversecontact.com)

We sell B2B people and company data, and we publish this directory. Every tier requirement, limit and sync direction in this chain was read from a vendor's own documentation, through the integration records each step rests on. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. [What has changed since](https://www.reversecontact.com/integrations-hub/changes) · [How we checked](https://www.reversecontact.com/integrations-hub/methodology), and what we will not claim

[Eugene Suslov](https://www.linkedin.com/in/eysuslov/)

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

- **Verified** — 2026-09-18
- **Sources** — 17 vendor documents
- **Paid placement** — None

### Read from

- [Reverse Contact API documentation](https://docs.reversecontact.com/getting-started)
- [Reverse Contact: credits](https://docs.reversecontact.com/guides/credits)
- [Reverse Contact: rate limits](https://docs.reversecontact.com/guides/rate-limits)
- [Reverse Contact: MCP delivery method](https://www.reversecontact.com/delivery-method/mcp)
- [Reverse Contact pricing](https://www.reversecontact.com/pricing)
- [HubSpot developers: custom code workflow actions](https://developers.hubspot.com/docs/api-reference/legacy/automation/workflow-actions/custom-code-actions)
- [HubSpot knowledge base: manage your notifications in Slack](https://knowledge.hubspot.com/integrations/manage-your-notifications-in-slack)
- [HubSpot community: Slack notification to the channel associated with the deal](https://community.hubspot.com/t5/CRM/Slack-notification-in-Workflows-Send-to-the-channel-associated/m-p/1177859)
- [Slack: web API rate limits](https://docs.slack.dev/apis/web-api/rate-limits/)
- [Slack: rate limit changes for non-Marketplace apps](https://docs.slack.dev/changelog/2025/05/29/rate-limit-changes-for-non-marketplace-apps/)
- [Slack: workflows and custom steps](https://docs.slack.dev/workflows/)
- [Slack: workflow steps](https://docs.slack.dev/workflows/workflow-steps/)
- [Slack: guide to Slack Workflow Builder](https://slack.com/help/articles/360035692513-Guide-to-Slack-Workflow-Builder)
- [Slack: sending messages using incoming webhooks](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/)
- [ClickUp: create a task webhook Automation](https://help.clickup.com/hc/en-us/articles/31126817112343-Create-a-task-webhook-Automation)
- [Google Apps Script: quotas for Google Services](https://developers.google.com/apps-script/guides/services/quotas)
- [Gong: what the Gong API provides](https://help.gong.io/docs/what-the-gong-api-provides)

## Questions

### Can Reverse Contact detect job changes?

It returns current role and company against an identity you already hold, with a last-updated timestamp, and markets change-aware signals for tracking updates across people and companies. The change detection itself is a comparison you run: current answer against what your CRM believes. The workflow is the diff, not the lookup.

### How often should I run the sweep?

Monthly. Profile data reflects a move when it becomes public, which is days to weeks after the fact, so a daily sweep costs twelve times as much to catch the same moves slightly earlier. Weekly is defensible for a small, very high-value champion list.

### Should I overwrite the old contact record?

No. Create a new contact at the new company and link it to the original. The deal history on the old record is the reason this person is worth an alert; edit it away and you have destroyed the asset while capturing the signal.

### What if the match is uncertain?

Send it to a review queue rather than to a rep. Reverse Contact returns null with a confidence score instead of a best guess, and you can raise the precision threshold on the request. One wrong alert costs more credibility than three missed ones cost pipeline.

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant
