---
title: "Pipedrive API: connect it to a tool built with AI (2026)"
url: https://while.sh/en/guides/connect-pipedrive-api-ai-tool/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-18
---

# Connect Pipedrive to a tool built with Claude or ChatGPT (2026)

Your sales team lives in Pipedrive, and your tool built with Claude needs to read deals or add contacts. The Pipedrive token acts on your behalf across the whole CRM, and it must end up neither in the code nor in the conversation. On while, it stays in while, and your AI never sees it. Here is how.

Many sales teams live in **Pipedrive**: open deals, pipeline stages, follow-ups. A tool built with Claude or ChatGPT takes over when you need **something other than a CRM**: a quote calculator that creates the deal, a commission table, a trade show form that adds contacts. To do that, it needs the **Pipedrive API token**, and that token acts **on your behalf across the whole CRM**.

That is where things often go wrong: **the token ends up pasted into the code**, or into the conversation with the AI, where it can leak. On while, the Pipedrive token **stays in while**. The tool calls Pipedrive without ever holding it, and your AI never sees it.

> **The short version.** Copy the API token from your Pipedrive personal preferences. Ask your AI to connect Pipedrive, then paste the token into while through the link it gives you. The tool reads your deals, every call is logged, and a write waits for the rule you approve.

## What to know about the Pipedrive token

The Pipedrive token is easy to find, and it has a few specifics to know before giving it to a tool (sources 1, 2 and 3).

| What to know | What it changes |
|---|---|
| It acts on behalf of one person | Every action of the tool is tied to that account, with its permissions |
| One active token per person and per company | Regenerating it cuts off every tool that uses it |
| API access depends on permissions | The admin can turn it on or off |
| It goes in the x-api-token header | while adds it there on each call |

For a team tool, use the token of an **account whose permissions suit the tool**, not necessarily the owner's.

## Connect Pipedrive to your tool, in three steps

The whole thing takes a few minutes, and you have no code to write.

1. **Copy the token in Pipedrive.** Open your account menu at the top right, then **Company settings**, **Personal preferences** and **API**. If the API tab is missing, ask the admin to turn it on for you (sources 1 and 2).
2. **Ask your AI to connect Pipedrive.** It declares the connection in while and gives you a link.
3. **Paste the token into while.** You open the link, paste the token and confirm. Neither your AI nor the tool's code sees it.

> You, to your AI: Connect Pipedrive to this tool, and build a table of the deals won this month by salesperson, with the amount and each person's commission.

<figure class="illus"><img src="/illustrations/pipedrive-relais-1200.webp" srcset="/illustrations/pipedrive-relais-768.webp 768w, /illustrations/pipedrive-relais-1200.webp 1200w" sizes="(min-width: 48rem) 46rem, 100vw" width="1536" height="1024" loading="lazy" decoding="async" alt="The tool built with AI calls the Pipedrive API through while: the API token is added to each call inside while, out of the code, every read of the pipeline's deals is logged and a CRM change waits for the rule a person approves" /><figcaption>The tool calls Pipedrive through while, which adds the token to each call.</figcaption></figure>

## What while does on each call

The tool calls Pipedrive **through while**, without a token. while adds the token to each call, and logs it in the history. For the first seven days, reads go through and teach while what the tool calls. **A write**, like creating a deal or editing a contact, goes through once you approve its rule. After that, an unexpected call is refused, and your AI is told.

You can also ask for your approval before a sensitive call.

> You, to your AI: Ask me before every deal deletion in Pipedrive.

Pipedrive gives each company a **daily call budget**, shared by everyone on the account. Each call uses part of it depending on its complexity, and the budget resets every day (source 4). Your AI takes it into account when it builds the tool.

The credentials of your software are detailed on our [security](/en/security/) page, and the same mechanism works for any API in [connect an API with no credentials in the code](/en/guides/api-keys-out-of-code/).

## Changing the token

Since there is only one active token at a time, generating a new one **cuts off everything that used the old one** (source 1). With while, there is only one place to update: **paste the new token into while**, and the tool uses it from the next call, without being put back in place.

## What while adds around it

- **Your colleagues** use the tool with a while account for up to 3 people, or, on the Pro plan, with their email account, Google or Microsoft. See [keep a tool for your colleagues](/en/guides/internal-tool-company-sign-in/).
- **Connected software**: one on the Libre plan, and 25 on the Pro plan, Pipedrive included.
- **The tool's data** is backed up every day, and your tools are hosted in France by Nextmap.

To go further, see [the quote tracker](/en/guides/quote-tracker-small-business-ai-2026/), [connect HubSpot](/en/guides/connect-hubspot-ai-tool/) and [build a simple CRM](/en/guides/simple-crm-small-business-claude-chatgpt-2026/).

## Try it with your tool

Give this message to your AI, then ask it to connect Pipedrive. The trial is **free, with no sign-up**, and your tool has its address **in 3 minutes**.

```text titre="The message to give your AI"
Read while.sh/agents and help me get started with while.
```

## Sources

1. [Pipedrive, How to find the API token](https://pipedrive.readme.io/docs/how-to-find-the-api-token), 2026-11-18
2. [Pipedrive, Enabling API for company users](https://pipedrive.readme.io/docs/enabling-api-for-company-users), 2026-11-18
3. [Pipedrive, Authentication](https://pipedrive.readme.io/docs/core-api-concepts-authentication), 2026-11-18
4. [Pipedrive, Rate limiting](https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting), 2026-11-18

## Questions

### Where do you find the Pipedrive API token?

In Pipedrive, open your account menu at the top right, then Company settings, Personal preferences and API. Each person has one token per company, and only one active token at a time (source 1).

### Why can't I see the API tab in Pipedrive?

It is a company permission setting. The Pipedrive admin can turn on API access for you in the permission sets (source 2).

### Does my AI see the Pipedrive token?

No. Your AI declares the connection to Pipedrive and gives you a link. You paste the token into while there, and neither your AI nor the tool's code sees it.

### On whose behalf does the tool act in Pipedrive?

On behalf of the person who owns the token: Pipedrive ties every action to that account. For a team tool, use the token of an account whose permissions suit the tool (source 1).

### How many calls does the Pipedrive API accept?

Each company has a daily call budget, shared by everyone on the account. Each call uses part of it depending on its complexity, and the budget resets every day (source 4).
