HubSpot Event and Badge List Enrichment

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

How it works

1. Reads the raw export and identifies what is present per row (name, company, sometimes a title)
2. Normalises the company name to a domain, flagging ambiguous names (common names, multiple possible matches) for confirmation
3. Runs search_business_profile_by_name with name plus domain to return title, seniority, and LinkedIn URL
4. Runs linkedin_to_best_email where a LinkedIn URL was returned, to get a business email
5. Runs search_companies on the domain to attach firmographics to each row
6. 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

Rows in export:              X
Rows resolved:                X/N (XX%)
Ambiguous / flagged:          X
Already in HubSpot:           X
New contacts imported:        X
MoltSets tokens used:         X

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