HubSpot Campaign Segment Builder
Turn a targeting brief like "VP+ Fintech, 200-1000 employees" into a HubSpot static list, matching existing contacts first and topping up with net-new people from MoltSets. Every email returned is graded A-F for deliverability risk, and you pick which grades to keep.
example prompts
-
Build a campaign list of VP+ Fintech contacts at 200-1000 employee companies, top up from MoltSets if needed -
I need 500 Director+ Marketing contacts at mid-market SaaS companies for a campaign
about this skill
What this skill does
Builds a campaign-ready list against a plain-English brief. It translates the brief into title, seniority, industry, and company size filters, matches against your existing HubSpot contacts first, and only pulls net-new people from MoltSets to make up the shortfall to your target list size. Existing contacts are never duplicated, and the output is a single static list sized to the brief.
Chain
Targeting brief (title / seniority / industry / size / target count)
to hubspot/search-crm-objects (existing contacts matching the brief)
to compare match count against target list size
to MoltSets:
search_people (title/seniority/department + industry + employee_range, if shortfall)
to dedupe candidates against existing HubSpot contacts
to linkedin_to_best_email (fill email gaps on net-new candidates)
to hubspot/create-object (create net-new contacts)
to hubspot/create-list / add-to-list (build the static list from existing + net-new)
Inputs
- Targeting brief - title/seniority, department, industry, employee range, and any other firmographic filter
- Target list size - how many total contacts the campaign needs
- Existing-contact priority - whether to use existing HubSpot contacts first, always, or only above a certain match quality
- List name - the HubSpot static list the result should be saved to
- Acceptable risk scores - which A-F deliverability grades to keep (recommended: A, B, C and F; D excluded)
How it works
- Parses the brief into structured filters: title or seniority, department, industry, and employee range
- Searches existing HubSpot contacts against those filters first
- If the existing match count falls short of the target list size, runs
search_peoplein MoltSets with the same filters to source net-new candidates - Dedupes the candidates against existing HubSpot contacts by email and domain plus name
- Runs
linkedin_to_best_emailon any net-new candidate missing an email - Creates the net-new contacts in HubSpot and adds both existing and net-new contacts to the named static list
Output
| Name | Company | Title | Seniority | Industry | Risk | Source | Existing/Net-New | Added to List |
|---|
Target list size: X
Existing matches used: X
Net-new candidates sourced: X
Net-new added to HubSpot: X
Final list size: X
MoltSets tokens used: X
Email risk scores:
A: X B: X C: X D: X F: X
kept (accepted grades): X
filtered (excluded): X
Search filters
search_people filters on query, company, company_domain, country, state, city, seniority, department or functional_area, industry, linkedin_industry, naics_code, employee_range, and revenue_range.
- Filters are free precision - execution cost comes from the free-text
query, so a filters-only search runs ~40x cheaper and lands more precisely. A barequeryis never the right shape; at minimum it getscountryattached (~99% fill rate). - Size and revenue apply to the person's current employer - "VPs at 51-200 employee software companies" is one call, not a company search followed by a people search.
- Three industry vocabularies - broad
industrybuckets, LinkedIn's ~150 niche labels, or a NAICS code at any depth. Shortening the code widens the net. - Sparse filters are the usual cause of a thin result set -
seniority/industry/departmentare ~60% filled andnaics_code/linkedin_industry~50%, and every filter is exact-match, silently dropping records where the field is empty. - Probe before you pull -
search_peoplehas no count-only mode, so run it atlimit: 1first and readresults.totalbefore paginating. (count_only: trueis free, but only onsearch_linkedin_profile.)
Tips
- Requires the HubSpot remote MCP (mcp.hubspot.com) and the MoltSets MCP connected in the same client
- Prioritising existing HubSpot contacts first keeps token spend down and avoids working an account you already have a relationship with
- If the brief is vague on seniority, run a small sample first and confirm the mapping before sourcing the full shortfall
- A per-company cap keeps a single large account from dominating the list at the expense of coverage
- Custom objects are not reachable through HubSpot's remote MCP, so create standard contact records and standard lists
- Every returned email carries an A-F deliverability risk score; you're asked up front which grades to keep, and out-of-range grades are shown and flagged rather than silently dropped