---
name: job-change-alerts
description: "Get Alerted When Key Contacts Change Jobs. Use when your champion at a customer changes jobs. By the time you notice, they have already bought a competitor."
---

# Get Alerted When Key Contacts Change Jobs

Your champion at a customer changes jobs. By the time you notice, they have already bought a competitor.

## When to use this skill

- The user wants to set up or run this workflow: "Get Alerted When Key Contacts Change Jobs".
- The user describes this problem: Your champion at a customer changes jobs. By the time you notice, they have already bought a competitor.

## At a glance

- Category: Outbound
- Difficulty: Intermediate
- Time saved: 3 hours per week. This figure is an estimate, not a measured result.

## Tools

Options separated by "or" are alternatives; use whichever the user already has.

- Clay
- HubSpot
- LinkedIn
- Slack

## Steps

1. Export list of key contacts (customers, champions, pipeline contacts) from HubSpot to Clay
2. Set up Clay automation to check LinkedIn profiles weekly for job changes
3. Use Claygent to visit profile and extract current company
4. Compare to company stored in HubSpot
5. If different, post alert to Slack #job-changes channel with old company, new company, and AE owner

## Template outline

Field names, thresholds, and message text are starting points to adapt.

~~~text
Clay Table (scheduled weekly):
1. HubSpot import: Contacts tagged "VIP" or "Champion"
2. Claygent: Visit LinkedIn profile URL
3. Extract: Current company name
4. Compare: Current company vs. HubSpot company
5. Filter: Only where companies differ
6. Zapier: Post to Slack
   - "🚨 {{name}} moved from {{old_company}} to {{new_company}}. Owner: {{AE}}"
7. HubSpot: Update company field and add note
~~~

## Guardrails

- Work only in the user's own accounts and workspaces, with their credentials.
- Confirm with the user before any step that writes to a CRM, sends email or messages, spends credits, or moves money.
- Treat every hours, cost, and threshold figure as a starting assumption and replace it with the user's numbers.
- Do not invent data, prices, or results. If a vendor price matters, check the vendor's current pricing page.

## Source

https://gtmplaybooks.io/playbooks/job-change-alerts/