Salto’s Salesforce adapter allows you to:

Fetch and deploy common Salesforce metadata items, e.g., custom objects and fields, apex classes and triggers, email templates, layouts, process builders, profiles.
In many cases a salesforce org is also configured via data records, e.g., CPQ, SBAA. Salto introduces a unified approach for managing both data records and metadata items from a single place.
Deploy configuration changes from one Salesforce org to another.
Compare orgs.
Audit / document configuration changes.
Monitor specific changes of interest in your Salesforce orgs, e.g., Profiles or Permissions.

Authentication Instructions

In order to connect Salesforce to Salto you can either:

Connect via OAuth:
- Choose OAuth authorization method and click 'Authenticate'.
- If you are connecting to a sandbox, check 'Sandbox account'.
- You will be prompted to choose one of your authenticated orgs or login to a new one.
- Click 'Allow'.
Connect with your username, password and token:
- Choose 'Username / Password' Authorization Method.
- If you are connecting to a sandbox, check 'Sandbox account'.
- Enter your username, password and token (leave the token field empty if your org uses IP whitelisting).

FAQs

How does a Salesforce config file look like?

Please refer to this page for details.

Which config file changes are needed to manage CPQ via Salto?

Please refer to this page for details.

What impact does Salto have on my API limits?

	Concurrency	Total Requests	Request Size
What are the limits?	API Request Limits and Allocations	API Request Limits and Allocations	Metadata Limits
How can you monitor?	N/A	Go to Setup → System Overview → API Usage Deploy's API consumption variance is high, since it depends on the scope of changes you choose to deploy, and therefore harder to gauge Fetch's API consumptions varies based on the total number of configuration elements in your account, e.g. more custom objects means more API calls, and therefore might be stabler, depending on the rate of change in your organization How to gauge fetch's API usage on your account (click to expand) On the System Overview page, note the number of API requests in the last 24 hours Run Fetch, wait for it to complete Wait an additional 5 minutes to let Salesforce update their API calls numbers Refresh the System Overview page and note the new number of API requests — the difference should be the number of API calls Fetch used This might not be true if other API-consuming processes ran in parallel to Fetch	N/A
How can you adjust usage or capacity?	See `maxConcurrentRetrieveRequests` in Salesforce adapter configuration.	See `metadataTypesSkippedList` and `instancesRegexSkippedList` in Salesforce adapter configuration.	See `maxItemsInRetrieveRequest` in Salesforce adapter configuration.

Concurrency

Total Requests

Request Size

What are the limits?

API Request Limits and Allocations

Metadata Limits

How can you monitor?

N/A

Go to Setup → System Overview → API Usage

Deploy's API consumption variance is high, since it depends on the scope of changes you choose to deploy, and therefore harder to gauge
Fetch's API consumptions varies based on the total number of configuration elements in your account, e.g. more custom objects means more API calls, and therefore might be stabler, depending on the rate of change in your organization

How to gauge fetch's API usage on your account (click to expand)

On the System Overview page, note the number of API requests in the last 24 hours
Run Fetch, wait for it to complete
Wait an additional 5 minutes to let Salesforce update their API calls numbers
Refresh the System Overview page and note the new number of API requests — the difference should be the number of API calls Fetch used
- This might not be true if other API-consuming processes ran in parallel to Fetch

N/A

How can you adjust usage or capacity?

See maxConcurrentRetrieveRequests in Salesforce adapter configuration.

See metadataTypesSkippedList and instancesRegexSkippedList in Salesforce adapter configuration.

See maxItemsInRetrieveRequest in Salesforce adapter configuration.

What are the advantages of Salto over Salesforce’s native ‘Where is this used’ feature?

Salesforce’s 'Where is this used' only works for Custom Fields while Salto supports standard fields as well as any other metadata type, e.g., Email Templates, Flows, Escalation Rules, Assignment Rules etc.

In addition, Salto enables free text searches across all configuration which allows you to find hardcoded values such as email addresses, profile IDs, and more.

Please refer to this blog post and step by step guides for more information