HubSpot Event and Badge List Enrichment
Expand a raw event or badge-scan export of just names and companies into full contact records with MoltSets, before it lands in HubSpot for post-event outreach. Every email returned is graded A-F for deliverability risk, and you pick which grades to keep.
example prompts
-
Enrich this event attendee list before I import it into HubSpot -
Expand these badge-scan names and companies into full contacts with email and title
about this skill
What this skill does
Takes a raw event or trade show attendee export, usually just a name and a company, and expands each row into a full contact record before it goes anywhere near HubSpot. It resolves title, business email, LinkedIn, and firmographics through MoltSets, flags rows it cannot resolve, and hands back an import-ready file so post-event outreach starts with real data rather than a name and a booth number.
Chain
Raw attendee export (CSV or sheet: name + company, sometimes title)
to normalise company name to domain (best-effort, or ask for domain if ambiguous)
to MoltSets:
search_business_profile_by_name (name + domain -> title, LinkedIn, seniority)
linkedin_to_best_email (LinkedIn URL -> business email)
search_companies (domain -> firmographics)
to flag unresolved rows (ambiguous company name, no match found)
to hubspot/search-crm-objects (check for existing contacts, avoid duplicate import)
to hubspot/create-object (import new, enriched contacts)
Inputs
- Attendee file - the raw export (CSV or sheet) with at minimum name and company
- Event context - event name and date, to tag the imported contacts
- Company resolution - whether to guess domains from company name automatically or confirm ambiguous ones with you first
- Import scope - all resolved rows, or only rows above a confidence threshold
- Acceptable risk scores - which A-F deliverability grades to keep (recommended: A, B, C and F; D excluded)
How it works
- Reads the raw export and identifies what is present per row (name, company, sometimes a title)
- Normalises the company name to a domain, flagging ambiguous names (common names, multiple possible matches) for confirmation
- Runs
search_business_profile_by_namewith name plus domain to return title, seniority, and LinkedIn URL - Runs
linkedin_to_best_emailwhere a LinkedIn URL was returned, to get a business email - Runs
search_companieson the domain to attach firmographics to each row - Checks resolved contacts against existing HubSpot records to avoid duplicate import, then creates the new, enriched contacts tagged with the event name and date
Output
| Name (as scanned) | Company | Resolved Domain | Title | Risk | Confidence | Action |
|---|
Rows in export: X
Rows resolved: X/N (XX%)
Ambiguous / flagged: X
Already in HubSpot: X
New contacts imported: 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_companies filters on query (company name only), domain, industry, linkedin_industry, naics_code, employee_range, revenue_range, country, and state.
domainbeats free text every time - exact match, and full URLs are normalised automatically, sohttps://www.acme.com/aboutneeds no cleanup first.- Filters are free precision - a filters-only search runs ~40x cheaper than one carrying free text, and most firmographic work needs no
queryat all. - Three industry vocabularies -
industryis 22 broad buckets ("Information Technology", not"Computer Software"); niches like software or insurance live inlinkedin_industry("Software Development") ornaics_code. A thin result is often a neighbouring-label problem rather than a coverage one. - Company location is derived from where the team is based, and large multinationals resolve to a single one of their offices - pair location with another filter on enterprise or international targeting.
- Range values are exact and skewed -
"1-10"dominates employee counts,"$500k - $1M"dominates revenue.
Tips
- Requires the HubSpot remote MCP (mcp.hubspot.com) and the MoltSets MCP connected in the same client
- Badge scans and business card OCR are frequently misspelled, so check flagged rows manually rather than force-matching them
- Tag every imported contact with the event name and date so lifecycle and attribution reporting can isolate this cohort later
- Run a coverage check on the first 20 to 50 rows before processing a large export, to catch a systematic domain-guessing problem early
- Custom objects are not reachable through HubSpot's remote MCP, so import to standard contact properties
- 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