Connect Salesforce to Claude Cowork
Give Claude Cowork governed access to Salesforce’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Salesforce to Claude Cowork in four steps
Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.
- 1
Approve Salesforce in Runlayer
Add Salesforce from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Claude Cowork to Runlayer
Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Salesforce’s 21 tools show up in Claude Cowork’s own tool list.
Claude Cowork setup guide - 3
Sign in to Salesforce
Sign in the way Salesforce requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Salesforce from Claude Cowork
Salesforce’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.
Tools
21 Salesforce tools in Claude Cowork
Runlayer policy decides which of these Claude Cowork users can call. 7 read data only and 1 can change or delete data.
Create record
Create a new Salesforce record.
Delete record
Delete a Salesforce record by ID.
Describe object
Get detailed metadata for a specific Salesforce sObject including all fields, their types, picklist values, relationships, and constraints.
Get limits
Get the org's API usage limits including daily API calls, data storage, file storage, and other governor limits.
Get record
Retrieve a single Salesforce record by its ID.
List objects
List all sObjects (standard and custom objects) available in the Salesforce org.
Query
Execute a SOQL (Salesforce Object Query Language) query.
Query more
Retrieve the next page of results from a SOQL query.
Control
What Runlayer can see and stop in Claude Cowork
Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.
Gateway policy (available)
Every Salesforce call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.
OTLP telemetry (available)
Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Stop a call before it runs (available)
Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.
In Claude Cowork
- Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.
Frequently asked questions
Connect more