How to Connect Pipedrive to an AI Agent
Auth setup
1. Settings > Personal preferences > API > copy API token. 2. Append ?api_token={token} to all requests. 3. For OAuth: register app in Marketplace, implement auth code flow.
Key facts
| Base URL | https://api.pipedrive.com/v1/ |
| API version | v1 |
| Auth | API token or OAuth 2.0. API token from Settings > Personal preferences > API. Pass as api_token query parameter or OAuth Bearer. |
| Token URL | https://oauth.pipedrive.com/oauth/token |
| Scopes | deals:read, deals:write, persons:read, persons:write, activities:read, activities:write, etc. |
| Request body | application/json |
| Pagination | Cursor-based: additional_data.pagination.next_start in response. Pass as start param. limit for page size. |
| Rate limit | 80 req/2sec (Essential), 160/2sec (Advanced), 240/2sec (Professional). X-RateLimit-* headers. |
| Error format | JSON: {"success":false,"error":"...","error_info":"...","data":null} |
Key endpoints
| Method | Path | Description |
GET | /deals | List deals with filters |
POST | /deals | Create a deal |
GET | /persons | List contacts/persons |
POST | /activities | Create an activity (call, meeting, etc.) |
GET | /pipelines | List sales pipelines |
Quickstart
GET /v1/deals?status=open&limit=10&api_token={token}
Response: {"success":true,"data":[{"id":1,"title":"Big Deal","value":50000,...}]}
Agent pitfalls & tips
- API token in query param is simplest but less secure โ use OAuth for production.
- All responses have success boolean โ check it, HTTP 200 doesn't guarantee success.
- Custom fields use hashed keys (e.g., 'abc123_custom_field') โ GET /dealFields to map names.
- Use filter_id parameter to apply saved filters from the UI.
- Deals flow through pipeline stages โ use PUT /deals/{id} to move stages.
Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-07. Specs change โ verify against the official docs before production use.
Frequently Asked Questions
What is Pipedrive's AEO score?
โผ
Pipedrive has an AEO score of 0.70 and is rated A (Functional agent integration). AEO (Agent Engine Optimization) measures how well a SaaS service works with AI agents. Scores range from 0.00 to 1.00, with grades from AAA (best) to D (not agent-ready).
Is Pipedrive AI-agent-ready?
โผ
Pipedrive is currently connectable for AI agent use. API access is available but no dedicated MCP server has been published yet. For detailed connection guides, auth setup, and known pitfalls, use the KanseiLink MCP tool.
How does Pipedrive compare to other CRM & Sales services?
โผ
In the CRM & Sales category, Pipedrive is rated A. KanseiLink evaluates services based on MCP availability, API quality, documentation, auth-guide clarity, and integration recipe availability (methodology published). Visit the full rankings at kansei-link.com to see how Pipedrive compares.
How can I integrate Pipedrive with an AI agent?
โผ
The fastest way to integrate Pipedrive with an AI agent is through KanseiLink MCP. Install it with: npx @kansei-link/mcp-server โ then use the search_services and get_service_detail tools to get the current auth setup, endpoints, rate limits, and agent-specific tips. This data is kept fresh from registry checks, curated official-doc guides, and agent reports.
How do I authenticate with Pipedrive?
โผ
API token or OAuth 2.0. API token from Settings > Personal preferences > API. Pass as api_token query parameter or OAuth Bearer. Setup: 1. Settings > Personal preferences > API > copy API token. 2. Append ?api_token={token} to all requests. 3. For OAuth: register app in Marketplace, implement auth code flow.
What are Pipedrive's API rate limits?
โผ
80 req/2sec (Essential), 160/2sec (Advanced), 240/2sec (Professional). X-RateLimit-* headers.