Pipedrive integration
What Management OS does with your Pipedrive data.
Operator-grade transparency. Every OAuth scope we request maps to a specific Management OS feature you can see and measure. Nothing pulled, nothing stored, nothing inferred beyond what this page documents.
1. What we read
Management OS reads CRM data from your Pipedrive company — specifically: Deals, Persons, Organizations, Users, and Activities. We do not access Pipedrive Projects, Campaigns, Files, Documents, Insights dashboards, or any Pipedrive data not explicitly listed in the scope table below.
Per-company: Pipedrive returns an api_domain at token exchange (e.g. https://acme.pipedrive.com). All REST calls target only that company's domain — we never read across companies.
Why: Management OS is the leadership execution layer above the revenue stack. We synthesize CRM data into a Weekly Intelligence Brief that develops the leader, their team, and their business. We can't synthesize what we can't read.
2. What we write
We do not write to your Pipedrive CRM. Management OS is a read-only consumer of your Pipedrive data. We do not create, modify, or delete any Pipedrive records — no Deals, no Persons, no Organizations, no Activities, no Notes, no fields, no automations.
All Management OS outputs (Account Plans, Coaching Briefs, Forecast Locks, Meeting Prep dossiers, Pitch Decks) are generated and stored in Management OS's own database and surfaced through the Management OS application — not pushed back into your Pipedrive company.
3. The OAuth scopes we request — and why each one
Every scope below maps to a specific feature. We requested the minimum scope set needed to deliver the Management OS feature surface; we did not request scopes that we don't currently use.
Required scopes (5)
These scopes are requested on every connection. Without them, the core Management OS feature surface does not function.
base
Standard Pipedrive OAuth grant — identifies which Pipedrive company is connecting and resolves the per-company API domain (e.g. https://acme.pipedrive.com) that all REST calls target. No data access on its own.
deals:read
Read deal records so the Opportunity Scorer can grade pipeline against the 15-dimension / 75-criterion rubric (MEDDPICC + SPICED + Blue Sheet consolidated), surface deal-slip patterns, and lock the quarterly forecast. Deals drive the Business pillar of the Weekly Intelligence Brief.
contacts:read
Read Persons and Organizations (contacts and accounts) so Management OS can build the Account Plan, map stakeholder coverage on deals, identify champion-leaving signals, and surface multi-thread risk in the Brief.
users:read
Map Pipedrive users to Management OS workspace members so coaching alerts and rep-effectiveness rankings are addressed to the correct person.
activities:read
Read Activities (calls, meetings, tasks, emails logged as activities) so the Brief surfaces buyer-intent signals at the deal and contact level, and Meeting Prep dossiers anchor on real upcoming activities rather than calendar-only signals.
Optional scopes (3)
These scopes are requested only when the customer's Pipedrive plan has the corresponding feature enabled. If the customer's plan does not include a feature, the corresponding optional scope is skipped without blocking the install.
mail:read
Read sales-mail engagement metadata (sent / opened / replied) so the Brief surfaces buyer-intent signals from email activity tracked inside Pipedrive. Email body content is read only when the user has chosen to sync the email into Pipedrive itself.
products:read
Read product catalogs so deal line items are surfaced in the Account Plan and the deal scorer (multi-product expansion signals).
leads:read
Read Lead records (Pipedrive's pre-qualified pipeline) for top-of-funnel coverage in the Weekly Brief, where leads are tracked separately from deals.
4. Where your Pipedrive data lives
Application database: Supabase Postgres (Management OS's production database, US East). Encrypted at rest (AES-256), encrypted in transit (TLS 1.3). Workspace-scoped row-level security (RLS) means one customer's data is never visible to another.
OAuth tokens: Stored in the same Supabase database under workspace-scoped RLS. Access tokens, refresh tokens, and the per-company api_domain are encrypted at rest and never returned to client browsers. Only the Management OS server-side runtime has access via service-role credentials.
Inference layer: Anthropic API (Claude models). CRM data required for a specific brief generation is passed to Anthropic; outputs are returned to Management OS and stored in our database. Anthropic does not train on customer data per their API terms.
Retention: We retain Pipedrive-sourced data while your subscription is active. On disconnect we delete OAuth tokens immediately. On subscription cancellation, customer data is retained for 30 days for restoration, then permanently deleted. Data subject deletion requests are honored within 30 days per our Privacy Policy.
5. How to install Management OS for Pipedrive
- Sign up at mgmt-os.ai and complete onboarding to your workspace
- Open Management OS → Settings → Integrations
- Find Pipedrive in the integration directory and click Connect Pipedrive
- You'll be redirected to Pipedrive's authorization screen. Sign in with the Pipedrive account you want Management OS to read from
- Review the requested scopes and click Allow and install
- You'll return to Management OS with a confirmation that the integration is connected. The initial CRM sync starts immediately and typically completes within 2-5 minutes
If you administer Pipedrive on behalf of an organization: Pipedrive requires an admin to install third-party apps for company-wide access. If you encounter a permission prompt, your Pipedrive admin can install Management OS from the Marketplace on behalf of the company.
6. How to use Management OS once connected
The Weekly Intelligence Brief is the primary surface. Three pillars synthesize your Pipedrive data:
- Develop Your Business — deal scoring (every open Deal scored against the Opportunity OS rubric), forecast accuracy, account plans, champion-behavior alerts, renewal cascade
- Develop Your Team — coaching priorities mapped to specific reps and deals, rep-effectiveness rankings, 1:1 prep, GROW conversation planners
- Develop Yourself — leader focus, calendar audit, ninety-day competency focus, decision deadlines you're sitting on
Ask Anything (AMA) — a conversational surface where you can query your Pipedrive data in plain English. Examples: "Which deals slipped from this month to next?", "Show me the top 5 deals at risk with no activity in 14 days", "What's my coverage ratio against Q4 quota by rep?"
7. How to disconnect from Management OS
- Open Management OS → Settings → Integrations
- Find Pipedrive in the connected integrations list
- Click Disconnect → confirm
On disconnect we immediately delete the stored OAuth tokens (access, refresh, and api_domain) and stop reading any new CRM data. Previously synthesized briefs remain in your Management OS workspace as historical records — they are not deleted automatically because they may contain decisions and context the leader still references.
To remove all historical briefs and data after disconnect, email privacy@mgmt-os.ai with your workspace identifier. We process deletion requests within 30 days.
8. How to revoke from Pipedrive's side
- Sign in to Pipedrive as the user who authorized the connection
- Click your avatar → Personal preferences → Marketplace apps
- Find Management OS in the installed apps list
- Click Uninstall
Revoking from Pipedrive's side invalidates our access and refresh tokens immediately. Our next API call returns 401 and we surface a re-connection prompt in Management OS Settings.
9. Security disclosures + contact
Security incident reporting: security@mgmt-os.ai
Privacy / data subject requests: privacy@mgmt-os.ai
Integration support: support@mgmt-os.ai
For general questions about Management OS, see our Support page or Manifesto.
Last updated: 2026-11-01. We update this page within 7 days of any change to scopes, data flows, or retention.