Connect Salesforce to Windsurf
Give Windsurf governed access to Salesforce’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Salesforce to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf 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 Windsurf to Runlayer
Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Salesforce’s 21 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf 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 Windsurf
Salesforce’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
21 Salesforce tools in Windsurf
Runlayer policy decides which of these Windsurf 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 Windsurf
Some controls apply to every client at the gateway. Others depend on what Windsurf exposes to Runlayer.
Gateway policy (available)
Every Salesforce call from Windsurf passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Windsurf as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Windsurf runs it.
Block output after it runs (not available)
Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.
In Windsurf
- Enforcement needs Windsurf 1.12.31 or newer.
- When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.
Frequently asked questions
Connect more