Template

Sync contact and company signals in HubSpot

Time to build: 8 min
Difficulty: Medium
Tools: HubSpot ▪ Lusha ▪ Zapier

This Zapier workflow pulls Lusha Signals for your HubSpot contacts, like promotions, role changes, and seniority updates, and writes them back to HubSpot. When a signal points to a change at the company level, it updates the company record too, so contact and account data stay in sync.

Why sync contact and company signals in HubSpot?

Most CRMs treat contact and company enrichment as separate, one-time tasks. But a change at the contact level often means something changed at the company, too.

This workflow connects the two. Contact signals flow into account data automatically, so segmentation, routing, scoring, and reporting all run on current information.

What this workflow does

  • Starts when a contact is created or reaches a specific lifecycle stage
  • Pulls Lusha Signals for the contact, like promotions, seniority changes, and role updates
  • Updates the contact in HubSpot with the current title, seniority, and last signal date
  • Updates the company record when a signal points to a company-level change
  • Flags accounts that need review or show high intent

How to set it up

01

Connect your apps in Zapier

Ensure active connections for:

  • HubSpot: permission to read/update contacts and companies
  • Lusha: access to contact and company signals
02

Configure the HubSpot trigger

Choose when enrichment should run:

  • New contact created
  • Specific lifecycle stage reached

Best practice: Limit triggers to contacts with work emails or known companies to reduce noise.

03

Configure Lusha Signals enrichment

Identify contacts using:

  • Work email
  • LinkedIn URL
  • Full name + company

Retrieve signals such as:

  • Promotion or seniority change
  • Role or department update
  • Authority or decision-maker indicators
04

Update HubSpot contact records

Write back fields like:

  • Current job title
  • Seniority
  • Last signal date
  • Custom “Lusha Signal Detected” flag

These fields power downstream workflows.

05

Update HubSpot company records (conditional)

If the signal suggests a company-level change:

  • Update company size, industry, or growth indicators
  • Flag the account as “Needs Review” or “High-Intent”

This ensures account views stay accurate.

06

Test end-to-end

Create a test contact and confirm:

  • Signals are retrieved correctly
  • Contact fields update as expected
  • Company updates occur only when relevant

What to do next

  • Trigger workflows automatically: Enroll enriched contacts into sales, expansion, or nurture workflows.
  • Add scoring logic: Increase lead or account scores when seniority or authority increases.
  • Alert teams in real time: Add Slack or email alerts for high-impact changes.
  • Track enrichment freshness: Report on how recently contacts and companies were updated by signals.
  • Standardize CRM hygiene: Use this play as your default enrichment layer for HubSpot.

The goal: Contact changes don’t happen in isolation. This play ensures HubSpot reflects who changed, what changed, and where it matters—keeping both contacts and companies continuously enriched and ready for action.

FAQ

  • Use this Zapier workflow. It pulls Lusha Signals for your contacts and updates both the contact and the company record in HubSpot.

  • Promotions, seniority changes, role or department updates, and decision-maker indicators.

  • Only when a contact signal points to a company-level change. Otherwise, only the contact is updated.

  • You choose the trigger: new contacts, or contacts that reach a specific lifecycle stage.

  • A work email, a LinkedIn URL, or a full name with a company.

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.