One approval, no passwords
CRMmaps is a HubSpot app. You connect it on HubSpot's own install screen (OAuth), and an admin approves it once for the whole portal.
- Uninstall any time, and access stops.
- Coming to the HubSpot App Marketplace.
Two-way with
HubSpot.
CRMmaps reads your records straight from HubSpot and writes back only what your team asks it to. Here's every connection, so you know exactly what you're approving.
CRMmaps is in development and coming to the HubSpot App Marketplace.
CRMmaps reads
- Records
- Addresses
- Owners
CRMmaps writes
- Owner, label or property
- Note
Step 1: Install from HubSpot
Only the access it uses
The permissions CRMmaps asks for when you install it, in plain words.
- Contacts, companies, deals and tickets Read and update
- Owners Read, to know who's who
- Custom objects Optional Only if your portal has them, so installs never fail on plans without them
- Basic connection HubSpot's standard scope for connecting an app
Step 2: Choose how it works
Choose where an assignment lands
Your admin picks one of three ways. Whichever you pick, CRMmaps checks that HubSpot saved the change before it says it's done.
Links the person to the record with a label you choose, like Assigned. Requests use a Requested label. CRMmaps only adds or removes its own label and leaves the record's other associations and labels alone. Labels need HubSpot Professional or Enterprise.
Choose who can assign
Seats are your HubSpot users. Only the dispatchers your admin chooses can assign.
| Who | See the map | Assign |
|---|---|---|
| Dispatchers your admin chooses | Yes | Yes |
| Others with a seat | Yes | No |
| People without a seat | Card summary | No |
Step 3: Open any record
A map in every record
The CRMmaps card sits on contacts, companies, deals, tickets and custom-object records. It shows who's assigned, who's been requested and the nearest people who can take the job.
One button opens the full map in a HubSpot pop-up, so you never leave the record.
Your HubSpot data, live
CRMmaps reads records, properties and associations straight from HubSpot. There's no import or export, and HubSpot stays the source of truth.
It works out map coordinates for your addresses and keeps them on its side. It never rewrites your HubSpot address fields.
Stays in step
New records, edited addresses and reassignments in HubSpot reach the map through HubSpot's webhooks. Edits on the map save to HubSpot.
Step 4: Assign from the map
A note on every change
Every assign, request or unassign adds a note to the record's timeline, so HubSpot's history shows who did what.
Works with your automation
Assignments are ordinary HubSpot changes to an owner, a label or a property, so your existing workflows can react to them, for example to notify the assignee.
CRMmaps will ship workflow templates for common notifications.
- WhenThe record's owner, label or property changes
- ThenNotify the assignee
Under the hood
How CRMmaps protects your portal
- HubSpot's access tokens are encrypted at rest.
- Every request from HubSpot is verified by its signature.
- Map sessions are short-lived.
- CRMmaps keeps its use of your portal's HubSpot API limit in check, so your other integrations keep working.
- An admin can mark an object as containing health information. CRMmaps then never sends those addresses to a mapping or routing provider.
Maps on real roads
Maps are built on OpenStreetMap data, and drive times follow real roads.
Later: iOS and Android apps, iPhone Duo included, will use the same HubSpot data and log check-ins to the HubSpot timeline.
Questions from HubSpot admins
What does CRMmaps store?
A map index of the records you choose to map: their coordinates, owners and the properties you filter and rank by. Also your CRMmaps settings and a log of assignments made in CRMmaps. HubSpot's access tokens are encrypted at rest. There's no import or export: CRMmaps reads your records from HubSpot, which stays the source of truth.
Will CRMmaps change our existing data?
Only when your team does something in CRMmaps, like assigning someone or editing on the map. Each assignment updates the owner, label or property your admin picked and adds a note to the record. CRMmaps never rewrites your address fields, and it leaves associations and labels it didn't add alone.
What happens if we uninstall?
Access stops, so CRMmaps can no longer read or change anything in your portal, and CRMmaps deletes what it stored about your portal within 30 days. The owners, labels, properties and notes it wrote are ordinary HubSpot data, so they stay on your records.
Do we need a developer to set it up?
No. An admin installs CRMmaps from HubSpot's install screen, then chooses how assignments land and who can assign. Notifications run on your own HubSpot workflows, and CRMmaps will ship templates for common ones.
Does it work with custom objects?
Yes, if your portal has them. The CRMmaps card works on custom-object records too. Custom-object access is optional, so CRMmaps still installs on plans without them.
When can we install it?
CRMmaps is in development. Early access opens to a small group of HubSpot teams first, and then CRMmaps comes to the HubSpot App Marketplace. Join the early-access list to get an invite.
Be first on the map.
CRMmaps opens to a small group of HubSpot teams first. Leave your work email and we'll send your invite.