HubSpot

The connection is made with HubSpot's own approval screen, the same one every HubSpot app uses. You sign in as yourself, see the exact permissions before agreeing to them, and can withdraw them later from either side. Nothing is copied and pasted, and we never hold a password of yours.

You need to be signed in to StackScan, and to be a HubSpot user who is allowed to install apps. In most portals that means a Super Admin.

1. Open Integrations in StackScan

In your dashboard, go to My Accounts → Integrations. It sits next to API Tokens, because connecting a CRM is the same kind of decision as issuing a key.

2. Press Connect HubSpot

That sends you to HubSpot. The connection belongs to the StackScan workspace you are in at the time, so if you keep more than one, check you are in the right one first.

3. Pick the HubSpot account

If your login reaches several portals, HubSpot asks which one to connect. Choose the portal whose companies you want enriched. A sandbox or developer test account is a perfectly good place to start.

4. Review the permissions and agree

HubSpot lists what StackScan is asking for. Nothing beyond companies is on that list. HubSpot also shows an unverified-app notice at this point; that is explained below.

5. You land back on Integrations

The card turns green and names the portal it is attached to. On this first connection StackScan creates the property group and the 6 properties, so they are on your company records before anything is written to them.

6. We start the first run with you

Tell us you are connected and we will run a preview across a sample of your records, so you can see the values before any are saved. You approve, we run it properly, and after that it can repeat on a schedule.

What HubSpot will ask you to approve

Four permissions, all of them about companies:

• oauth - required of every HubSpot app. It is what lets the connection exist and be refreshed.
• crm.objects.companies.read - find the companies that have a domain.
• crm.objects.companies.write - write the 6 StackScan properties onto them.
• crm.schemas.companies.write - create those 6 properties, once, on the first connection.

Contacts, deals, tickets, quotes, files and your users are not on the list, so they are not reachable even by mistake.

What lands on the record

Six new company properties, grouped under StackScan so they sit together rather than scattered through the record:

We only ever write these 6. Nothing standard is touched, nothing is deleted, and contacts and deals are never read. Because they are ordinary HubSpot properties, everything else in HubSpot works on them straight away: list filters, workflows, lead scoring, reports.

Disconnecting

Two independent switches, and either one is enough to stop us:

• From StackScan. Integrations → Disconnect. The stored tokens are deleted, not just marked inactive.
• From HubSpot. Settings → Integrations → Connected Apps → StackScan → Uninstall. Access ends the moment you do it, with no involvement from us. This is also where HubSpot shows you which permissions the app currently holds.

Doing both is tidiest. The 6 properties and the data already written stay on your records either way; delete the StackScan property group if you want those gone too.

About the "unverified app" notice

Partway through the approval step HubSpot warns that you are connecting an unverified app and asks you to confirm. It means StackScan has not yet completed HubSpot's marketplace review. It does not mean the connection is insecure, and it is not caused by anything on your side.

Every app is unverified until it is listed, and HubSpot only accepts a listing after an app already has live customer installs, so the notice necessarily comes first. The permissions HubSpot shows you on that screen are the real and complete set either way, and the disconnect routes work exactly the same.

Will it overwrite what my team has entered?

No. We only write the 6 StackScan-prefixed properties. Your Industry, City and Country fields are untouched, so you can compare ours against yours rather than losing either.

What about companies with no website?

Skipped, and not charged. Everything we know is keyed on the domain, so a record without one cannot be matched. Resolving a company name to a domain is not something we do today.

What does it cost?

One Bulk Lookup Credit per company enriched - the same credits as the dashboard and the API, with nothing extra to buy. Companies we cannot match are free, and records without a domain are skipped before anything is looked up.

Every run starts with a count and a cost. If your balance will not cover the whole list, it enriches what it can afford and tells you exactly which records were left, so a top-up and a re-run finishes the job without paying twice for anything.

Who in my team can connect it?

Anyone who can sign in to your StackScan workspace and who is allowed to install apps in HubSpot, usually a Super Admin. The connection is held by the workspace rather than by the person, so it survives that person leaving. What it will not survive is their HubSpot account being deleted, which is a good reason to connect as an admin rather than from a personal seat.

Do I have to reconnect it periodically?

No. HubSpot access expires every thirty minutes and StackScan renews it in the background before it runs out. You would only reconnect if someone uninstalled the app in HubSpot, and the Integrations card tells you plainly when that has happened rather than failing quietly.

How big a portal can it handle?

Tens of thousands of companies. Runs are resumable, so a large sync can stop and continue without re-charging for records it already did.

Can I try it on a few records first?

Yes, and we would encourage it. A HubSpot developer test portal is free, connects through the same screens, and behaves identically. Or connect your real portal and let us cap the first run to a small list.