Keep Pipedrive. Klipy runs the follow-up.

The gap Klipy fills

Pipedrive is a strong pipeline-first CRM, but it doesn't read a Gmail or Outlook inbox for sales signal on its own. Most teams still log calls and emails by hand, or bolt on a separate tool for that layer. Klipy fills that gap: it captures conversations across email and meetings, drafts the follow-up for your approval, and keeps Pipedrive current through a native two-way sync.

Pipedrive runs its own AI features inside the CRM. Klipy runs the AI in the inbox and around the pipeline, so the two sit on different parts of the job rather than competing for the same one.

How it connects

Klipy connects to Pipedrive with a native two-way sync, included on the Growth plan and up: contacts, companies, and deals move in both directions, so the pipeline stays current without you logging it in by hand. Connect Pipedrive from Klipy alongside your email and calendar, and the sync runs from there. Nothing to migrate.

Beyond the built-in sync, the same connection is open: an API, webhooks, and an MCP server, documented for teams who want to build past what the sync covers.

API

Create and update Pipedrive-bound contacts, companies, and deals with Klipy's REST API v2. Requests authenticate with a scoped klipy_live_* key and are rate-limited to 200 requests per minute per key, 1,000 per minute per organization. POST and PATCH calls accept an Idempotency-Key header: send the same key with the same request body twice, and the second call returns the cached response instead of creating a new record.

curl https://api.klipy.ai/api/v2/contacts \
  -X POST \
  -H "X-Klipy-Api-Key: <key>" \
  -H "Idempotency-Key: 8f14e45f-ceea-4b0a-9127-1e2e3c3c1a1a" \
  -H "Content-Type: application/json" \
  -d '{"email": "person@example.com"}'

Webhooks

Subscribe to Klipy events like deal.created, deal.moved, lead.captured, and interaction.captured, and react the moment something changes on Klipy's side. Deliveries go out over Svix with signature verification, so your endpoint can trust every payload it receives. Here's what a lead.captured payload looks like:

{
  "type": "lead.captured",
  "object": "event",
  "data": {
    "id": "h7w8y2f1",
    "first_name": "Jordan",
    "last_name": "Patel",
    "email": "jordan.patel@acmeanalytics.com",
    "title": "Head of Growth",
    "company_name": "Acme Analytics",
    "company_domain": "acmeanalytics.com",
    "industry": "SaaS",
    "employee_count": 350,
    "estimated_revenue": 1200000,
    "city": "Austin",
    "state": "TX",
    "country": "US",
    "linkedin": "https://linkedin.com/jordan-patel"
  }
}

MCP

Klipy's MCP server at https://api.klipy.ai/mcp lets an agent read and write both sides of the connection: pull Pipedrive-bound records from Klipy, or propose updates back. It authenticates over OAuth and exposes 38 tools across 9 capability scopes. Sending stays gated: an agent can prepare a message, but it needs a single-use confirmation token and your approval before anything goes out.

No-code

Klipy is listed on Zapier and Make.com, so you can build a Zap or scenario that moves records between Klipy and Pipedrive without writing a line of code. Another automation tool, like n8n, can reach the same API and webhooks with a generic HTTP node.