Reference · built on requestConnectorCRM & sales

Pipedrive

Deals, leads, persons, organizations, and activities from a Pipedrive company account, with webhooks on change.

Request accessPricing ↗

About

Pipedrive is a pipeline-first CRM used by small and mid-sized sales teams. A company account holds deals moving through stages, the persons and organizations attached to them, leads waiting in the Leads Inbox, and the activities scheduled against each deal. Its v2 endpoints cover deals, activities, and search, while some resources remain on v1.

Fibric reads those records and the webhooks Pipedrive sends on create, change, and delete. An operator proposes the next activity, a stage move, or a lead conversion, and a person confirms it before anything is written.

This is a reference listing. It documents what Fibric would read from Pipedrive and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Deals through GET /api/v2/deals and /api/v2/deals/{id}, with field history at GET /api/v1/deals/{id}/changelog
  • Leads in the Leads Inbox through GET /api/v1/leads, with title, person_id, organization_id, value, and expected_close_date
  • Activities through GET /api/v2/activities, with type, due_date, done, and links to deal_id, person_id, org_id, or lead_id
  • Persons, organizations, pipelines, stages, notes, and products through their own endpoints
  • Webhooks with event_action create, change, or delete on deal, person, organization, activity, lead, note, product, pipeline, stage, and user
  • Deal search through GET /api/v2/deals/search by title, notes, or custom fields

Proposed actions

  • Target capability: propose a stage or value change through PATCH /api/v2/deals/{id}
  • Target capability: propose a new activity through POST /api/v2/activities with a due date and an owner
  • Target capability: propose converting a lead into a deal through POST /api/v2/leads/{id}/convert/deal
  • Target capability: propose merging two deals through PUT /api/v1/deals/{id}/merge after a person compares them

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Nudge a deal that has stalled in a stage

    Deals with no completed activity since a date you set are listed with their stage and owner. The operator drafts the next activity, and a person schedules it.

    With Stale Pipeline

  • Turn a lead into a deal at the right moment

    New leads in the Leads Inbox are read with their person and organization. The operator proposes a first activity and, once it is answered, the conversion to a deal.

    With Lead Response

  • Record why a deal was won or lost

    When a deal closes, the operator reads the changelog and activities and drafts a short record of what happened. The owner edits and approves it.

    With Win-Loss Record

  • Chase a proposal before it expires

    Deals in a proposal stage with an expected close date inside your window are surfaced with the last note. The operator drafts the follow-up for the owner to send.

    With Quote Follow-up

Requirements

  • A Pipedrive company account and a user whose API token the connector acts under
  • Enough daily token budget for the read volume: 30,000 base tokens times the plan multiplier times seats
  • A webhook target URL if you want create, change, and delete events rather than polling
  • A separate sandbox account for testing, as Pipedrive recommends
Authentication
A per-user API token sent in the x-api-token header for one company, or OAuth 2.0 for a Marketplace app; only one API token is active per user at a time.

Limits

  • Daily budget is metered in tokens: a single read costs 2, a list 20, a search 40; the budget resets at server midnight
  • Burst limits per API token: 20, 40, 100, or 120 requests per 2 seconds by plan; OAuth apps get four times that
  • Search endpoints are limited to 10 requests per 2 seconds on every plan
  • Replacing a user's API token breaks any integration still using the old one

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Pipedrive ↗

Questions and answers

Does Pipedrive send webhooks?
Yes. A webhook subscribes to an event_action of create, change, delete, or * on an event_object such as deal, person, organization, activity, or lead. Webhook version 2.0 is the default since March 17, 2025.
How is API usage metered?
In tokens. Each company gets 30,000 base tokens per day multiplied by the plan multiplier (Lite 1, Growth 2, Premium 5, Ultimate 7) and by seats, plus any purchased top-ups. A single read costs 2 tokens, a list 20, a search 40.
Can the connector use OAuth instead of a user's API token?
Yes. OAuth 2.0 is the model for Marketplace apps and carries burst limits four times those of an API token. A per-user API token in the x-api-token header is the simpler path for one company.
Ask about Pipedrive

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Pipedrive through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy