01
Lead → customer funnel
Lifecycle stages from subscriber to customer, with conversion and time in stage.
MQL → SQL → Won
CRMPopular
HubSpot + Kimo
Contacts, companies and deals from HubSpot, joined with product usage and Stripe to build a pipeline you can forecast on.
- Auth
- OAuth 2.0
- Sync
- Hourly
- Setup
- ≈ 2 min
Live demo workspace with fictional data · no signup, no credentials needed
kimo / connectors / hubspotSyncing
Sync loghourly
- Succeeded:engagements+591 rowsnow
- Succeeded:companies+1,372 rows2m ago
- Succeeded:deals+1,429 rows4m ago
- Succeeded:contacts+2,210 rows6m ago
Rows synced · 30 days
39.1M
Workspaces
57%
What you can do
What teams build with HubSpot
HubSpot on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
02
Pipeline coverage
Weighted pipeline against quota for every owner and quarter, refreshed hourly.
Coverage 3.1×
03
Closed-won vs. collected
Match deals to Stripe subscriptions so bookings and revenue reconcile.
deals ⋈ stripe
Objects & tables
Exactly what gets synced
Kimo maps HubSpot into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
4 tables · 17 fields
Tables
contacts
Incremental≈ 79,900,000 rows| Field | Type | Notes |
|---|---|---|
| id | id | Primary key |
| string | ||
| lifecyclestage | string | |
| hs_analytics_source | enum | Low-cardinality dimension |
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model
From raw HubSpot tables to a certified metric
This model ships with the Business Intelligence demo. Open it to see every join and measure.
Recurring revenue
MRR, new customers, expansion and churn from Stripe + product DB.
- Stripesubscriptions
- PostgreSQLaccounts
- HubSpotdeals
Model
customer_id = stripe_id
Measuresmrrnew_customerschurned
MRR · last 30 days
$4.9K-1.7% wk/wk
Fictional data · hover the chart for daily values
Setup
Connect HubSpot in 2 min
No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.
- 1
Click “Connect HubSpot”
You are redirected to HubSpot to sign in. Kimo never sees your password.
- 2
Approve read-only scopes
Kimo requests the narrowest scopes available. You can revoke access at any time.
- 3
Pick portal
Choose which portal to sync. Add more later without reconnecting.
- 4
First sync and schema mapping
Kimo backfills history, maps contacts and suggests joins with your other sources.
Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.
Connect HubSpot
Step 2 of 3 · Kimo demo workspace
Kimo wants read-only access to your HubSpot account
crm.objects.contacts.readreadcrm.objects.deals.readreadcrm.objects.companies.readread
Portal
- Northwind (Portal 2481937)
Read-only access
Illustration only · placeholder values, never real secrets
Works great with
Pair HubSpot with the rest of your stack
Kimo suggests these joins automatically when both sources are connected.
FAQ
HubSpot questions, answered
By default Kimo syncs HubSpot hourly. You can change the schedule per table, or trigger a sync manually from the connector page.
HubSpot · OAuth 2.0 · Hourly
See your HubSpot data in Kimo in 2 min.
Try it on the live demo workspace first, then connect your own account when you are ready.