Auto-build buying committees for new HubSpot deals with Lusha

Build an agent workflow that runs every 2 hours on a cron trigger and constructs the full buying committee for each newly created HubSpot deal, then notifies the deal owner in Slack with an org chart and a multi-threading recommendation.

Step 1. Use HubSpot Search Deals to find every deal where createdate is within the last 2 hours. Request the deal's primary company association in the same call. Also request the deal owner so you know who to notify.

Step 2. For each deal, use HubSpot Get Deal (or Get Company on the associated company) to pull the account's domain and the list of contacts already associated to the deal. If the company has no domain, skip the deal and move on.

Step 3. Use the agent's judgement to pick the buyer titles that matter for this deal based on the company's industry, size, and deal amount. Start from a default set of CTO, VP Engineering, Head of Procurement, Director of RevOps, and the likely manager of the existing primary contact, but adapt it (for example, add Head of Security for regulated industries, or add CFO for large deals).

Step 4. Call Lusha Search Prospecting Contacts filtered by the company domain plus the chosen titles. Take the returned contact IDs and the requestId, then call Lusha Enrich Prospecting Contacts to reveal verified email and phone. Cap the reveals at the top 5 stakeholders per deal so credit spend stays predictable.

Step 5. Dedupe against the contacts already on the deal (and against existing HubSpot contacts by email). For each genuinely new stakeholder, use HubSpot Create Contact with the enriched fields and then use HubSpot Create Association to link the new contact to the deal.

Step 6. Use Slack Bot Send a Message to DM the deal owner (look them up by email on the HubSpot owner record). The message should contain a tidy org chart with each committee member's name, title, email, phone, and their role on the committee (champion, economic buyer, technical buyer, procurement, etc.), followed by a one-paragraph recommendation on who to multi-thread next and why. Keep the formatting in Slack mrkdwn.

Constraints: skip deals with no associated company domain; cap reveals at 5 per deal; never duplicate a contact that is already on the deal or already in HubSpot by email; do nothing if the 2-hour window returned zero new deals.

Additional information

What does this prompt do?

Sweeps HubSpot every two hours for deals created in the last cycle so nothing slips through.
Pulls the account domain from each deal's associated company and asks Lusha for the right buying titles (engineering, procurement, RevOps, plus a likely manager for the primary contact).
Reveals verified email and phone for the top five stakeholders, adds them as contacts in HubSpot, and links them to the deal.
Sends the deal owner a Slack message with an org chart of the committee and a short recommendation on who to multi-thread first.

What do I need to use this?

A HubSpot account with permission to read deals and companies and create contacts.
A Lusha account with API access and enough credits for prospecting and reveals.
A Slack workspace where the deal owner can receive a direct message.

How can I customize it?

Change the sweep cadence (every hour, every four hours, or weekday mornings only).
Tune which buyer titles matter for your product, your average deal size, or your industry.
Adjust the stakeholder cap per deal (default five) to control how many reveals you pay for.
Route the Slack notification to a channel instead of a DM, or include the sales manager.

Frequently asked questions

Why build the buying committee instead of just enriching the primary contact?

Most B2B deals stall when only one champion is engaged. Multi-threading across the committee (engineering, procurement, RevOps, and the champion's manager) shortens cycle time and protects the deal if your champion leaves or goes quiet.

What happens if the company on the deal has no domain?

The workflow skips that deal and moves on. Domain is what Lusha uses to find coworkers, so without it there is nothing reliable to search against.

Will it create duplicate contacts in HubSpot?

No. Before creating anyone, the agent checks whether the stakeholder is already on the deal or already in your CRM and skips or re-links them instead of duplicating.

How are Lusha credits used?

Searching is free, but revealing email and phone consumes credits. The workflow caps reveals at the top five stakeholders per deal so spend stays predictable.

Can the deal owner change who they want suggested?

Yes. Ask the agent to weight specific titles (for example, prioritize security buyers for enterprise deals), exclude others, or change the size of the committee.