HubSpot Bulk List Enrichment

What this skill does

Runs your enrichment waterfall across an entire saved HubSpot list and writes the results back to the CRM. It pulls every member of the list with pagination, checks your MoltSets token budget up front, enriches each contact for email, mobile phone, title, and firmographics, throttles to respect HubSpot's write limits, and batches the updates back. This is the CSV waterfall workflow, sourced from and returned to HubSpot directly.

Chain

HubSpot saved list or segment
  to hubspot/search-crm-objects (paginate)    (pull all members)
  to MoltSets get_usage                        (pre-flight: tokens + daily results remaining)
  to per-contact waterfall:
      linkedin_to_best_email
      linkedin_to_mobile_phone
      reverse_linkedin_lookup / search_business_profile_by_name
  to throttle to HubSpot 100 req / 10s
  to hubspot/update-object (batched)           (write enriched fields, source + date)

Inputs

• HubSpot list - the saved list or segment to enrich
• Fields to enrich - any combination of email, mobile phone, title, seniority, and firmographics
• Budget cap - a token ceiling for the run, checked against get_usage before starting
• Overwrite policy - fill blanks only, or refresh selected fields

How it works

1. Pulls every member of the HubSpot list, paginating through the full set
2. Calls get_usage first to read tokens remaining and the daily results limit, then compares that against the list size and your budget cap
3. For each contact, runs the waterfall: linkedin_to_best_email for email, linkedin_to_mobile_phone for a verified mobile, and reverse_linkedin_lookup (or search_business_profile_by_name when there is no LinkedIn URL) for title, seniority, and firmographics
4. Skips fields that are already populated unless the overwrite policy says to refresh them
5. Throttles write-back to stay inside HubSpot's limit of 100 requests per 10 seconds, batching updates where possible
6. Writes all enriched fields back with a source and date stamp

Output

List size:               X
Contacts enriched:       X
Emails found:            X/N (XX%)
Mobiles found:           X/N (XX%)
Titles filled:           X/N (XX%)
MoltSets tokens used:    X
Daily results remaining: X

Tips

• Requires the HubSpot remote MCP (mcp.hubspot.com) and the MoltSets MCP connected in the same client
• Run the pre-flight coverage check on a sample of 20 to 50 contacts first to estimate cost before committing the full list
• MoltSets only charges tokens when data is returned, so a low match rate does not burn your budget on misses
• Watch the daily results limit as well as your token balance; a large list can hit the daily cap before the token cap
• Batch write-back rather than updating one contact at a time, and keep the run inside HubSpot's 100 requests per 10 seconds limit
• Custom objects are not reachable through HubSpot's remote MCP, so write to standard contact and company properties