Enrich and score companies on a scheduled cadence — Lusha in HubSpot Breeze

Trigger — Scheduled Workflow runs every Monday at 5am

Set the enrollment trigger to “Company property — Lusha enriched date — is unknown” OR “Lusha enriched date is more than 30 days ago.” Enable re-enrollment. Companies enriched more recently than 30 days are skipped to avoid unnecessary credit consumption.

Action — Fire webhook to refresh company firmographics

Add a “Send a webhook” action. POST to https://api.lusha.com/v2/companies/search with the company domain or name. Lusha returns the current verified profile — industry, employee count, revenue range, funding stage, HQ location, and tech stack — refreshed from Lusha’s database as of today.

Action — Detect and flag significant changes

Add If/Then branches comparing Lusha’s response against existing HubSpot company properties. Employee count variance above 20%, funding stage changes, and HQ location changes are flagged by setting lusha_flagged_for_review to true and appending a note to lusha_change_log. Minor updates are written silently.

Action — Verify primary contact for each company

For each company, fire a second webhook to /v2/contacts/search for the primary associated contact. Departed contacts are flagged. Title changes are logged. The lusha_last_verified timestamp is updated on all contacts checked regardless of outcome.

Action — Recalculate ICP score with current data

After firmographic refresh, add If/Then branches to re-evaluate the ICP criteria using the updated properties. Write the new score to lusha_icp_score on the Company record. Log the score change and date to lusha_change_log so you can see when an account’s fit changed.

Output — Current, verified, scored company database

Every company in your HubSpot portal reflects current reality. Reps, campaigns, and Breeze agents running on this data work from verified firmographics — not records that haven’t been touched since the account first entered the CRM.

Create the enrichment properties on the Company object

In HubSpot → Settings → Properties, add all company enrichment properties listed in the table above. These are the write targets for the webhook response mapping.

Build the Company-based Workflow

In HubSpot → Automation → Workflows → Create Workflow → Company-based. Set enrollment trigger to “Lusha enriched date is unknown OR is more than 30 days ago.” Enable re-enrollment. Set schedule to run every Monday at 5am.

Add the company enrichment webhook

Add action → Send a webhook. POST to https://api.lusha.com/v2/companies/search. Request body: { "name": "{{company.name}}" } or use the domain if available: { "domain": "{{company.domain}}" }. Add header api_key: YOUR_LUSHA_API_KEY.

Map response fields and detect significant changes

Add “Set property value” actions to write refreshed firmographics to the Company record. Add If/Then branches for significant change detection — employee count variance above 20%, funding stage change, HQ change. Flag the company for review and append to the change log on any significant change path.

Add the contact verification webhook

Add a second webhook to /v2/contacts/search for the primary associated contact. Map the response to update contact title and status. Flag departures and log the new company. Update lusha_last_verified on the contact regardless of outcome.

Add ICP rescoring branches

After the firmographic update, add If/Then branches that re-evaluate the ICP criteria using the updated property values. Write the new ICP score to lusha_icp_score and append the change to lusha_change_log with today’s date.

Create a flagged companies list view

In HubSpot → Companies → Create view. Filter by lusha_flagged_for_review = true. Add lusha_change_log and lusha_icp_score as visible columns. This gives your team a weekly review queue — companies where something meaningful changed and human review is warranted before the next outreach or call.

Test with a sample batch

Before activating at full scale, add an additional enrollment filter limiting to companies in a specific industry or owner. Confirm the enrichment fields populate correctly, the change log appends without overwriting, and the ICP score recalculates. Full troubleshooting guidance at docs.lusha.com/guides.