Connect Pipedrive to Rig

    Sync your Pipedrive persons, deals, organisations, activities and notes into Rig, so pipeline questions run on live CRM data. Pipedrive connects with your personal API token and company subdomain.

    Before you start

    • You need a Pipedrive user whose view of the data matches what you want synced. The token reads what that user can see.
    • Know your company subdomain, the part before .pipedrive.com in the address you sign in at.

    Step 1: Find your Pipedrive API token

    1. Sign in to Pipedrive.
    2. Go to Settings, then Personal preferences, then API.
    3. Copy your personal API token.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Pipedrive, open the card and click Connect.
    3. Pipedrive API token: paste your personal API token.
    4. Company subdomain: enter the part before .pipedrive.com, for example acme. Pasting the full URL also works.
    5. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    6. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Pipedrive lands in its own pipedrive schema in your warehouse:

    • Persons and organizations: the people and companies in your CRM.
    • Deals: deals with their pipeline and stage.
    • Activities and notes: calls, meetings, tasks and notes logged against your records.
    • Pipelines, stages and users: the structure around your deals and your Pipedrive team.

    Good to know

    • The token belongs to one user and takes that user's permissions. Use an admin's token if records owned by other people are missing.
    • The token is tied to its user. If you switch to another user's token later, update the source in Rig.
    • Pipedrive keeps the token on a personal page, so it can be copied again at any time. Treat it like a password.
    • To disconnect Pipedrive, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Measure pipeline conversion and cycle length
    • Connect activities to outcomes
    • Track forecast and deal hygiene

    More ideas for using Pipedrive

    Was this guide helpful?