CRM and sales
Pipedrive for AI agents.
Managed auth, ready-made tools.
Find and update deals, add people and log activities and notes in Pipedrive on behalf of each of your users.
About Pipedrive
With the Pipedrive connector, your agent works in each user’s own Pipedrive account. It can search deals and people, create or move a deal, add a person, schedule an activity and add a note, using only the tools your project allows.
Pipedrive is a sales CRM built around a visual deal pipeline.
Tools
What your agent can do in Pipedrive.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Pipedrive connection.
-
Search deals
Readpipedrive_search_dealsFind deals by title or other fields.
-
Get a deal
Readpipedrive_get_dealGet a deal's value, stage, owner and contacts.
-
Create a deal
Writepipedrive_create_dealAdd a deal with a title, value and stage.
-
Update a deal
Writepipedrive_update_dealChange a deal's stage, value, status or owner.
-
Search people
Readpipedrive_search_personsFind people by name, email or phone.
-
Add a person
Writepipedrive_create_personAdd a person with their contact details.
-
Schedule an activity
Writepipedrive_create_activityAdd a call, meeting or task linked to a deal or person.
-
Add a note
Writepipedrive_create_noteAdd a note to a deal, person or organization.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Pipedrive, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read deals and add notes, and switch off
pipedrive_update_dealso it can never move or close a deal. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example deals and activities but not contacts. A call outside them is refused.
Get started
Connect Pipedrive
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Pipedrive
Each end user authorizes their own Pipedrive account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Pipedrive account, once. const connection = await agent200 .user("user_123") .connect("pipedrive"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Pipedrive tools
Name the user, the model and the tools. The model decides which Pipedrive tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Move the Globex deal to negotiation", tools: ["pipedrive"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Pipedrive's own sign-in page. You never see or store their Pipedrive password.
-
What access is requested
The scopes the connection needs, such as reading deals, writing deals, reading contacts or managing activities, listed on Pipedrive's authorization screen. Users can remove the app later from their Pipedrive account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Pipedrive connector and how to use it.
Connector: Pipedrive, through Agent200. In code: "pipedrive". What it does: Find and update deals, add people and log activities and notes in Pipedrive on behalf of each of your users. Page: https://www.agent200.com/connectors/pipedrive/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Pipedrive's own page, through the authorization link Agent200 returns. Never ask a user for a Pipedrive password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: pipedrive_search_deals, pipedrive_get_deal, pipedrive_search_persons. Write tools: pipedrive_create_deal, pipedrive_update_deal, pipedrive_create_person, pipedrive_create_activity, pipedrive_create_note. Name "pipedrive" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/pipedrive/framework/claude/ https://www.agent200.com/connectors/pipedrive/framework/chatgpt/ https://www.agent200.com/connectors/pipedrive/framework/claude-code/ https://www.agent200.com/connectors/pipedrive/framework/muse/ https://www.agent200.com/connectors/pipedrive/framework/grok-bot/ https://www.agent200.com/connectors/pipedrive/framework/openai-dots/ https://www.agent200.com/connectors/pipedrive/framework/claude-duet/ https://www.agent200.com/connectors/pipedrive/framework/hermes-agent/ https://www.agent200.com/connectors/pipedrive/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/pipedrive.md
Guides
Use Pipedrive with the AI you build on.
Step-by-step setup for Pipedrive with a specific model, assistant or agent framework.
-
Pipedrive + Claude
How to connect Pipedrive to Claude
-
Pipedrive + ChatGPT
How to connect Pipedrive to ChatGPT
-
Pipedrive + Claude Code
How to connect Pipedrive to Claude Code
-
Pipedrive + Muse
How to connect Pipedrive to Muse
-
Pipedrive + Grok Bot
How to connect Pipedrive to Grok Bot
-
Pipedrive + OpenAI Dots
How to connect Pipedrive to OpenAI Dots
-
Pipedrive + Claude Duet
How to connect Pipedrive to Claude Duet
-
Pipedrive + Hermes Agent
How to connect Pipedrive to Hermes Agent
-
Pipedrive + OpenClaw
How to connect Pipedrive to OpenClaw
FAQ
Pipedrive and Agent200, answered.
Who handles the Pipedrive OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Pipedrive.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Pipedrive connection, never another user's. It cannot reach anything the user or Pipedrive has not authorized.
Can I limit what my agent can do in Pipedrive?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.