How to Send Google Maps Leads to HubSpot (No CSV)

In Mantis, connect HubSpot once with an access token, then select leads and click Send to CRM; each lead becomes a HubSpot Company (plus a Contact when there is a person or email), and sending again updates the same record instead of duplicating it. That is the whole flow for moving Google Maps leads to HubSpot — no spreadsheet in between. The rest of this guide is the detail: which token to create after HubSpot's October 2026 change, the exact scopes, and what to do when a send fails.

Three steps:

If you already collect local businesses with a Google Maps scraping tool — or you are still comparing Google Maps scrapers — this is how that list becomes CRM records instead of another CSV.

On 26 October 2026, HubSpot stopped letting accounts create new legacy private apps. Two things follow:

Mantis sends whatever token you paste as a Bearer token, which is how HubSpot documents both private app tokens and service keys. HubSpot's example service key starts with pat-na1-, the same prefix Mantis shows as the placeholder in its "Private app access token" field, so you paste either kind into that one field.

Who can create what: a service key requires a super admin or a user with the Developer tools access permission; a private app requires a super admin.

In your HubSpot account:

HubSpot's changelog names a second path, Settings → Integrations → Service Keys; use whichever one your account shows. Either way you end up with a key to copy; HubSpot's own example key starts with pat-na1-.

Keep the key somewhere safe until it is pasted into Mantis, and plan to rotate it later: HubSpot recommends rotating tokens every six months.

Before saving, Mantis checks the token with HubSpot: it reads the account, then reads companies to prove the scopes are present. If the check passes, the token is stored encrypted and is never shown again.

This is how you import local business leads into HubSpot as companies rather than rows in a file. Re-sending is safe: Mantis matches a company by domain first, then by exact name, so a company that already exists in HubSpot gets updated rather than duplicated. The exception: if a record was deleted in HubSpot since the last push, it is created again.

If you prospect every week, folding this send into a weekly prospecting routine keeps the CRM current without extra work.

Every sent lead lands as a HubSpot Company, with a Contact added when the lead includes a person or an email. The fields map like this:

The Contact is associated to its Company, so you see the person on the company record. Note the description field: it carries the prospecting context — category, area, rating and review count, signals, Mantis score, contact role, LinkedIn, and the list name — so the Company record shows why the lead was saved in the first place.

Two details worth knowing. A rejected token stops the batch early, so fix the token first and then re-select and resend — the dedupe rules mean resent leads update instead of duplicating. And HubSpot limits how fast any one app can call it: on Free and Starter accounts the limit is 100 calls per 10 seconds per app. If Mantis shows the rate-limit message, wait a minute and send again.

There are two other routes people use: export a CSV and import it into HubSpot, or wire up a marketplace or automation app. A CSV is a snapshot: every new list means another export, column mapping and import. A direct push sends from the screen where you found the leads, and re-sending updates the same company. If you are still deciding where leads should come from, see bought database vs live search.

I'm Tarun, founder of Mantis.