Salesforce + Kroy

Connect Salesforce once. Use it safely with any AI.

  1. Salesforce, where it already is.

    Salesforce stays the authoritative record. Nothing moves, and nothing is copied that doesn’t need to be.

  2. Salesforce connects to Kroy.

    OAuth 2. Kroy holds the connection.

  3. Your AI connects to Kroy.

    Claude, ChatGPT or another AI connects to Kroy — not to Salesforce. It never receives Salesforce credentials.

  4. Exactly what is allowed.

    Each Salesforce action is a Kroy capability; update contact waits for a person by default. Records cannot be deleted through Kroy.

  5. A real request.

    Claude asks for read accounts. Kroy checks the person, the agent and the policy, calls Salesforce, and records the request.

Salesforce
Kroy
Claude
Priya Client manager
AUDIT

Salesforce capabilities

  • salesforce.account.read
  • salesforce.contact.read
  • salesforce.opportunity.read
  • salesforce.task.create
  • !salesforce.contact.update
  • Records cannot be deleted through Kro…
Salesforce
Kroy
Claude
Priya Client manager
AUDIT

Salesforce capabilities

  • salesforce.account.read
  • salesforce.contact.read
  • salesforce.opportunity.read
  • salesforce.task.create
  • !salesforce.contact.update
  • Records cannot be deleted through Kro…
Salesforce connecting to Kroy, then to an authorised AI. Salesforce, where it already is.. Salesforce connects to Kroy.. Your AI connects to Kroy.. Exactly what is allowed.. A real request..

Supported resources

  • Accounts
  • Contacts
  • Leads
  • Opportunities
  • Tasks and activity history
  • Notes

Authentication

OAuth 2.0 through a Salesforce connected app, approved by a Salesforce administrator. Kroy holds the connection; AI clients never receive Salesforce tokens.

Supported actions

CapabilityTypeDefault
salesforce.account.read
Read accounts
readPolicy
salesforce.contact.read
Read contacts
readPolicy
salesforce.opportunity.read
Read opportunities
readPolicy
salesforce.task.create
Log task or call
writePolicy
salesforce.note.create
Add note
writePolicy
salesforce.lead.create
Create lead
writePolicy
salesforce.contact.update
Update contact
writeHuman approval
salesforce.opportunity.update
Update opportunity
writeHuman approval

Events

salesforce.opportunity.updatedsalesforce.lead.created

Overview

CRM data is only useful when it is kept up to date, and keeping it up to date is the job everybody postpones. AI can help: summarising a call, logging the follow-up, noting that a deal has moved.

Kroy connects to Salesforce once. Authorised AI tools reach Salesforce through Kroy, which knows the person behind each request and limits what the AI can see and change.

Permissions

Each Salesforce action is a Kroy capability. Kroy decides every request against the person, the agent, the delegation between them and the organisation’s policies.

By default, AI may read, log activity, add notes and create leads. Updating an opportunity — its stage, value or close date — and updating a contact’s details require approval, because these records feed forecasts and client communications. A sales director might allow a Skill to propose opportunity changes while a person confirms each one.

Proposed updates

A useful pattern: after a meeting, the AI prepares a set of proposed CRM changes — a logged call, a new next step, an updated close date. The account owner sees them together, accepts or rejects each, and Kroy applies the accepted ones. Kroy records the proposal, the decision and the change.

Industries

Financial services firms, consultancies and technology companies rely on accurate client records. Where client information is sensitive, Kroy can keep particular fields or record types out of AI’s reach altogether.

Security

Kroy holds the Salesforce connection. AI clients never receive tokens. Every request, approval and refusal is recorded, and revoking an AI’s Kroy access removes its Salesforce access at the same moment.

Limitations

  • Records cannot be deleted through Kroy.
  • Bulk updates and data imports are not supported.
  • Salesforce configuration, metadata and user administration cannot be changed through Kroy.
  • Salesforce profiles, permission sets and field-level security for the connected user still apply.
  • Actions count towards your Salesforce API limits.