---
name: champion-job-change-alerts
description: Build a monthly sweep that detects when a past customer contact changes company and turns it into pipeline: re-resolve the champion list, diff against the CRM, and alert the account owner on confirmed moves. Use when the user wants job-change tracking, champion tracking, or to find warm accounts from existing customer relationships.
---

# Champion job-change alerts

> Generated from https://www.reversecontact.com/integrations-hub/workflows/champion-job-change
> Every tier requirement and limit below was read from the vendor's own documentation on 2026-09-18.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**Tools in this workflow:** HubSpot, Reverse Contact, Slack.
**Build effort:** Hours.

## What you are building

A monthly sweep over the people who already bought from you. Re-resolve each one, compare the current company to what the CRM believes, and where they have moved and the confidence is high, create a record at the new company and tell the account owner.

## Ask this before writing anything

How big is the champion list? This is a precision play, not a coverage one. Hundreds of contacts attached to closed-won deals, plus advocates on lost deals. If the user wants to sweep their whole database, push back: it costs an order of magnitude more, produces alerts nobody reads, and the signal disappears in the noise within a month.

## Prerequisites

| What | Where to get it | Notes |
|---|---|---|
| A champion list in the CRM | Contacts on closed-won deals, plus advocates on lost ones | Hundreds, not thousands |
| Reverse Contact API key | Workspace > API Keys | One call per champion per month, the smallest metered line of any workflow here |
| CRM write access | A private app with contacts read and write | You will create records, not edit the originals |
| A scheduler | n8n on a monthly cron, or a Clay table on auto-update | n8n if an engineer owns it; Clay if the segment definition changes |

## The tools, and how to call them

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

### HubSpot

- **Base:** `https://api.hubapi.com`
- **Auth:** `Authorization: Bearer <private-app-token>` for a private app, or OAuth for a marketplace app. Full CRM API access is on every tier including Free.

| Call | Request | What it does |
|---|---|---|
| `PATCH /crm/v3/objects/contacts/{contactId}` | `{ "properties": { "rc_title": "VP Sales" } }` | Update a contact. Send only the properties you own. |
| `POST /crm/v3/objects/contacts/search` | `{ "filterGroups": [...], "properties": [...] }` | Find records by property. Use this to pull the slice that is missing a field. |
| `POST /crm/v3/objects/contacts/batch/update` | `{ "inputs": [ { "id": "...", "properties": {...} } ] }` | Batch of up to 100. Prefer this over per-record PATCH at volume: it is one request against the rate limit. |

**Rules that will cost you time if you skip them:**

- **Rate limits.** A private app gets 190 requests per 10 seconds on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000 / 625,000 / 1,000,000 calls **per account, shared across every app**. A public OAuth marketplace app is capped at 110 per 10 seconds per installing account.
- **Calling an external API from a workflow needs Data Hub Professional or Enterprise.** Both the webhook action and the custom code action live in that hub, not in Sales Hub. Check this before designing an in-HubSpot build.
- **Custom code actions get 20 seconds and 128 MB.** Combined length of all workflow secrets is capped at 1,000 characters. Secrets are read with `process.env.NAME`.
- **Workflows:** up to 50 simple on Starter, up to 300 fully customisable on Professional.
- **Never write to a property a human maintains.** Use prefixed properties (`rc_*`) and promote with a separate workflow only where the human field is empty.

**HubSpot custom code action (Node 20):**

```javascript
// Input field: email   Output fields: rc_status, rc_title, rc_company, rc_headcount
// Secret: RC_API_KEY
const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  const res = await axios.post(
    'https://api.reversecontact.com/v2/enrich/persons',
    { email },
    { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } }
  );

  const person = res.data?.data?.person;
  const company = res.data?.data?.company;

  // null means "not found", not "try harder". Write nothing and flag it.
  if (!person) return callback({ outputFields: { rc_status: 'no_match' } });

  callback({ outputFields: {
    rc_status:    'matched',
    rc_title:     person.currentPosition?.title || '',
    rc_company:   company?.name || '',
    rc_headcount: company?.employeeCount || 0
  }});
};
```

Docs: https://developers.hubspot.com/docs/api/overview

### Slack

- **Base:** `https://slack.com/api`
- **Auth:** `Authorization: Bearer xoxb-...` (bot token). Scope `chat:write`, plus `chat:write.public` to post to a channel the bot has not joined.

| Call | Request | What it does |
|---|---|---|
| `POST /api/chat.postMessage` | `{ "channel": "C0123", "text": "...", "blocks": [...] }` | The only call most of these workflows need. Use this when you need to choose the channel at runtime. |

**Rules that will cost you time if you skip them:**

- **HubSpot's Slack workflow action cannot route to the channel associated with the record.** It sends to a channel chosen at design time. If you need per-record routing, look the association up yourself and call `chat.postMessage` directly.
- Creating a Slack channel from a HubSpot workflow requires HubSpot Professional or Enterprise.
- Route only events a named human must act on within minutes. A channel that fires forty times a day gets muted, and a muted channel is indistinguishable from a working one in the admin screen.

Docs: https://api.slack.com/methods/chat.postMessage

### n8n

- **Base:** `Self-hosted or n8n Cloud`
- **Auth:** Credentials are stored in n8n, not in the workflow JSON, so the workflow stays safe to export and review.

| Call | Request | What it does |
|---|---|---|
| `NODE HTTP Request` | `Authentication: Generic > Header Auth. Name: Authorization. Value: Bearer rc_your_api_key` | There is no dedicated Reverse Contact node and you do not need one. Five minutes to configure, and no node update can break it. |
| `NODE HubSpot Trigger` | - | Authenticates with a **developer API key from a HubSpot developer account**, not a private app token, because that is how HubSpot exposes the webhooks API. Free to create, and nobody expects it. |
| `NODE Wait + IF` | - | The polling loop for Reverse Contact's /live endpoints: Wait 5s, GET the webhook id, IF status != succeeded loop back. |

**Rules that will cost you time if you skip them:**

- HubSpot allows **one webhook URL per app**. Route several object types through one subscription and branch inside n8n with a Switch node.
- Self-hosting is usually the reason this route was chosen: records never leave infrastructure you control. Do not quietly move it to a third-party cloud.
- n8n must be reachable by HubSpot for webhook triggers to fire.

Docs: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest

## Build it

### 1. Build the list, deliberately small

Contacts attached to closed-won deals, plus anyone with a real activity history on a lost deal. Those are the people whose move is worth an alert. Everyone else generates noise and costs credits.

### 2. Re-resolve monthly, not daily

Profile data reflects a move when it 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.

### 3. The diff is the workflow

Compare `currentPosition.companyName` to what the CRM holds. The enrichment is only interesting where it disagrees with the record you already have. Build the comparison, not just the lookup.

### 4. Threshold on confidence, then review

A low-confidence answer is a maybe, not a job change. Set a threshold and send everything under it to a review queue rather than to a rep. One wrong alert costs more credibility than three missed ones cost pipeline.

### 5. Create at the new company. Never overwrite the old record.

The deal history on the original record is the reason this person is worth an alert. Create a new contact at the new company and link it to the original. Editing the old one destroys the asset while capturing the signal.

### 6. Alert the account owner, with both records linked

Name the person, the old company, the new company and the deal history. This is the part that turns a data point into pipeline, and it only works if somebody owns the follow-up.

## Gotchas

- Never overwrite the original contact. This is the mistake that makes the whole play worthless, and it is easy to make because "update the record" is the obvious action.
- This produces a small number of high-value alerts, which is exactly the kind that gets admired and not actioned. Assign each one to a named owner with a next step.
- Expect a lower resolution rate on contacts whose only address is a personal one. Route those to review rather than lowering the threshold to catch them.

## What breaks, from the vendors' own docs

- **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.

## How to verify it works

- Seed the test with a contact you know has moved and confirm the diff fires.
- Seed it with one you know has not and confirm it does not.
- Confirm the original record is untouched and the new record links back to it.
- Check a low-confidence result lands in the review queue rather than in Slack.
- Count alerts in month one. Single digits on a few hundred champions is normal and correct.

## What this costs to run

| 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.

## Sources

- Reverse Contact: https://docs.reversecontact.com/getting-started
- HubSpot: https://developers.hubspot.com/docs/api/overview
- Slack: https://api.slack.com/methods/chat.postMessage
- n8n: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest
- This workflow, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/workflows/champion-job-change

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
