Sales Navigator list to verified CRM contacts
Evaboot + HubSpot
Who it's for
SDRs who build lead lists in Sales Navigator and want them in the CRM with verified emails, without creating duplicates or paying for leads the team already has. Evaboot can be swapped for PhantomBuster or Wiza. HubSpot can be swapped for Salesforce, Attio or Pipedrive.
What you get
The de-duplicated list, with the HubSpot contacts waiting for approval. Sample output: every company and person in it is fictional.
List: 'Q4 Logistics VPs' in Sales Navigator, 42 leads Evaboot export: 42 credits used (1 per lead), 36 verified emails | # | Name | Title | Company | Email | HubSpot match | Action | |---|---|---|---|---|---|---| | 1 | Dana Okafor | VP Operations | Larkspur Freightworks (fictional) | [email protected] | none | Create | | 2 | Sam Whitlock | Head of Logistics | Quarry Lane Analytics (fictional) | [email protected] | Contact exists (same email) | Skip | | 3 | Priya Raman | Director, Supply Chain | Mossgate Labs (fictional) | [email protected] | Company exists, no contact | Create | | 4 | Alex Rivera | VP Fulfillment | Fernhill Software (fictional) | none found | Contact exists at old company | Review | | 5 | Morgan Ellery | COO | Bramblecrest Shipping (fictional) | [email protected] | none | Create | Summary: 42 leads. 29 new with a verified email, 7 already in HubSpot (skip), 6 with no verified email (skip). Row 4 looks like a job change: HubSpot has Alex at a different company. Flagged for you, not changed. No HubSpot records created yet. No Sales Navigator lists changed. Reply 'create 29' to add the new contacts, or list row numbers to leave out.
Time and cost
Estimate About 15–20 minutes for a list of 100 leads, most of it reviewing the match table.
Assumptions: One Sales Navigator list of about 40 leads, one export, and one de-duplication pass.
- Evaboot: One credit and quota check, one list lookup, and one export after you approve it (charged per lead, and it uses your Sales Navigator seat's daily quota). Some tools use credits. Exports cost 1 credit per lead (email included), each recurring-export run charges per lead, find_email_single costs 1, find_emails 1 per email found, verify_email_single 1, verify_email 1 per email checked; search building, lists, saved searches, alerts and integrations are free. Exports also use the daily quota of the connected Sales Navigator seat. Source: docs.evaboot.com, checked 2026-10-16
- HubSpot: One contact search by email and one company search by domain per lead, then one contact created per approved new lead. Credit use not confirmed by HubSpot.
Exact credit costs depend on your plan with each vendor. Check the tool pages before a large run.
MCP servers
Every server is confirmed in: ClaudeChatGPT
-
ClaudeChatGPTClaude CodeCursorCopilotRead + writeSome tools use credits
https://mcp.evaboot.com/mcp -
ClaudeChatGPTRead + writeCredits not confirmedNeeds admin or IT
https://mcp.hubspot.com
Set up in a chat app
Every server in this recipe is confirmed for Claude and ChatGPT. Connect each one, then paste the prompts below into one conversation.
- Connect Evaboot without code (Claude, ChatGPT)
- Connect HubSpot without code (Claude, ChatGPT)
Developer setup
Auth setup and mcp.json for Claude Code and Cursor
- Evaboot: Sign in with OAuth, or pass an API key as a Bearer token for headless use.
- HubSpot: Sign in with OAuth in your client (run
/mcpin Claude Code). Do it once interactively, and the client stores and refreshes the token.
Put this in .mcp.json (Claude Code, project root) or ~/.cursor/mcp.json (Cursor). Swap the example keys for your own, and don't commit real ones. Remove the // comment lines if your client requires strict JSON.
{
"mcpServers": {
"evaboot": {
"url": "https://mcp.evaboot.com/mcp"
// headless alternative: "headers": { "Authorization": "Bearer YOUR_EVABOOT_API_KEY" }
},
"hubspot": {
"url": "https://mcp.hubspot.com"
}
}
}
Step-by-step prompts
- Use Evaboot to show me my Sales Navigator lead lists and saved searches with their lead counts, and check my Evaboot credits and daily quota. Don't change any lists or searches.
- For {list_name}, tell me how many leads it has and how many credits the export will use. Start an export with verified emails only after I approve it.
- Search HubSpot for each exported lead by email, and for their company by domain. Show me a table: name, title, company, email, HubSpot match (none, contact exists, company exists with no contact, possible job change) and the action you suggest. Don't change anything.
- After I approve it, create HubSpot contacts only for the rows marked 'Create' that have a verified email. Then give me the count created and a list of the rows you skipped and why.
Run it on a schedule (optional)
- This works best by hand, right after you finish building a list.
- Evaboot can set up recurring exports, but each run charges per lead. If you want one, approve it once you've run the manual version and trust the de-duplication.
- In a scheduled run, stop at the match table and approve the HubSpot creates yourself.
Where this goes wrong
- Duplicates with a different email. A lead may already be in HubSpot under an old or personal email. Besides the email match, check name plus company domain, and mark those rows 'Review' instead of 'Create'.
- Job changes created as new people. Sales Navigator shows the current company. HubSpot may have the same person at their old one. If the name matches a contact at another company, flag it as a possible job change and don't create a second record.
- Free email domains treated as companies. If a lead's email is on a personal domain, don't use that domain to match a HubSpot company. Match on the company name instead, and list those rows for review.
- Credits spent on a bigger list than expected. Exports cost one Evaboot credit per lead. Show the lead count and your remaining credits before the export, and stop if the list is larger than you planned.
Gotchas
- Evaboot exports need your own Sales Navigator seat, and they count against that seat's daily quota as well as your Evaboot credits.
- Evaboot can push exports straight to a CRM through its integrations. This recipe doesn't, so the de-duplication step always runs first.
- On Claude Team or Enterprise, an owner adds Evaboot in Organization settings. In ChatGPT, it's a custom connector that needs developer mode.
- HubSpot only shows records the connected user can see, so duplicates owned by other teams can be missed. Non-admin users need a Super Admin to approve the connector first.
Download
Get the prompts, guardrails and expected output as one Markdown file. Paste it into a Claude Project or ChatGPT project's instructions, or save it as CLAUDE.md for Claude Code.
Download sales-nav-list-to-crm.md
New recipe and breakage notes every week
Vendor sites: HubSpot. If we join an affiliate program, these links will be labeled as affiliate links.