Integrations

Kaypo and Salesforce.

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.

  • Score writeback, once somebody turns it on: one number to one custom field on the opportunity, which you choose.
  • An edit made in Kaypo: the owner, stage, amount or close date of an opportunity.
  • Agent work, after somebody presses Approve: a task with the drafted email, the Next step, a corrected close date or stage, or the owner of a company family’s opportunities and Account. Undo lasts seven days.
  • Lead routing, once an admin says yes to it: for each new Lead from a web or form Lead Source (or sources the admin picks), not converted, owned by a queue or by a user the admin marked as unassigned, and at a company nobody owns or has an open opportunity with, the rep as the Lead owner and a task on the Lead with the fit and why it matches. Contacts and Accounts keep the owners they have.

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:

  1. Install Kaypo for the org. In Setup, open Connected Apps OAuth Usage, find Kaypo and choose Install. Then open Manage Connected Apps, edit Kaypo’s policies, set Permitted Users to “Admin approved users are pre-authorized”, and add the profile or permission set of the people who will connect.
  2. Or let one person approve it. Give the person connecting the Approve Uninstalled Connected Apps permission through a permission set.

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.

All integrations