Who can use this feature?
- Global admins or users with advanced permissions
- Available on all plans
A connection is an authentication mechanism to allow Totango to integrate with another system. Each connector has different requirements for connection. You can reuse connections to support multiple integration jobs.
CRM integrations are a closed system; you cannot reuse CRM connections for other integration families.
A Salesforce connection requires a dedicated connected app configured in Salesforce and OAuth credentials. The dedicated connected app is the authentication endpoint, and the OAuth user holds the object permissions to your Salesforce instance.
The Salesforce connector user should have “API Access” enabled and should have full read/write abilities on the objects you want to pull data from. Additionally, Totango Customer Data Hub uses Salesforce REST API v47.0 (/services/data/v47.0) to retrieve the data and update your sync-back attributes. Refer to this article to understand which Salesforce editions are rest compatible.
1. Create a connected app in Salesforce
A connected app is required for an authentication endpoint within Salesforce. The new connected app informs Salesforce of this new authentication entry point and includes the relevant authentication configuration.
- Log into Salesforce using an account with administrator access.
- To access the Code and Credentials Flow settings, allow external client apps to access the flow.
- From Setup, in the Quick Find box, enter OAuth, and then select OAuth and OpenID Connect Settings.
- Turn on Allow Authorization Code and Credentials Flows.
- Create a new connected app.
- Lightning view: Open Platform Tools > Apps > External Client App > Settings. (Or from Setup, enter External Client Apps in the Quick Find box, then select Settings in the External Client App section.)
- Turn on Allow creation of connected apps, if it's off.
- Click New Connected App.
- Classic view: No longer supported.
- Lightning view: Open Platform Tools > Apps > External Client App > Settings. (Or from Setup, enter External Client Apps in the Quick Find box, then select Settings in the External Client App section.)
- Configure basic connected app settings:
- Enter the name of your application (Totango Connected App or your choice).
- The name "TotangoApp" and "TotangoAppSandbox" are saved for the Totango package. Please do not use those names to prevent duplication.
- Enter the contact email information, as well as any other information appropriate for your application.
- Enable OAuth Settings for API Integration.
- In the API (Enable OAuth Settings) area of the page, select Enable OAuth Settings.
- Enter this Callback URL:
https://app.totango.com/auth/connector/callback. - OAuth scopes are permissions given by the user running the connected app. Add these scopes to the Selected OAuth Scopes:
- Full access (full)
- Perform requests on your behalf at any time (
refresh_token,offline_access). This permission lets Totango refresh its connection without a person signing in again.
- Ensure the Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows box is checked.
- Ensure the Enable Refresh Token Rotation box is checked.
- Ensure the Limit Idle Refresh Token Time-to-Live (TTL) to 30 Days box is checked.
- Ensure the Require Secret for Refresh Token Flow box is cleared (not checked). Totango cannot refresh its connection when this setting is on.
- Click Save.
- Click Continue.
It will take 30-45 minutes before your new connected app is propagated through Salesforce infrastructure. The below steps will fail if you have not waited for it. If you experience failure with the below after 1 hour has lapsed, please contact our support team.
2. Retrieve the client id and client secret
- Within Salesforce, open Platform Tools > Apps > Connected Apps > Manage Connected Apps.
- Locate the app you just set up, and click View.
- Within the app details, click Manage Consumer Details.
- Copy the Consumer Key and Consumer Secret. (The secret may be protected by a "click to reveal" link and/or a verification identity.)
3. Create a Salesforce connection
After the Salesforce connected app is created, create a Salesforce or Salesforce Aggregation connection in Totango using OAuth. The OAuth user holds the object permissions to your Salesforce.
We recommend creating a dedicated user for this integration, which has the desired object access permissions (e.g., the user can access Account object but not Contact object).
- In Totango, click Settings from the left nav.
- Expand Data Management > Customer Data Hub.
- From the list of active connectors (left), choose CRMs.
- From the list of available connectors, hover over Salesforce or Salesforce Aggregation, and click Connect (or View Integrations).
- Enter a name and description for the connection (e.g., Acme Salesforce Production). Because you can have multiple connections with a connector (using different authentication profiles), a name and description helps you identify the connection later.
- Add the Consumer Key and Consumer Secret from the previous steps.
- Choose Production or Sandbox.
- Click Connect.
- Enter your Salesforce credentials when prompted, unless you are already connected in a different tab of the browser (e.g., the OAuth configuration will take the credentials stored in your active browser session).
You can now schedule a Salesforce integration job using the connection.
Then turn on the remaining Salesforce security controls in section 4.
4. Turn on Salesforce's required security controls
Salesforce requires extra security controls on every connected app. Salesforce flags an app without them in App Insights and on the app's Security Posture page. Totango supports all of these controls.
Use these steps for a new connected app and for a connected app you created before.
Your existing Totango connection keeps working after you turn on these controls. You do not need to install an update or connect again.
- In Salesforce, open the connected app you created for Totango. If Salesforce shows its Security Posture page, click Manage App.
- Turn on these three OAuth controls. Salesforce uses different names for them on different pages.
- Require PKCE, also named Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows.
- Rotate Refresh Token, also named Enable Refresh Token Rotation.
- Enforce Refresh Token TTL, also named Limit Idle Refresh Token Time-to-Live (TTL) to 30 Days. If Salesforce asks for a maximum lifetime, enter 90 days. Do not enter a shorter time.
- Keep Require Secret for Refresh Token Flow cleared (not checked).
- Turn on Enforce Refresh Token IP Allowlist. Add each Totango IP address for your data center from Add IP addresses for Totango to your allow list. Enter each address as its own range, with the same start and end address.
- Leave DPoP off. Salesforce needs only one of the two proof-of-possession controls. DPoP works only with a localhost or Salesforce callback URL, and Totango's callback URL is a third-party URL.
- Click Save.
- In Totango, wait for the next Salesforce sync. Check that it completes without errors.
- After a sync completes, lock the controls in Salesforce with Review Controls.
Lock the controls only after a sync completes. After you lock a control, only Salesforce Support can change it.
If a sync fails after you change these settings, check the settings above. Then reconnect in Totango: open Settings > Data Management > Customer Data Hub > CRMs, open your Salesforce connection, and click Connect. If the sync still fails, contact our support team.
FAQs
Question: Will the configured Salesforce integration jobs in Totango get impacted if there is a transition from Salesforce Classic to Salesforce Lightning (no change to backend code in SFDC)?
Answer: No, there will be no impact to the existing jobs.