---
name: moltsets-hubspot-mobile-phone-backfill
description: Use this skill to add carrier-verified mobile numbers to the HubSpot contacts on your open deals, sourced through MoltSets and written straight back to the CRM.
---

# HubSpot Mobile Phone Backfill

Add mobile phone numbers to the HubSpot contacts who matter most: the ones attached to live pipeline. Find deal-associated contacts with no phone on file, pull a carrier-verified mobile through MoltSets, format it, dedupe it, and write it back to the contact record. Scoping the run to open deals keeps token spend tied to revenue rather than the whole database.

## Triggers

"Add mobile numbers to the contacts on my open HubSpot deals", "backfill carrier-verified mobiles for deal contacts that have no phone". Use when the user wants verified mobile numbers on the contacts attached to open deals.

## Requirements

- HubSpot remote MCP (mcp.hubspot.com) and the MoltSets MCP connected in the same client
- Custom objects are not reachable through HubSpot's remote MCP - write to the standard mobile phone property

## Chain

```
HubSpot deal-associated contacts
  -> hubspot/search-crm-objects        (contacts on open deals with no phone)
  -> hubspot/list-associations         (confirm deal association + deal owner)
  -> resolve LinkedIn URL per contact  (skip contacts with no LinkedIn URL)
  -> MoltSets:
       linkedin_to_mobile_phone        (LinkedIn URL -> carrier-verified mobile)
  -> dedupe + format to E.164
  -> 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

## Steps

1. Pull contacts associated with open deals that have no phone number in HubSpot.
2. Confirm the deal association and capture the deal owner so results can be routed back to the right rep.
3. Take the LinkedIn URL on the record - contacts with no LinkedIn URL are skipped and flagged (mobile only comes from `linkedin_to_mobile_phone`).
4. Run `linkedin_to_mobile_phone` on each LinkedIn URL for a carrier-verified mobile.
5. Format each number to E.164 and dedupe against any existing phone data.
6. Write the mobile back to HubSpot with a source and date stamp.

## Output

| Name | Company | Deal | Owner | Existing Phone | Found Mobile | Source Tool | Action |
| --- | --- | --- | --- | --- | --- | --- | --- |

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

## Tips

- 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.
- Throttle write-back to stay inside HubSpot's limit of 100 requests per 10 seconds.