Skip to main content
Feedback

Salesforce connection

The Salesforce connection represents a single Salesforce organization, including login credentials.

If you have multiple organizations or sandbox instances, you need a separate connection for each. You can pair a single connection with different Salesforce operations to perform a unique action against a Salesforce organization.

Connection tab

URL

This connector exclusively supports SOAP-based service URLs. Providing a REST-based URL in this field is not supported and will result in connection failures.

  • For Username-Password Authentication - The default URL for new Salesforce connection’s web services is changed. For production this should always be: https://login.salesforce.com/services/Soap/u/<your_version_of_Salesforce>

  • For Oauth 2.0 - The URL inserted in the Connection tab for OAuth 2.0 should be the instance URL. Ex: <domain-instance-url>.my.salesforce.com/services/Soap/u/39.0

Important

Versions of the SOAP API older than version 30.0 are no longer supported. You can reference which version numbers are currently supported at API End-of-Life Policy. See List Available REST API Versions to view summary information about currently available REST API Versions.

Integrations using outdated URLs continue to show the original configuration but are redirected automatically.

To take advantage of the feature provided by Bulk API v2, update the URL to Salesforce API version 41.0 or later.

Authentication Type

note

Environment Extensions can manage Salesforce authentication fields, but they cannot switch the Authentication Type (for example, Username-Password ↔ OAuth 2.0) dynamically. Set the authentication type on the Base Connection component and redeploy the process.

Username-Password

  • User - The user name to log in to Salesforce. The user must have sufficient permissions to use the API and perform the necessary actions required by your integration scenario.

  • Password - The password to log in to Salesforce. The password is often concatenated with a security token. See the Replacing your Salesforce password with a password and security token topic for more information.

OAuth 2.0

Prerequisites

  • Salesforce connected app or Salesforce External app configured with Client Credentials (for OAuth 2.0 authentication).
  • API access privileges confirmed by your Salesforce representative.

When OAuth 2.0 is selected as the Authentication Type, the following properties are displayed:

important

The URL inserted in the Connection tab for OAuth 2.0 should be the instance URL.

PropertyHelp Text
Grant TypeOAuth 2.0 grant type to connect with your Salesforce connected app. (Displays one option only: Client Credentials.)
Client IDEnter the Client ID from your Salesforce connected app.
Client SecretEnter the Client Secret from your Salesforce connected app.
Access Token URLEnter the Salesforce OAuth token endpoint.
note

The connector supports the latest API version listed at API End-of-Life Policy automatically without needing connector updates.

Maximum Concurrent Connections - Sets the maximum number of concurrent connections to the Salesforce application. Enter up to 25. The default is 10.

On this Page