01
Pipeline by stage
Stage conversion, velocity and coverage, with history so you can see how the quarter moved.
Stage → stage %
CRM
Pipedrive + Kimo
Sales pipeline and activities. Model your pipeline next to product usage and billing to forecast with numbers sales and finance both trust.
- Auth
- OAuth 2.0
- Sync
- Hourly
- Setup
- ≈ 2 min
Live demo workspace with fictional data · no signup, no credentials needed
kimo / connectors / pipedriveSyncing
Sync loghourly
- Succeeded:contacts+680 rowsnow
- Succeeded:deals+2,299 rows2m ago
- Succeeded:companies+1,518 rows4m ago
- Succeeded:contacts+737 rows6m ago
Rows synced · 30 days
86.1M
Workspaces
14%
What you can do
What teams build with Pipedrive
Pipedrive on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
02
Win rate by source
Tie every won deal back to the channel that created the lead in the first place.
Win rate · source
03
Usage-aware forecasting
Combine deal stage with product usage to flag deals that look likely to slip.
Forecast vs. target
Objects & tables
Exactly what gets synced
Kimo maps Pipedrive into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
3 tables · 14 fields
Tables
contacts
Incremental≈ 5,180,000 rows| Field | Type | Notes |
|---|---|---|
| id | id | Primary key |
| string | ||
| lifecycle_stage | enum | Low-cardinality dimension |
| owner_id | id | References owner |
| source | enum | Low-cardinality dimension |
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model
From raw Pipedrive tables to a certified metric
A starter model Kimo suggests the moment Pipedrive is connected. Every join is editable.
Pipedrive · Sales pipeline
Contacts and deals joined with product signups and billing on email and account id.
- Pipedrivecontacts
- PostgreSQLusers
- Stripesubscriptions
Model
email · account_id
Measurespipelinewon
Pipeline value · last 30 days
$84.6K+1.6% wk/wk
Fictional data · hover the chart for daily values
Setup
Connect Pipedrive 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 Pipedrive”
You are redirected to Pipedrive 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 accounts
Choose which accounts 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 Pipedrive
Step 2 of 3 · Kimo demo workspace
Kimo wants read-only access to your Pipedrive account
read-only accessread
Accounts
- Northwind · Pipedrive
- Northwind EU · Pipedrive
Read-only access
Illustration only · placeholder values, never real secrets
Works great with
Pair Pipedrive with the rest of your stack
Kimo suggests these joins automatically when both sources are connected.
FAQ
Pipedrive questions, answered
By default Kimo syncs Pipedrive hourly. You can change the schedule per table, or trigger a sync manually from the connector page.
Pipedrive · OAuth 2.0 · Hourly
See your Pipedrive data in Kimo in 2 min.
Try it on the live demo workspace first, then connect your own account when you are ready.