Pipedrive is a sales-first CRM built around deals moving through a visual pipeline. Connecting it as a data source through the Connectors library syncs your deals, people, organizations, and activities into your Alta workspace, where they become training data for Alta and a foundation for your metrics, dashboards, and Luna analysis. Once it's flowing, you can measure pipeline value, win rates, and sales velocity — and ask Luna questions in plain English. Pipedrive connects with credentials (an API token).

Who this is for: RevOps and sales teams who run their pipeline in Pipedrive and want that data measured across Alta.

Before you start

Get your Pipedrive API token (in Pipedrive: account settings → Personal preferences → API). The token inherits that user's visibility, so use a user who can see all the deals you want to analyze.
If you use multiple pipelines, note which ones you care about — you'll usually analyze them separately.
Connect a source only once per workspace. If Pipedrive already shows Connected, edit the existing connection.

Connect Pipedrive

Open Connectors from the sidebar.
Find Pipedrive via the CRM tab or the Search data sources box.
Click the Pipedrive card to open the Create connector screen.
Fill in the connection fields shown (such as your API token), then click Create.
Alta runs a quick connect test. If it can't reach Pipedrive you'll see The connect test has failed with the provider's error — fix the field and retry.
Once it passes, the card shows Connected and Data is syncing until the first sync finishes.

Choose which tables sync

Open the connection. Pipedrive brings in standard objects like deals, persons, organizations, and activities.
Use the Synced toggle in the Pipedrive tables section to control what's pulled in.
Turn off Show only synced tables to see everything available, including custom fields.

Key tables and fields synced

deals — the core pipeline record: id, title, value, currency, stage_id, status (open/won/lost), pipeline_id, add_time, won_time, owner_id
persons — contacts: id, name, email, phone, org_id
organizations — companies: id, name, owner_id
activities — tasks and meetings: id, type, done, due_date, deal_id, person_id
stages / pipelines — stage and pipeline definitions used to order your funnel
users — owner lookup: id, name, email

What you can ask this data

Once it's syncing, build it into metrics and dashboards or just ask Luna / Ask AI. For example:

"What's the value of open deals by stage?" — sums deals.value where status = open, grouped by stage_id.
"How many deals were won this month, and by whom?" — counts deals by won_time and owner_id.
"What's the average time to close a deal?" — measures add_time to won_time.
"What's our win rate by pipeline?" — compares won vs lost status grouped by pipeline_id.
"Which activities are overdue?" — filters activities where done = false and due_date is past.

Example use cases

Pipeline health dashboard. Open value by stage, deals at risk (no recent activity), and weighted forecast.
Sales velocity. Combine add_time/won_time with stage data to see how fast deals move and where they stall.
Rep leaderboard. Won value and win rate by owner_id over any period.
Train Alta on winners. With won deals tied to organizations, Alta learns which accounts close to sharpen targeting.

Keep it in sync

Sync status shows Last sync (Succeeded/Failed) and the Sync frequency.
Click Sync now to refresh immediately (Sync triggered successfully); it's disabled while a sync runs.
Use the overflow menu (⋯) to Disable, Enable, or Delete.

Tips and common pitfalls

A failed connect test is almost always the token. Re-copy the API token and make sure it hasn't been regenerated in Pipedrive.
Token visibility matters. The token only sees what its user can — if deals are missing, the user lacks visibility into them.
Filter by pipeline when you run more than one, so stages don't get mixed.
Deleting is permanent. Disable instead to pause without losing data.