What Attio does, and the gap Klipy fills
Klipy captures the inbox and meeting signal most CRMs don't read on their own, then writes the result back to Attio. Attio itself is a strong, API-first CRM: it's built around its own REST API, real-time webhooks, and, per Attio's developer docs, its own MCP server for managing a workspace via AI. That makes it a solid system of record for a technical team.
But like most CRMs, Attio doesn't read a Gmail or Outlook inbox for sales signal on its own. Most teams still log calls, emails, and meeting notes by hand, or stitch together separate tools to cover that layer. Klipy fills that capture gap and keeps Attio current with what actually happened in the conversation.
How Klipy connects to Attio
Growth tier and above adds native two-way sync with Attio: Klipy keeps contacts and deals current from captured conversations, without anyone typing it in. Beyond the native sync, direct connection surfaces let you build your own flow on top, or use instead if you're not yet on Growth.
API. Create and update Attio-bound contacts, companies, and deals with Klipy's REST API v2: scoped klipy_live_* keys, 11 resources, 200 requests per minute per key and 1,000 requests per minute per org, with Idempotency-Key support on POST and PATCH.
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 lead.captured, interaction.captured, deal.created, and deal.moved, 12 wired in total, delivered via Svix with signature verification.
MCP. Klipy runs its own OAuth-gated MCP server (38 tools across 9 scopes, send-gated) so an external agent can read and write on Klipy's side. This is separate from the MCP server Attio publishes for its own workspace; Klipy doesn't read from or write to it.
No-code. The same API and webhooks power Zapier, Make, and n8n, so you can build your own Zap or scenario for anything the native sync doesn't cover, or if you're on a plan below Growth.
Attio's own REST API and real-time webhooks (at developers.attio.com) work the same way on its side, so a Zap, scenario, or custom script can move data in either direction alongside the Growth-tier sync.