Alert reps when a key contact changes roles — Lusha in HubSpot Breeze

Example outputs in this workflow are illustrative — they reflect the structure, fields, and format of real Lusha API output, but were not pulled from a live session. Build this workflow with your own Lusha API key and HubSpot portal to see live results.

A deal that was progressing well goes quiet. The rep follows up twice. No reply. Six weeks later in a pipeline review, someone asks whether the contact is still at the company. They’re not — they left five weeks ago, two days after the last call. The deal didn’t stall. The champion left and nobody knew.

This workflow runs a daily check on every key contact in your HubSpot portal via the Lusha API, detects departures and role changes, updates the contact record, creates a task for the owning rep, and optionally fires a Slack notification. The rep finds out within 24 hours — not six weeks later in a pipeline review.

Requires: Lusha API key · HubSpot Workflows (Professional or Enterprise) · HubSpot admin access · Slack (optional)

How it works

This workflow runs on a daily scheduled cadence. It checks every monitored contact in your HubSpot portal against Lusha’s verified database, detects departures and role changes, updates the contact record, and alerts the owning rep before the situation affects a deal.

1

Trigger — Scheduled Workflow runs daily at 6am

Set the enrollment trigger to “Contact property — Lusha monitor contact — is equal to true.” Enable re-enrollment so contacts are checked every time the Workflow runs. Tag contacts on open deals, champions, and economic buyers with this property to bring them into the monitoring scope.

2

Action — Fire webhook to verify contact via Lusha

Add a “Send a webhook” action. POST to https://api.lusha.com/v2/contacts/search with the contact email. Lusha returns their current status — confirmed in seat, departed, or promoted — along with their current title and company.

3

Decision — Detect departure or role change

Add an If/Then branch comparing the Lusha response company against the contact’s associated Company in HubSpot. Company changed = departure. Title changed at same company = promotion. No change = update lusha_last_verified only and exit.

4

Action — Update contact record and create task

Departure path: set lusha_contact_status to “Departed,” log the new company to lusha_new_company, and create a high-priority task for the contact owner. Promotion path: update the job title, log the previous title to lusha_previous_title, create a standard task.

5

Action — Send internal email or Slack notification

For departures on contacts associated with open deals, add a “Send internal email notification” action to the contact owner. Optionally fire a Slack notification via a second webhook action to the rep’s Slack channel with the contact name, company, departure date, and a link to the HubSpot record.

6

Output — Rep alerted within 24 hours of any change

The rep receives a task in HubSpot and an optional Slack notification with full context — who left, where they went, which deal is affected, and what to do next. They know within 24 hours, not six weeks later in a pipeline review.

Detection logic

POST https://api.lusha.com/v2/contacts/search
Body: { "emailAddress": "{{contact.email}}" }

Compare Lusha response to HubSpot contact record:

IF response.company != contact.associated_company
  → DEPARTURE detected
  → lusha_contact_status = "Departed"
  → lusha_new_company = response.company
  → lusha_departure_date = today
  → Create HIGH priority task for contact owner
  → Send Slack notification if contact has open deal

IF response.title != contact.jobtitle
   AND response.company = contact.associated_company
  → PROMOTION detected
  → lusha_previous_title = contact.jobtitle
  → jobtitle = response.title
  → lusha_contact_status = "Promoted"
  → Create standard task for contact owner

IF no change
  → lusha_last_verified = today
  → lusha_contact_status = "Active"
  → Exit workflow

Example Slack alert on departure

⚠ Champion departure detected — action required

Contact: R.M. — VP of Sales
Company: [Company A]
Open deal: [Deal name] — Deal stage 3 — $42K
Departed: [date]
New company: [New Company]

Find the new owner at [Company A] before this deal goes cold.
View contact in HubSpot →

Custom properties to add to the Contact object

Property labelTypeInternal name
Lusha — Contact statusDropdown (Active / Departed / Promoted / Unverified)lusha_contact_status
Lusha — Previous companySingle-line textlusha_previous_company
Lusha — New companySingle-line textlusha_new_company
Lusha — Previous titleSingle-line textlusha_previous_title
Lusha — Departure dateDate pickerlusha_departure_date
Lusha — Last verifiedDate pickerlusha_last_verified
Lusha — Monitor contactSingle checkboxlusha_monitor_contact

Build steps

1

Create the monitoring properties

In HubSpot → Settings → Properties, add all contact monitoring properties listed in the table above. Create lusha_contact_status as a Dropdown select with four options: Active, Departed, Promoted, Unverified.

2

Tag contacts to monitor

Manually check lusha_monitor_contact on any contact you want this workflow to watch — champions, economic buyers, primary contacts on open deals. You can also build a separate Workflow that automatically tags all contacts associated with open deals above a minimum deal value.

3

Build the scheduled Workflow

In HubSpot → Automation → Workflows → Create Workflow → Contact-based. Set enrollment trigger to “Lusha monitor contact is equal to true.” Enable re-enrollment so contacts are checked every time the Workflow runs. Set the schedule to run daily.

4

Add the verification webhook

Add action → Send a webhook. POST to https://api.lusha.com/v2/contacts/search with the contact email. Add header api_key: YOUR_LUSHA_API_KEY.

5

Add If/Then branches for detection

Add an If/Then branch comparing the webhook response company name against the contact’s associated Company name. Build three paths: departure, promotion, and no change. Each path sets the appropriate properties and creates the appropriate task.

6

Add Slack notification for departures (optional)

On the departure path, add a second webhook action to your Slack incoming webhook URL. Pass the contact name, company, departure date, new company, and a link to the HubSpot contact record in the request body. Fire only when the contact is associated with an open deal above your minimum ACV threshold.

7

Test with a known contact change

Identify a contact in your HubSpot portal who you know has recently changed companies or been promoted. Check lusha_monitor_contact on that contact and manually trigger the Workflow from the contact record. Confirm the departure or promotion is detected, the properties are updated correctly, and the task is created with the right priority.

Example outputs in this workflow are illustrative — they reflect the structure, fields, and format of real Lusha API output, but were not pulled from a live session. Build this workflow with your own Lusha API key and HubSpot portal to see live results.

Built by: Lusha
Time to build: 45 min
Difficulty: Medium
Tools: HubSpot, Lusha, Slack
Type: Template

FAQ

  • How is this different from HubSpot's native contact activity tracking?

    HubSpot’s native activity tracking monitors what a contact does inside your marketing funnel — emails opened, pages visited, forms submitted. It has no way of knowing whether the contact still works at the company, whether their title has changed, or where they went if they left. Lusha’s verification checks the contact against a live, independently sourced database of B2B contact data. The two systems are tracking completely different things — HubSpot tracks behavior, Lusha tracks reality.

  • Should I monitor all contacts or only key ones?

    Start with key contacts only — champions, economic buyers, and primary contacts on open deals above your minimum ACV threshold. Monitoring every contact in your HubSpot portal consumes API credits on contacts that have no active commercial relationship and creates alert noise that dilutes the value of genuine departure notifications. The <code>lusha_monitor_contact</code> checkbox gives you precise control. A good starting rule: automatically tag any contact associated with an open deal as monitored, and automatically untag contacts on deals closed more than six months ago.

  • What if the contact moved to a new company that's also a target account?

    The departure path logs the new company name to <code>lusha_new_company</code>. If that company is already in your HubSpot portal as a target account, you can add a step to the departure path that searches for the company and creates a new association or a task to follow the contact to their new role. This is one of the highest-value motions in outbound — a champion who already knows your product and just joined a new company is a warm introduction, not a cold outreach. The Write the outreach when a contact changes jobs play handles the message for exactly this scenario.

  • Can I trigger an immediate alert rather than waiting for the daily run?

    Yes — add a second Workflow on the Contact object triggered by “Lusha contact status changes to Departed.” This Workflow fires in real time the moment the departure is written to the contact record and can send an immediate internal email or Slack notification without waiting for the next daily run. Use this for contacts on high-value deals where a 24-hour delay matters — set the trigger filter to “contact is associated with a deal with amount greater than [your threshold]” to avoid over-notifying on lower-priority contacts.

  • What happens to open deals when a champion departs?

    The workflow creates a task for the contact owner but does not automatically update the associated deal — that decision belongs to the rep. The task description includes the deal name and a prompt to find the new owner of the deal at the account. To surface this in deal views as well, add a step to the departure path that updates a custom deal property — “Lusha — Champion status” — to “Departed” on all deals associated with the contact. This makes the departure visible in deal pipeline views and pipeline review filters without requiring a rep to open the contact record first.

Related Plays

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.

Get free access Read the Docs