Skip to main content
This is a step-by-step guide to acquiring Salesforce credentials and authorizing the Salesforce Load and Salesforce Query components.

​
Obtain Salesforce credentials

To create an OAuth connection to Salesforce, you need your Salesforce consumer key and consumer secret. In , these are referred to as your client ID and client secret. To find these credentials, follow the steps in the Salesforce View and Rotate the Consumer Key and Consumer Secret of a Connected App documentation until you can view these credentials. Keep this page open or copy and paste them somewhere so you can use them in the OAuth creation process in . You do not need to generate new values for these credentials.

​
Authorize Salesforce components

  1. Follow the instructions in OAuth, and select Salesforce or Salesforce Sandbox in the Provider field, depending on whether you are connecting to a regular Salesforce account or a sandbox account.
  2. In the Authentication type drop-down, select your authentication type:
    • Select OAuth 2.0 Authorization Code Grant to log in to Salesforce to authorize the connection. If you select this option, click Authorize, log in to Salesforce and complete the authorization process.
    • Select OAuth 2.0 Client Credentials to use your credentials. If you select this option, continue with the steps below.
    The OAuth 2.0 Client Credentials grant type does not require a callback or redirect URL. If you’re setting up a connected app in Salesforce, you don’t need to configure one.
  3. In the Token URL field, enter your Salesforce token URL. This URL format differs depending on your Salesforce account type. Replace the placeholders with your domain name and sandbox name, as shown below:
    • For a regular Salesforce account: https://{your-company}.my.salesforce.com/services/oauth2/token
    • For a sandbox account: https://{your-company}--{your-sandbox}.sandbox.my.salesforce.com/services/oauth2/token
  4. In the Client ID field, enter your Salesforce consumer key.
  5. In the Client secret field, enter your Salesforce consumer secret.
    When copying the credentials, some browsers may add a space to the end of the string. Watch out for this as it will cause the credentials to fail.
  6. Click Authorize.
Your new OAuth connection is ready for use with the Salesforce Load or Salesforce Query component.

​
IP allowlisting

Whether you need to allowlist the ‘s IP address depends on your authentication method and your Salesforce Organization’s network settings.

​
Username and password authentication

Salesforce requires a security token only when the connection originates from an IP address outside your Salesforce Organization’s Trusted IP Ranges. You have two options—you only need to do one:
  • Enter your security token in the Security Token field on the connection. No IP allowlisting is needed.
  • Add the ‘s egress IP to your Trusted IP Ranges in Salesforce under Setup > Network Access > Trusted IP Ranges. You don’t need a security token if you do this.
If your Salesforce admin has set Login IP Ranges on your user profile, a security token won’t bypass this restriction. You must add the ‘s egress IP to the allowed range on that profile.

​
OAuth authentication

The security token doesn’t apply to OAuth connections. However, if your Salesforce admin has set Login IP Ranges on your user profile or Connected App, you must still add the ‘s IP address to the allowed range.

​
Which IP address to allowlist

The IP address to allowlist depends on your runner type: