You can use these credentials to authenticate the following nodes:

  • Pipedrive
  • Pipedrive Trigger

Supported authentication methods

  • API token
  • OAuth2

Refer to Pipedrive’s developer documentation for more information about the service.

Using API token

To configure this credential, you’ll need a Pipedrive account and:

  • An API Token

To get your API token:

  1. Open your API Personal Preferences.
  2. Copy Your personal API token and enter it in your credential.

If you have multiple companies, you’ll need to select the correct company first:

  1. Select your account name and be sure you’re viewing the correct company.
  2. Then select Company Settings.
  3. Select Personal Preferences.
  4. Select the API tab.
  5. Copy Your personal API token and enter it in your credential.

Refer to How to find the API token for more information.

Using OAuth2

To configure this credential, you’ll need a Pipedrive developer sandbox account and:

  • A Client ID
  • A Client Secret

To get both, you’ll need to register a new app:

  1. Select your profile name in the upper right corner.

  2. Find the company name of your sandbox account and select Developer Hub.

    If you don’t see Developer Hub in your account dropdown, sign up for a developer sandbox account.

  3. Select Create an app.

  4. Select Create public app. The app’s Basic info tab opens.

  5. Enter an App name for your app.

  6. Copy the OAuth Redirect URL add it as the app’s Callback URL.

  7. Select Save. The app’s OAuth & access scopes tab opens.

  8. Turn on appropriate Scopes for your app. Refer to Pipedrive node scopes and Pipedrive Trigger node scopes below for more guidance.

  9. Copy the Client ID and enter it in your credential.

  10. Copy the Client Secret and enter it in your credential.

Refer to Registering a public app for more information.

Pipedrive node scopes

The scopes you add to your app depend on which node(s) you want to use it for and what actions you want to complete with those.

Scopes you may need for the Pipedrive node:

ObjectNode actionUI scopeActual scope
ActivityGet data of an activity Get data of all activitiesActivities: Read only or Activities: Full Accessactivities:read or activities:full
ActivityCreate Delete UpdateActivities: Full Accessactivities:full
DealGet data of a deal Get data of all deals Search a dealDeals: Read only or Deals: Full Accessdeals:read or deals:full
DealCreate Delete Duplicate UpdateDeals: Full Accessdeals:full
Deal ActivityGet all activities of a dealActivities: Read only or Activities: Full Accessactivities:read or activities:full
Deal ProductGet all products in a dealProducts: Read Only or Products: Full Accessproducts:read or products:full
FileDownload Get data of a fileRefer to note belowRefer to note below
FileCreate DeleteRefer to note belowRefer to note below
LeadGet data of a lead Get data of all leadsLeads: Read only or Leads: Full accessleads:read or leads:full
LeadCreate Delete UpdateLeads: Full accessleads:full
NoteGet data of a note Get data of all notesRefer to note belowRefer to note below
NoteCreate Delete UpdateRefer to note belowRefer to note below
OrganizationGet data of an organization Get data of all organizations SearchContacts: Read Only or Contacts: Full Accesscontacts:read or contacts:full
OrganizationCreate Delete UpdateContacts: Full Accesscontacts:full
PersonGet data of a person Get data of all persons SearchContacts: Read Only or Contacts: Full Accesscontacts:read or contacts:full
PersonCreate Delete UpdateContacts: Full Accesscontacts:full
ProductGet data of all productsProducts: Read Onlyproducts:read

The scopes for Files and Notes depend on which object they relate to:

  • Files relate to Deals, Activities, or Contacts.
  • Notes relate to Deals or Contacts.

Refer to those objects’ scopes.

The Pipedrive node also supports Custom API calls. Add relevant scopes for whatever custom API calls you intend to make.

Refer to Scopes and permissions explanations for more information.

Pipedrive Trigger node scopes

The Pipedrive Trigger node requires the Webhooks: Full access (webhooks:full) scope.