Pipedrive
Work Pipedrive deals, persons, organizations, leads and activities from agent tasks.
Connect it with: Sign in (OAuth), API key. Pipedrive's own documentation: https://pipedrive.readme.io/docs/marketplace-oauth-authorization.
What agents can do
Connect Pipedrive so the agents working your tasks can reach it. With it connected, they can:
- Create, move and update deals across pipeline stages.
- Add and update persons and organizations, and link them to deals.
- Schedule and complete activities such as calls, meetings and follow-up tasks.
- Search across deals, persons, organizations and leads by name, email or phone.
Before you start
- A Pipedrive user (any plan); to approve the sign-in for the whole company you must be a Pipedrive admin.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Pipedrive
This is the quickest way in: you sign in to Pipedrive and approve what Jaah asks for. You never copy a key.
- In Jaah, open Secrets and select New.
- Search for Pipedrive and select its card.
- Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
- Select Connect Pipedrive. Pipedrive's sign-in window opens.
- Sign in to Pipedrive if asked, check the access listed, and approve it.
- You land back in Jaah on the new secret, which reads Connected once its test passes.
If the button reads Jaah app not configured, this Jaah has no app registered at Pipedrive yet. Use an API key, or your own OAuth app, until it does.
Scopes Jaah requests
Jaah asks Pipedrive for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.
Jaah names no scopes on the sign-in request: the vendor grants the access set on Jaah's app itself, and lists it on its approval screen.
Connect with an API key
Prefer this when you cannot sign in with Pipedrive — for example a service account, or a token your admin issued. On the Connect screen select Use an API key instead.
Find each value first:
- API token: In Pipedrive, open the account menu at the top right, select Personal preferences, then the API tab, and copy Your personal API token (an admin can turn this tab off under Company settings > Permission sets).
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Pipedrive card.
- Name the secret and choose who can use it.
- Select Use an API key instead.
- Fill in API token.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Register your own OAuth app at Pipedrive when your company requires apps it controls, or before this Jaah has an app registered there.
- Create an OAuth app in Pipedrive's developer console, https://developers.pipedrive.com/ (Pipedrive's documentation).
- Set its redirect URI to
https://app.jaah.ai/api/credentials/connect/callback(on your own Jaah, its console address followed by/api/credentials/connect/callback). - Give it the scopes in Scopes Jaah requests.
- Copy its client ID and client secret.
- In Jaah, start a new Pipedrive secret, select Use your own OAuth app, paste both values and select Connect Pipedrive.
The client secret is stored with the connection, encrypted, like any other secret value.
Test the connection
Select Test on the secret. Jaah calls Pipedrive's API once (GET https://api.pipedrive.com/v1/users/me) with the stored values, and shows who it answered as, or which value Pipedrive refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
A key connection hands the agent its fields: api_token.
Tell the agent in your task description which secret to use, for example “use the Pipedrive secret org/pipedrive”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Pipedrive once the test passes. Steps: Replace or delete a secret.
- Reconnect: when Pipedrive ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Pipedrive's side too, revoke Jaah in Pipedrive's settings, or revoke or delete the key at Pipedrive.
Limitations
- Agents act as the user who connected and see only the deals and contacts that user's visibility groups allow.
- With sign-in, what agents can do is fixed by the scopes on Jaah's Pipedrive app (deals, activities, contacts, leads, search and users read); Pipedrive shows the list on its install screen.
- Pipedrive rate-limits each company per token on a rolling 2-second window and, on newer plans, with daily token budgets.
- An agent learns the company's own API address from users/me (
data.company_domain); requests to api.pipedrive.com also work. - Agents can do only what the connected Pipedrive account and its granted scopes allow.
Troubleshooting
Test says Pipedrive rejected the API token (401)
The personal token was regenerated or the user was deactivated. Copy the current token from Personal preferences > API and select Replace on the secret.
The API tab is missing from Personal preferences
Your company turned off API access for your permission set. A Pipedrive admin enables Use API under Company settings > Permission sets, or you connect with Sign in instead.
The secret shows Needs reconnect
The app was uninstalled in Pipedrive (Tools and apps > Marketplace apps) or the refresh token expired after 60 days unused. Select Reconnect and approve again.
Still stuck? Select Test and read the result: it names the value Pipedrive refused and the status it answered.
FAQ
Sign in or API token - which should I use?
Sign in when you can: Jaah renews the access itself and you can uninstall it in Pipedrive at any time. Use the API token for automation accounts or when your admin has not approved the app.
Can I limit which data agents reach?
Connect as a user whose visibility groups limit what they can see; Pipedrive applies those to every API call.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Pipedrive account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.