Pipedrive

Connect Pipedrive to collect crm evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Pipedrive:

   1. Sign in to Pipedrive as the user Safeguard should act as.
   2. Click your account name (top right) › Company settings › Personal preferences › API.
   3. Copy your personal API token and paste it into API token. If the API option is not visible, API access must first be enabled for company users.

   Where to find the other values:

   • API URL (optional): Your company's Pipedrive address (https://<companydomain>.pipedrive.com); the fetched doc does not show where the UI displays it.
   • Access token (optional): Only for OAuth apps; leave empty when using the personal API token.

   Each user has a distinct API token per company and only one active token at a time. The personal token carries the user's rights. The fetched page does not say whether the token can be viewed again.

   Source: pipedrive.readme.io, checked 2026-10-07.

   The permissions Safeguard needs: users:read.

2. On Compliance › Connectors, open Pipedrive, click Connect, choose API token and fill in:

   Field	What to enter
   API token	Optional. Stored encrypted and never shown again.

   Or, instead: Access token (optional), API URL (optional).

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Pipedrive and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• CRM connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks