Integrations

Kaypo and HubSpot.

Kaypo reads your HubSpot pipeline and the activity around it, scores every open deal, and proves those scores against the deals you have already won and lost. It is the only connection Kaypo requires, because a deal has to exist somewhere before it can be scored.

What Kaypo reads

Deals, companies, contacts and owners, and the engagement attached to them: emails, meetings, notes, tasks and stage changes, each with its timestamp. Note and email text is read for what a buyer said about budget, authority, process and competition.

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 property on the deal, which you choose.
  • An edit made in Kaypo: the owner, stage, amount or close date of a deal.
  • Agent work, after somebody presses Approve: a task with the drafted email, the deal’s Next step, a corrected close date or stage, or a company family’s owner. Undo lasts seven days.
  • Lead routing, once an admin says yes to it: for each new contact who submitted a form (or came from sources the admin picks), with no owner, on no open deal and at a company nobody owns, the company owner, the owner on any unowned open deal there, and a task for the rep with the fit and why it matches.

Setting a company owner needs HubSpot’s permission to edit companies (crm.objects.companies.write). Kaypo asks for it only as an optional permission, so a portal that does not grant it still connects, and Kaypo then writes the deal owner and the task instead. Connections says which one your connection has. A connection made before November 6 gets it by reconnecting HubSpot. Kaypo never deletes a record or edits a note.

What Kaypo stores

The deal, company and contact records it needs to score, the signals derived from activity, and the score history. Email and note bodies are read to derive signals and are not kept. Tokens are encrypted at rest.

Connecting and disconnecting

Connect from Connections inside Kaypo. 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.

All integrations