Skip to main content

Configuration of Salesforce Sales Cloud

The Snow Integration Connector for Salesforce Sales Cloud is used to determine the number of registered Sales Cloud users.

The configuration must be started and prepared according to SaaS connector configuration.

Prerequisites​

To configure the connector, your company’s Salesforce website address and the credentials for a Salesforce account, with the permissions described below, are required.

Permissions required for the Set up a Salesforce app in the Salesforce website:

  • Administrative permissions that should be selected:

    • Customize Application, which includes:

      • Manage Custom Permissions

      • View Setup and Configuration, which includes:

        • View Roles and Role Hierarchy

  • General user permissions that should be selected:

    • Manage Connected Apps

Permissions required for the authorization of the app during the OAuth process in Snow Integration Manager:

  • Administrative permissions that should be selected:

    • API Enabled

    • View Setup and Configuration, which includes:

      • View Roles and Role Hierarchy

    • View All Users

Set up a Salesforce app​

  1. Log in to your company’s Salesforce website with the account with admin privileges.

  2. Select the user name in the upper right corner of the website and select Setup.

  3. On the Build > Create menu, select Apps.

    tip

    Search for Apps to make it easier to find the menu option Apps.

  4. In the Connected apps section, select New.

  5. On the Create new connected app page:

    1. In the Connected app name, enter the name of the app.

    2. In the Contact email, enter your email address.

    3. Select the Enable OAuth settings.

  6. In the OAuth settings section:

    1. In Callback URL, enter the following URL: https://login.salesforce.com/services/oauth2/success

    2. From the Available OAuth Scopes list, add Manage user data via APIs (api) and Perform requests on your behalf at any time (refresh_token, offline_access) to the Selected OAuth Scopes list.

    3. Select the Require Secret for Web Server Flow checkbox.

  7. Select Save.

    The new connected app is created and the management page for the app appears. The Consumer key and the Consumer secret are found on the management page. The information is used when configuring the connector.

Configure the Salesforce Sales Cloud connector​

In the Configure section at the bottom of Connector Configuration: SaaS:

  1. In the Client ID, enter the Consumer key generated in Set up a Salesforce app.

    salescloud.png

  2. In the Client Secret, enter the Consumer secret generated in Set up a Salesforce app.

  3. In the EndPoint, enter the web address of your company's Salesforce website.

    tip

    You can find your company's Salesforce web address in the URL of your browser's address bar.

    EXAMPLE

    https://YourDomainName.my.salesforce.com

    https://YourDomainName.salesforce.com

    In the examples mentioned, YourDomainName should be replaced with your company's Salesforce subdomain.

  4. In the Redirect URI, enter the value for the Callback URL of the created app in Set up a Salesforce app.

  5. Select Authenticate.

  6. On the login dialog that appears, to authenticate the connector with your Salesforce account, follow the login procedure.

    A dialog will inform you that the authentication was successful.

    note

    If you are having issues with the login process, instead select Open default browser at the bottom of the login dialog. This opens the login page in your default browser instead.

    After a successful login, copy the url in the address bar of the browser and paste it into the text box dialog that has appeared in SIM.

  7. To verify the connection, select Test connection.

  8. If the connection could not be established, verify that the connector has been configured according to Step 1 till 7 of the Configure the Salesforce Sales Cloud connector.

  9. To allow the data to be aggregated, select the Active checkbox.

  10. Select Save.

Flexera does not own the third party trademarks, software, products, or tools (collectively, the "Third Party Products") referenced herein. Third Party Product updates, including user interface updates, may not be reflected in this content.