HubSpot
Send Target Account intent from Leapio to the matching company in HubSpot, so your reps see the latest signal without leaving the CRM.
The HubSpot integration writes Target Account intent onto the matching company in HubSpot. When a signal fires for a target account, Leapio updates that company with the latest signal, how strong it was, when it happened, a short summary, and a link back to Leapio. Your reps see the intent on the record they already work in.
HubSpot is available on the Pro plan and higher.
What Leapio Writes
Leapio writes six fields, in a Leapio property group on the company:
| Field | What it holds |
|---|---|
| Leapio Company ID | The Leapio company this record is linked to. |
| Leapio Latest Signal | The most recent signal, such as High-Intent Page Visit. |
| Leapio Signal Strength | The strength of that signal, from 1 (low) to 3 (high). |
| Leapio Signal Time | When the signal happened. |
| Leapio Intent Summary | A short summary of the signal. |
| Leapio Link | Opens the account in Leapio. |
You can keep these Leapio-owned properties, or point any field at one of your own HubSpot company properties of the same type. Leapio Company ID always uses its own Leapio property, since it is the key that ties the two records together.
The signals that reach HubSpot are the account-level intent signals: Target Account Visited, High-Intent Page Visit, Return Visit, Usage Spike, and Custom Rule Matched.
Connect HubSpot
- Go to Integrations → Browse Catalog and open HubSpot.
- Click Connect. Leapio sends you to HubSpot to approve access.
- Approve the connection in HubSpot, then return to Leapio.
On the HubSpot side, the person connecting needs to be a Super Admin or have the App Marketplace Access permission. Until HubSpot has reviewed and listed the Leapio app, HubSpot shows an unverified-app warning: to continue, type I accept the risk and connect. See HubSpot's docs on installing apps and the confirmation step for unverified apps.
Set Up the Fields
After connecting, the HubSpot card in Your Integrations shows Needs Setup with a Set Up Fields button. Open it to review each field:
- Create Leapio Properties creates the Leapio property group and any missing default properties in HubSpot. It never edits a property that already exists.
- Or point a field at one of your own HubSpot properties of the same type, then Save Field Choices.
Each field shows a state (Ready, Missing, Archived, Incompatible, or Read-Only) so you can tell what is left before Leapio writes anything. Use Check Again after you fix something in HubSpot. The card reads Connected once every field is ready.
Send Signals to HubSpot
Once every field is Ready, turn on Send Signals on the HubSpot card in Integrations → Your Integrations. Leapio creates a Send Notification action named Send Signals to HubSpot that writes each Target Account visit, high-intent page visit, return visit and usage spike to HubSpot as it happens. Turn the switch off to pause it.
To change what it sends, open the action in Actions → Your Actions:
- Add or remove triggers, including your custom rules.
- Turn on Create Missing Companies if you want Leapio to create a company in HubSpot when none matches.
- Use Send Test from the action's menu to write a test to HubSpot.
You can also build your own Send Notification action for HubSpot from Actions → Browse Catalog. An action that sends to HubSpot sends nowhere else, so post to Slack from a separate action. The switch pauses and resumes every action that sends to HubSpot.
Each signal Leapio writes to HubSpot uses 1 Action, the same as any notification. Writes that are skipped, held for review or fail cost nothing, and so does Send Test.
How Matching Works
Leapio matches by company domain.
- No match: the write is skipped, unless Create Missing Companies is on, in which case Leapio creates the company in HubSpot.
- One match: Leapio updates that company.
- Two or more matches: Leapio leaves them alone for you to review, rather than guessing which is right.
For example, a Usage Spike for acme.com updates the one HubSpot company whose domain is acme.com. An
older signal never overwrites a newer one already written, so the fields always reflect the latest intent.
Statuses and Reconnecting
The HubSpot card in Your Integrations shows one status:
- Connected: working.
- Needs Setup: connected, but the fields still need setup. Use Set Up Fields.
- Error: HubSpot access was lost. Use Reconnect to authorize again.
If HubSpot access is revoked, for example when someone uninstalls the app in HubSpot, the card moves to Error with a Reconnect button, and nothing more is sent to HubSpot until you reconnect. Updates can still reach HubSpot for up to 30 minutes after an uninstall, until Leapio's current access token expires.
Disconnecting
Open the HubSpot card's ⋮ menu and choose Disconnect. Leapio deletes its HubSpot tokens, cancels any writes still queued, and uninstalls the app from your HubSpot account, unless another Leapio organization is still connected to it. HubSpot emails you when the app is uninstalled. Actions that send to HubSpot stop delivering until you connect it again. The Leapio fields already written stay on your HubSpot companies.
If you uninstall Leapio in HubSpot instead (Settings → Integrations → Connected Apps), Leapio loses access and asks you to reconnect. Neither way deletes the Leapio properties. If you no longer want them, archive them in HubSpot under Settings → Properties (company properties, Leapio group). Your own properties that you pointed fields at keep the values Leapio wrote.