What it is.
You ask Claude to enrich your newest HubSpot contacts. It pulls the ones never enriched, shows the Apollo credit cost and waits for a yes. Then it matches them in Apollo, 10 people per call.
A Python script decides what gets written, so the same input always gets the same result. Apollo's high-confidence matches write into empty fields, and the email domain has to agree with the company Apollo found.
Everything else goes to an Enrichment review segment with the reason attached. A domain mismatch is often a job change, so the note shows both domains.
What you get.
- A SKILL.md that runs the pass in order, from the access check to the report.
- A decision script with no dependencies, plus a sample run that covers every outcome.
- A field map from Apollo fields to HubSpot properties that you can edit to fit your portal.
- Tracking properties on each contact, so a rerun skips people you already paid for.
- A review CSV that puts Apollo's values beside HubSpot's for each contact held back.
How to set it up.
Add the zip in Claude's Skills settings. For Claude Code, unzip it into ~/.claude/skills/.
Connect Apollo from Customize > Connectors and sign in with OAuth. Any Apollo plan works, including free.
Connect HubSpot the same way, signed in as a user who can edit contacts.
Ask for a first run on five contacts. Claude creates the Enrichment properties and asks you to confirm them.
Read the credit estimate before you say yes. It's at most 1 credit per contact, since the skill asks for no phone numbers.
Open review.csv after the run and work through the Enrichment review segment by hand.
Edit scripts/field_map.json if your portal already has its own LinkedIn or seniority property.
Use cases
Clean up this week's inbound
Ask Claude to enrich contacts created since Monday. Titles and company details are in HubSpot before reps start calling.
Backfill an old import
Point it at a list from a past event. It works through the contacts in batches and skips anyone already enriched.
Spot job changes
Title conflicts and domain mismatches land in the report. Those are often people who moved companies after they signed up.
Test it before a live run
Run the script on the sample folder first. You see every outcome without spending a credit.
Best for
HubSpot teams already on Apollo
The credits come with your Apollo plan, and this spends them on contacts already in your CRM.
RevOps leads who guard the CRM
Filled fields stay as they are, and HubSpot asks you to confirm every write.
Teams that work in Claude
It runs from a Claude chat, so there's no automation server to host or monitor.