> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/integrations/builtin/credentials/pipedrive.md).

# Pipedrive credentials

You can use these credentials to authenticate the following nodes:

* [Pipedrive](/integrations/builtin/app-nodes/n8n-nodes-base.pipedrive.md)
* [Pipedrive Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.pipedrivetrigger.md)

## Supported authentication methods <a href="#supported-authentication-methods" id="supported-authentication-methods"></a>

* API token
* OAuth2

## Related resources <a href="#related-resources" id="related-resources"></a>

Refer to [Pipedrive's developer documentation](https://pipedrive.readme.io/docs/getting-started) for more information about the service.

## Using API token <a href="#using-api-token" id="using-api-token"></a>

To configure this credential, you'll need a [Pipedrive](https://pipedrive.com/) account and:

* An **API Token**

To get your API token:

1. Open your [**API Personal Preferences**](https://app.pipedrive.com/settings/api).
2. 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:

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 n8n credential.

Refer to [How to find the API token](https://pipedrive.readme.io/docs/how-to-find-the-api-token) for more information.

## Using OAuth2 <a href="#using-oauth2" id="using-oauth2"></a>

To configure this credential, you'll need a [Pipedrive developer sandbox account](https://developers.pipedrive.com/) 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**.<br>

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>No Developer Hub</strong></p><p>If you don't see <strong>Developer Hub</strong> in your account dropdown, sign up for a <a href="https://developers.pipedrive.com/">developer sandbox account</a>.</p></div>
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, like `n8n integration`.
6. Copy the **OAuth Redirect URL** from n8n and 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](#pipedrive-node-scopes) and [Pipedrive Trigger node scopes](#pipedrive-trigger-node-scopes) below for more guidance.
9. Copy the **Client ID** and enter it in your n8n credential.
10. Copy the **Client Secret** and enter it in your n8n credential.

Refer to [Registering a public app](https://pipedrive.readme.io/docs/marketplace-registering-the-app) for more information.

### Pipedrive node scopes <a href="#pipedrive-node-scopes" id="pipedrive-node-scopes"></a>

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](/integrations/builtin/app-nodes/n8n-nodes-base.pipedrive.md) node:

| **Object**    | **Node action**                                                               | **UI scope**                                                                                 | **Actual scope**                                                       |
| ------------- | ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Activity      | <p>Get data of an activity<br>Get data of all activities</p>                  | <p><strong>Activities: Read only</strong> or<br><strong>Activities: Full Access</strong></p> | <p><code>activities:read</code> or<br><code>activities:full</code></p> |
| Activity      | <p>Create<br>Delete<br>Update</p>                                             | **Activities: Full Access**                                                                  | `activities:full`                                                      |
| Deal          | <p>Get data of a deal<br>Get data of all deals<br>Search a deal</p>           | <p><strong>Deals: Read only</strong> or<br><strong>Deals: Full Access</strong></p>           | <p><code>deals:read</code> or<br><code>deals:full</code></p>           |
| Deal          | <p>Create<br>Delete<br>Duplicate<br>Update</p>                                | **Deals: Full Access**                                                                       | `deals:full`                                                           |
| Deal Activity | Get all activities of a deal                                                  | <p><strong>Activities: Read only</strong> or<br><strong>Activities: Full Access</strong></p> | <p><code>activities:read</code> or<br><code>activities:full</code></p> |
| Deal Product  | Get all products in a deal                                                    | <p><strong>Products: Read Only</strong> or<br><strong>Products: Full Access</strong></p>     | <p><code>products:read</code> or<br><code>products:full</code></p>     |
| File          | <p>Download<br>Get data of a file</p>                                         | Refer to note below                                                                          | Refer to note below                                                    |
| File          | <p>Create<br>Delete</p>                                                       | Refer to note below                                                                          | Refer to note below                                                    |
| Lead          | <p>Get data of a lead<br>Get data of all leads</p>                            | <p><strong>Leads: Read only</strong> or<br><strong>Leads: Full access</strong></p>           | <p><code>leads:read</code> or<br><code>leads:full</code></p>           |
| Lead          | <p>Create<br>Delete<br>Update</p>                                             | **Leads: Full access**                                                                       | `leads:full`                                                           |
| Note          | <p>Get data of a note<br>Get data of all notes</p>                            | Refer to note below                                                                          | Refer to note below                                                    |
| Note          | <p>Create<br>Delete<br>Update</p>                                             | Refer to note below                                                                          | Refer to note below                                                    |
| Organization  | <p>Get data of an organization<br>Get data of all organizations<br>Search</p> | <p><strong>Contacts: Read Only</strong> or<br><strong>Contacts: Full Access</strong></p>     | <p><code>contacts:read</code> or<br><code>contacts:full</code></p>     |
| Organization  | <p>Create<br>Delete<br>Update</p>                                             | **Contacts: Full Access**                                                                    | `contacts:full`                                                        |
| Person        | <p>Get data of a person<br>Get data of all persons<br>Search</p>              | <p><strong>Contacts: Read Only</strong> or<br><strong>Contacts: Full Access</strong></p>     | <p><code>contacts:read</code> or<br><code>contacts:full</code></p>     |
| Person        | <p>Create<br>Delete<br>Update</p>                                             | **Contacts: Full Access**                                                                    | `contacts:full`                                                        |
| Product       | Get data of all products                                                      | **Products: Read Only**                                                                      | `products:read`                                                        |

{% hint style="info" %}
**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.
{% endhint %}

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](https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations) for more information.

### Pipedrive Trigger node scopes <a href="#pipedrive-trigger-node-scopes" id="pipedrive-trigger-node-scopes"></a>

The [Pipedrive Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.pipedrivetrigger.md) node requires the **Webhooks: Full access** (`webhooks:full`) scope.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.n8n.io/integrations/builtin/credentials/pipedrive.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.