Pipedrive credentials
You can use these credentials to authenticate the following nodes:
Supported authentication methods
API token
OAuth2
Using API token
To configure this credential, you’ll need a Pipedrive account and:
An API Token
To get your API token:
Open your API Personal Preferences.
Copy Your personal API token and enter it in your n8n credential.
If you have multiple companies, you’ll need to select the correct company first:
Select your account name and be sure you’re viewing the correct company.
Then select Company Settings.
Select Personal Preferences.
Select the API tab.
Copy Your personal API token and enter it in your n8n 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:
Select your profile name in the upper right corner.
Find the company name of your sandbox account and select Developer Hub.
/// note | No Developer Hub If you don’t see Developer Hub in your account dropdown, sign up for a developer sandbox account. ///
Select Create an app.
Select Create public app. The app’s Basic info tab opens.
Enter an App name for your app, like
n8n integration.Copy the OAuth Redirect URL from n8n and add it as the app’s Callback URL.
Select Save. The app’s OAuth & access scopes tab opens.
Turn on appropriate Scopes for your app. Refer to Pipedrive node scopes and Pipedrive Trigger node scopes below for more guidance.
Copy the Client ID and enter it in your n8n credential.
Copy the Client Secret and enter it in your n8n 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 in n8n and what actions you want to complete with those.
Scopes you may need for the Pipedrive node:
Object |
Node action |
UI scope |
Actual scope |
|---|---|---|---|
Activity |
Get data of an activity |
Activities: Read only or |
|
Activity |
Create |
Activities: Full Access |
|
Deal |
Get data of a deal |
Deals: Read only or |
|
Deal |
Create |
Deals: Full Access |
|
Deal Activity |
Get all activities of a deal |
Activities: Read only or |
|
Deal Product |
Get all products in a deal |
Products: Read Only or |
|
File |
Download |
Refer to note below |
Refer to note below |
File |
Create |
Refer to note below |
Refer to note below |
Lead |
Get data of a lead |
Leads: Read only or |
|
Lead |
Create |
Leads: Full access |
|
Note |
Get data of a note |
Refer to note below |
Refer to note below |
Note |
Create |
Refer to note below |
Refer to note below |
Organization |
Get data of an organization |
Contacts: Read Only or |
|
Organization |
Create |
Contacts: Full Access |
|
Person |
Get data of a person |
Contacts: Read Only or |
|
Person |
Create |
Contacts: Full Access |
|
Product |
Get data of all products |
Products: Read Only |
|
Note
Files and Notes 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.