Integrations
Kaypo reads your Salesforce pipeline and the activity around it, scores every open opportunity, and proves those scores against the opportunities you have already won and lost.
What Kaypo reads
Opportunities, accounts, contacts and owners, and the activity attached to them: tasks, events and stage history, each with its timestamp. Task and event descriptions are read for what a buyer said about budget, authority, process and competition.
Once an admin turns on lead routing, new Leads too: name, email, title, company, website, Lead Source, owner and whether the Lead is converted. They are read with the same access as everything else, and only Leads created after routing was turned on are routed.
What Kaypo writes
Nothing, by default. Every write is something your team said yes to, and every one is recorded.
Kaypo never deletes a record, converts a Lead or edits an activity.
What Kaypo stores
The opportunity, account and contact records it needs to score, the signals derived from activity, and the score history. Activity bodies are read to derive signals and are not kept. A Lead that routing reads is not stored; for one it routes, Kaypo keeps its Salesforce id, the fit, the reasons and the rep. Tokens are encrypted at rest.
Connecting and disconnecting
Connect from Connections inside Kaypo through a Connected App. Disconnecting erases the stored token immediately and stops every sync. What Kaypo already read stays in the workspace, so reconnecting restores it as it was. The owner removes it by deleting the workspace, or by writing to hello@sapwood.io.
Security has every read and write in one place.
If Salesforce asks for your admin
Since September 2025, Salesforce lets most users connect only the apps their org has installed. If Kaypo says your admin needs to approve it, your Salesforce admin does one of these, then you press Connect again:
Either way it takes a few minutes, and Kaypo only reads until your team says yes to a write: score writeback, an agent change somebody approves, or lead routing.