Enrich contacts before a HubSpot email send — Lusha in HubSpot Breeze

Trigger — Contact added to campaign verification list

Set the enrollment trigger to “Contact is member of list — [your pre-send list].” When you build a campaign audience in HubSpot, add contacts to this verification list first. The Workflow fires immediately for each contact added and completes verification before you activate the send.

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’s email address. Lusha returns their current verified status — confirmed in seat, departed, or not found — along with their current title and verified email address.

Decision — Route by verification result

Add an If/Then branch on the Lusha response. Three paths: Departed — contact has left the company. Email changed — contact is in seat but email address has changed. Confirmed — contact is verified in seat with current email. Each path triggers a different action.

Action — Suppress departed contacts

On the Departed path: set lusha_contact_status to “Departed,” set lusha_send_suppressed to true, and remove the contact from the campaign send list. The contact remains in HubSpot for reporting purposes but is excluded from the send.

Action — Update stale contact data

On the Email changed and Confirmed paths: update the email address, job title, and seniority with the current verified values from Lusha. Personalization tokens in the campaign email pull from these updated fields — so the send goes out with accurate data, not stale records.

Output — Verified send list ready for campaign activation

Every contact on the campaign list is verified, updated, or suppressed. A verification summary property on each contact tells you the outcome — confirmed, departed, or email updated. Review the suppressed count in the list view before activating the send.

Create the verification properties

In HubSpot → Settings → Properties, add the three verification properties listed in the table above to the Contact object. Create lusha_verification_result as a Dropdown select with four options: Confirmed, Departed, Email updated, Not found.

Create the pre-send verification list

In HubSpot → Contacts → Lists → Create list → Active list. Name it “Lusha Pre-Send Verification.” This is the list you add contacts to before every campaign. The Workflow fires automatically for each contact enrolled.

Build the Contact-based Workflow

In HubSpot → Automation → Workflows → Create Workflow → Contact-based. Set enrollment trigger to “Contact is member of list — Lusha Pre-Send Verification.” Enable re-enrollment so contacts are re-verified each time they are added to the list for a new campaign.

Add the verification webhook

Add action → Send a webhook. POST to https://api.lusha.com/v2/contacts/search. Request body: { "emailAddress": "{{contact.email}}" }. Add header api_key: YOUR_LUSHA_API_KEY.

Add If/Then branches for each verification result

Add an If/Then branch checking the webhook response. Departed path: set lusha_contact_status to Departed, set lusha_send_suppressed to true, set lusha_verification_result to Departed. Email changed path: update email, set result to Email updated. Confirmed path: set result to Confirmed. All paths: set lusha_verification_date to today.

Create your verified send list

Create a second Active list filtered by “Lusha verification result is Confirmed OR Email updated” AND “Lusha send suppressed is false.” Use this list as the actual campaign audience in HubSpot Marketing Hub. Departed contacts are automatically excluded.

Review suppressed count before activating the send

Before activating the campaign, check the verification list view. Filter by lusha_verification_result = Departed to see the suppressed contacts. Review the count — a high suppression rate signals that the contact list source needs attention before the next campaign.

Test with a small list

Add 10 to 20 test contacts to the verification list including at least one you know has recently changed companies. Confirm the Workflow fires, the departed contact is suppressed, and the verification date is set on all contacts. Check the Workflow history tab if results are unexpected.