Gentrack Integration Resources

Salesforce Sales Cloud V2

Overview

Salesforce Sales Cloud is a sales performance management solution that compliments your Gentrack solution by providing lead-to-order journey management for demanding sales teams.

Gentrack Cloud Integration Services offers a native integration with Salesforce Sales Cloud which has been optimized to deliver the best of both systems. Our connector allows Gentrack events to be published to Salesforce in a format compatible with our managed salesforce package. Gentrack regularly invests in performance, reliability, and quality of the integration which is important in keeping pace of change driven by Salesforce, as well as Gentrack’s own products. Using this connector allows you to focus on your business and not worry about maintaining the skills necessary in both billing and CRM spaces, as well as integration strategies and tooling.

The documentation captures the general process of enabling the connector. Given the nature of Salesforce we consider this to be a complex connector where pricing includes an on-boarding program for us to work with you to activate the connector as well as address your unique integration needs.

Before you begin

To use this connector you will need to ensure that you are running:

  • Gentrack Billing System
    • Velocity 4.13 or later, with the latest system modules
    • Junifer 6 or later
  • Salesforce Sales Cloud Enterprise Edition
    • The integration user will require a licensed user profile

Preparing your Salesforce instance

Before you connect your Salesforce instance you will need to create an integration user and an External Client App that the connector will authenticate as.

Note: As of the Salesforce Spring ‘26 release, the creation of new Connected Apps is disabled by default in newly created Salesforce environments. The Salesforce Sales Cloud Connector V2 uses an External Client App with the OAuth 2.0 Client Credentials flow and no longer requires a username, password, or security token.

Creating the integration user

The integration user is the Salesforce user the External Client App will run as when the connector calls into your Salesforce instance.

  1. Create a new user for the integration account using the following values set and reviewing other settings as per your instance’s configuration:
    • Name: gcis-salesforce-sales-cloud-connector@[your domain]
    • Email Address: gcis-salesforce-sales-cloud-connector@[your domain]
    • User License: Salesforce
    • Profile: Standard User (or equivalent that can edit data)
  2. Take note of the user’s Username (not email address) - it will be needed when configuring the External Client App’s Run As field below.

Creating the External Client App

The External Client App allows the connector to authenticate to Salesforce using the OAuth 2.0 Client Credentials flow.

  1. In Salesforce Setup, navigate to External Client Apps and create a new External Client App with the following settings:
  2. Expand API (Enable OAuth Settings) and configure:
    • Enable OAuth: Checked
    • Callback URL: http://localhost
    • Selected OAuth Scopes:
      • Manage user data via Web browsers (web)
      • Manage user data via APIs (api)
    • Introspect All Tokens: Checked
    • Enable Client Credentials Flow: Checked
  3. Click Create.
  4. On the Manage External Client Apps page, click Edit, then expand OAuth Policies and configure:
    • Enable Client Credentials Flow: Checked
    • Run As: the Username of the integration user created above (not their email address)
    • IP Relaxation: Relax IP restrictions
  5. Click Save.
  6. Switch to the Settings tab, expand OAuth Settings, then click Consumer Key and Secret and take note of the following values for later:
    • Consumer Key
    • Consumer Secret

Connecting to Salesforce

When you are ready to create a new connector instance:

  1. Sign in to the GCIS Developer Portal
  2. Under Connectors click Connector Store
  3. On the Connector Store page choose Salesforce Connector by clicking on the Setup new instance button
  4. In the Setup New Instance dialog, provide the following:
    • Consumer Key - the consumer key of the External Client App
    • Consumer Secret - the consumer secret of the External Client App
    • Login URL - the URL of your Salesforce Sales Cloud instance, e.g. https://{domain}.my.salesforce.com
    • Event Endpoint - the Apex REST API path events will be published to (default: gtx_bu/v2/event)
    • Tenant - select a tenant from the drop down menu that will be connected to this connector instance
  5. Click Add Connector and wait for the instance to be created
  6. Click Test Connection to verify the credentials provided are valid
  7. From the Connectors list select the newly created connector instance, then navigate to the Salesforce Basic Information page

(Optional) API calls to Gentrack

API calls to Gentrack is an optional extra capability in Salesforce Sales Cloud Connector that allows Salesforce applications to directly call Gentrack APIs (Salesforce to Gentrack), separate from the inbound event flow described above.

Refer to How to call Gentrack APIs for more details.

Enable API calls to Gentrack

Once a new connector has been created, you can choose to enable API calls to Gentrack:

  1. Navigate to My Connectors under Connectors on the Developer Portal, find your Connector instance in the table and click on it.
  2. On the Salesforce Basic Information page, click Add under the Named Credentials section to enable API calls to Gentrack.

Note: For security reasons, Gentrack does not save the Named Credential.

Rotate Named Credentials

With the Calling Gentrack APIs feature enabled, you can rotate the Named Credential by clicking on the Rotate button.

Note:

  • You can do this any time you believe the Named Credential is lost or compromised.
  • Once the Named Credential has been rotated, the old credential becomes invalid and can no longer be used to request new access tokens.
  • Access tokens, which are generated before the rotation of the Named Credential, will not be revoked or invalidated. They will continue to be valid until its expiry time.
  • Rotating the Named Credential does not break the existing integration. However, it may take a few seconds for Gentrack to update the Named Credential in Salesforce. During this short period, it is possible that you might not be able to request new access tokens.

Disable API calls to Gentrack

With the Calling Gentrack APIs feature enabled, you can revoke the Named Credential by clicking on the Revoke button.

Note:

  • Once the Named Credential has been revoked, the old credential becomes invalid and can no longer be used to request new access tokens.
  • Similar to rotation, access tokens, which are generated before the revocation of the Named Credential, will not be revoked or invalidated. They will continue to be valid until its expiry time.
Last updated on 27 Apr 2026