HubSpot Mobile Phone Backfill

What this skill does

Adds mobile phone numbers to the HubSpot contacts who matter most: the ones attached to live pipeline. It finds deal-associated contacts with no phone on file, pulls a carrier-verified mobile through MoltSets, formats it, dedupes it, and writes it back to the contact record. Scoping the run to open deals keeps token spend tied to revenue rather than the whole database.

Chain

HubSpot deal-associated contacts
  to hubspot/search-crm-objects        (contacts on open deals with no phone)
  to hubspot/list-associations         (confirm deal association + deal owner)
  to resolve LinkedIn URL per contact  (skip contacts with no LinkedIn URL)
  to MoltSets:
      linkedin_to_mobile_phone         (LinkedIn URL -> carrier-verified mobile)
  to dedupe + format to E.164
  to hubspot/update-object             (write mobile phone, source + date)

Inputs

• Deal scope - which pipeline stages to include (for example all open deals, or deals above a value threshold)
• Contact scope - contacts with no phone, or also those with an unverified landline
• Write-back field - the mobile phone property plus optional source and date properties
• Owner filter - optional, restrict to a specific rep or team

How it works

1. Pulls contacts associated with open deals that have no phone number in HubSpot
2. Confirms the deal association and captures the deal owner so results can be routed back to the right rep
3. Takes the LinkedIn URL on the record - contacts with no LinkedIn URL are skipped and flagged (mobile only comes from linkedin_to_mobile_phone)
4. Runs linkedin_to_mobile_phone on each LinkedIn URL for a carrier-verified mobile
5. Formats each number to E.164 and dedupes against any existing phone data
6. Writes the mobile back to HubSpot with a source and date stamp

Output

Deal contacts scanned:   X
Missing phone numbers:   X
Mobiles found:           X/N (XX%)
Written back to HubSpot: X
MoltSets tokens used:    X

Tips

• Requires the HubSpot remote MCP (mcp.hubspot.com) and the MoltSets MCP connected in the same client
• Carrier-verified mobiles carry a higher token cost than email lookups, so scoping to open deals keeps spend deliberate
• linkedin_to_mobile_phone returns the strongest result, so prefer it whenever a LinkedIn URL is on the record
• Confirm your outbound calling and SMS consent posture before enriching phone data at scale
• Custom objects are not reachable through HubSpot's remote MCP, so write to the standard mobile phone property
• Throttle write-back to stay inside HubSpot's limit of 100 requests per 10 seconds