Integrations · CRM & sales

Salesforce in the conversation.

The enterprise CRM of record, and usually the system every other tool is reconciled against. Connect it once and your copilot works with leads, accounts, contacts, opportunities and cases without leaving the thread — and your workflows can act on it while the customer is still typing.

Start free trial →All integrations

No credit card required · 7-day free trial

Salesforce

CRM & sales

01 · COPILOT

Ask for it in plain language. It does the Salesforce part.

Copilot rides inside the inbox. With Salesforce connected it reads leads, accounts, contacts, opportunities and cases and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

Find an account, contact or lead by name, email or record id
Read an opportunity — stage, amount, close date and owner
Create a lead from an inbound conversation
Update fields on a record, including custom ones
Log a task or activity against an account
Run a SOQL-shaped query for the records matching a condition

What a specific connection exposes is decided by Salesforce, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.

02 · WORKFLOWS

Something happens in Salesforce. A workflow starts.

Once Salesforce is connected, its events show up in the workflow editor's trigger picker, and the fields the event carries become variables every later step can read — so the message you send is written from what actually happened.

A lead or contact is created
An opportunity changes stage
A case is opened or updated

The picker is the authority on which events your Salesforce connection publishes — these are the kinds that apps of this sort emit.

03 · THE AI AGENT STEP

One step that decides which Salesforce tools to call.

A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.

You declare the output

The rows you name become the variables downstream steps read, so a branch can test what Salesforce said.

You cap the effort

A step budget and a model tier per node — the loop stops where you told it to.

Only what you switched on

The loop can call the Salesforce tools you left enabled and nothing else.

What teams do with it

Two ways Salesforce earns its connection.

Qualify without a tab switch

An agent working a live chat asks Copilot whether this account is a customer, and gets the answer out of Salesforce in the same panel as the conversation.

Inbound becomes a lead automatically

A workflow creates the Salesforce lead the moment a first-time contact asks a pricing question, with the channel and the campaign that brought them in already on the record.

Setup

Connect Salesforce in about a minute.

1
Open Settings → Apps
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
2
Find Salesforce in Browse
The catalogue runs to hundreds of apps and is searchable. Connect Salesforce from its card.
3
Authorize with your own Salesforce account
You sign in on Salesforce's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
4
Choose the tools it may call
Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.

Open Settings → Apps →

Salesforce questions.

How do I connect Salesforce to Cloodot?

Open Settings → Apps in Cloodot, switch to Browse, and search for Salesforce. Connecting it opens Salesforce's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.

What can Cloodot do in Salesforce?

Work of this kind: find an account, contact or lead by name, email or record id; read an opportunity — stage, amount, close date and owner; create a lead from an inbound conversation; update fields on a record, including custom ones; log a task or activity against an account; run a soql-shaped query for the records matching a condition. The exact list depends on what your Salesforce account is allowed to do — Settings → Apps shows every tool the connection actually exposes.

Can I limit which Salesforce tools Cloodot may use?

Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Salesforce connection is a matter of leaving the writes off.

Can an event in Salesforce start a Cloodot workflow?

Yes. Events like a lead or contact is created, an opportunity changes stage, a case is opened or updated appear in the workflow editor's trigger picker once Salesforce is connected, and the event's own fields become variables the rest of the workflow can read.

Who in my team can connect Salesforce?

Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Salesforce account that authorized it, so a crm & sales connection is only ever as broad as the account behind it.

More crm & sales