What Klipy adds on top of Salesforce
Salesforce is the default system of record for many B2B SaaS sales teams, but it doesn't read a Gmail or Outlook inbox for sales signal on its own. Most Salesforce teams either log activity by hand or bolt on a separate tool for that layer. Klipy fills that gap: it captures conversations across email and meetings, then writes the result back to Salesforce.
This matters most for teams whose founder-led sales motion has grown past one person carrying the pipeline: Salesforce is already the system of record, and Klipy adds the capture, drafting, and follow-up work it doesn't do natively. This isn't a Salesforce replacement. Salesforce keeps its job throughout.
How Klipy connects to Salesforce
Salesforce connects through Klipy's open surfaces, the same mechanism as HubSpot, Pipedrive, and Attio. There's no bundled one-click Salesforce connector in Settings. Four routes get you there.
Klipy's REST API v2 creates and updates Salesforce-bound contacts, companies, and deals directly, using scoped klipy_live_* keys across 11 resources, at 200 requests per minute per key and 1,000 per minute per org, with Idempotency-Key support so a retried request with the same key returns the cached response instead of creating a second record. Webhooks let you subscribe to Klipy events like deal.created, deal.moved, lead.captured, and interaction.captured, and push the change into Salesforce the moment it fires; delivery runs through Svix with signature verification (see event types). Klipy's MCP server at https://api.klipy.ai/mcp lets an agent read and write both sides, behind an OAuth consent screen with 38 tools across 9 capability scopes; sending a message through it still requires a separate confirmation step before anything reaches a prospect. And because the API and webhooks are open, they also power no-code tools such as Zapier, Make, and n8n, so a non-engineer can wire up the sync with a Zap or a scenario instead of writing code.
On Salesforce's own side, the standard route is a Connected App authenticated with OAuth 2.0, then calls against Salesforce's REST or Bulk API, or Salesforce's own outbound-message and Platform Events mechanisms for the reverse direction.