Connector for Salesforce

The Salesforce connector imports user data from Salesforce using the Salesforce SOQL REST API. This enables you to bring relevant user attributes into Nexthink Adopt, allowing for enhanced targeting and personalization. Use the Salesforce connector to enrich custom fields in the Nexthink interface.

The connector supports OAuth and Basic Auth authentication methods. However, they appear as two separate connectors in the list:

• Salesforce: user attributes (OAuth)

• Salesforce: user attributes (Basic Auth)

Prerequisites

Before configuring the Salesforce connector, ensure:

• You have required administrator rights to configure a connected application in Salesforce. Refer to the official Salesforce documentation for more information.

• Configure the connector credentials using the relevant authentication method. Refer to the Nexthink connector credentials documentation for more information

Configuring the Salesforce application

To use OAuth 2.0 authentication for the connector, you must create a Connected App in Salesforce:

1. Go to Setup > Platform Tools > Apps > External Apps.

2. Click External App Manager > New External App.

3. Add the required fields under Basic Information to create the application:

   • Connected App Name: e.g., Nexthink Adopt Integration

   • API Name: Auto-generated

   • Contact Email: Your valid email address

   • Distribution State: Select Local

4. Click Create

5. If you use OAuth authentication, go to the Settings tab and click Edit to enable OAuth settings.

6. Under OAuth Settings, select the Enable OAuth Settings checkbox.

7. Add required fields under App Setting:

   1. Callback URL: Use http://localhost (placeholder)

   2. OAuth Scopes: Select the revelant OAuth scope

8. Under Flow Enablement, select the Client Credentials Flow checkbox.

9. Under the Security, select the:

   • Require secret for Web Server Flow checkbox

   • Require secret for Refresh Token Flow checkbox

10. Click Save

11. Navigate to the OAuth Settings and click on the Consumer Key and Secret to retrieve the credentials

• Follow Salesforce's prompts to verify your identity

• Click the copy to copy the Consumer Key and Consumer Secret key.

Configuring the Connector credentials

Use your Salesforce credentials to create new credentials for the integration between Nexthink and Salesforce. Refer to the Connector credentials for more information.

Configuring the Salesforce connector

From the Nexthink web interface:

1. Go to Administration > Inbound connectors.

2. Click the New connector button in the top-right corner of the page.

3. Select either Salesforce: User Attributes (Basic Auth) or Salesforce: User Attributes (OAuth), depending on your authentication method.

The General tab includes:

• Name: A meaningful name for the connector. This name appears on the administration page.

• NQL ID: A unique identifier for the connector used when referencing the Salesforce connector in NQL queries. You can initially modify the suggested NQL ID, but once you save the workflow, you can no longer change the NQL ID.

• Description: A short description of the purpose and behavior of the connector.

• Scheduling:

  • Recurrence: Set the execution time and recurrence. Executions start at the scheduled time.

• Connection:

  • Credentials: Select preconfigured credentials from the Connector credentials page. The connector supports Basic and OAuth authentication. Refer to the Connector credentials documentation for more information.

  • URL: This URL is automatically populated when you select credentials.

The Parameters tab includes:

• Query: Enter the Salesforce Object Query Language (SOQL) query to be executed by the Salesforce API. The query must return a list of User objects including:

  • Fields to import (e.g., name, email, department)

  • Use a field to identify the user and map it to the Nexthink identifier (for example, a user name in the form of an email address or UPN).

The Data mapping tab includes:

• Identification: Select a field from the API response to be used to identify users.

  • Source identifier (JSONata): Enter the field name returned by the API response that identifies users. Use JSONata if needed to transform the value.

  • Nexthink identifier: Select either UPN (requires UPN collection via Collector) or Email address (requires the Entra ID connector).

• Field Mapping: Click Add mapping to define how API response fields are matched to Nexthink custom fields.

  • Source identifier (JSONata): Specify the field name in the API response that contains the data to be imported. If you need to transform the data before mapping, use JSONata.

  • Nexthink field: Select the custom field on the User object for data import.

Known limitations

• If employees share the same UPN, the UPN-based identification only processes the first 1,000 user records.

• User Principal Name (UPN) requires configuration in Collector.

• Email address requires the Entra ID (Azure AD) connector.