Connect Salesforce to ECA
Give ECA governed access to Salesforce’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Salesforce to ECA in four steps
Admins approve the server once. Everyone in ECA 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 ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches Salesforce’s 21 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA 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 ECA
Salesforce’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
21 Salesforce tools in ECA
Runlayer policy decides which of these ECA 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 ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every Salesforce call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more