SALES & CRM

Salesforce + governed AI agents

Salesforce holds the record your revenue team argues about. An agent that can read it becomes useful immediately; an agent that can write to it without review becomes a data-quality incident. FlozentAi imports the Salesforce REST API, publishes only the actions you approve, and holds every write behind a human decision.

Start building How importing works

Connecting Salesforce

Definition	Import the Salesforce REST API OpenAPI description, or point the importer at your own gateway spec if you front Salesforce with one.
Credential	OAuth 2.0 — store the access and refresh tokens your connected app issued.
Stored as	A `secret://` reference to your own vault. FlozentAi never holds the value.

Actions teams usually publish

Action names are yours to choose during review — these are the shapes most teams end up with. Anything that writes is confirmation-gated unless you deliberately publish it otherwise.

Action	Kind	What it does
`account.get`	Read	Resolve an account by id, name or domain.
`opportunity.list`	Read	Pull open opportunities for a given account or owner.
`case.create`	Write	Open a case. Marked high risk, so it pauses for approval.
`opportunity.update`	Write	Change stage or close date. Approval is bound to the exact field values proposed.

What people build with it

A renewal assistant that reads the account, checks the open invoice elsewhere, and drafts the follow-up for a human to send.
A support agent that can see the customer’s plan and entitlement without giving the model a Salesforce session.
An internal assistant that proposes pipeline hygiene fixes and waits for the rep to approve each one.

The credential never enters FlozentAi

There is no field in the console that accepts a token or a password. You store the secret in your vault and give FlozentAi a reference; the runtime resolves it inside the execution layer, after the policy decision.

Salesforce questions

Does FlozentAi store our Salesforce credentials?

No. You put the tokens in your own vault and give FlozentAi a secret:// reference. The runtime resolves that reference inside the execution layer; the value is never entered in the console and never reaches the model.

Can we allow reads but not writes?

Yes. Actions are approved individually during import review. Publishing only the read actions is the normal starting point, and the write actions stay unpublished until you decide otherwise.

How do we keep one customer’s data out of another’s?

Each of your customers is a host tenant, and each run is bound to one. Tenant isolation is enforced in the database with row-level security, not by prompt instructions.

Use cases that involve Salesforce

Product

Embedded product assistant

Ship an AI assistant inside your own SaaS product, scoped per customer, without building the governance layer yourself.

Connect Salesforce the governed way.

Import the specification, review what it found, and publish only what you want reachable.

Create your workspace Read the docs

Salesforce + governed AI agents

Connecting Salesforce

Definition

Import the Salesforce REST API OpenAPI description, or point the importer at your own gateway spec if you front Salesforce with one.

Credential

OAuth 2.0 — store the access and refresh tokens your connected app issued.

Stored as

A secret:// reference to your own vault. FlozentAi never holds the value.

Actions teams usually publish

Action names are yours to choose during review — these are the shapes most teams end up with. Anything that writes is confirmation-gated unless you deliberately publish it otherwise.

Action

Kind

What it does

account.get

Read

Resolve an account by id, name or domain.

opportunity.list

Read

Pull open opportunities for a given account or owner.

case.create

Write

Open a case. Marked high risk, so it pauses for approval.

opportunity.update

Write

Change stage or close date. Approval is bound to the exact field values proposed.