Configure a connector for a virtual collection

Who can use this feature?

You can create a virtual collection connector for any application that supports OAuth2 application integration and query based endpoints.

Configure OAuth settings

Some data sources require you to configure OAuth settings in the source application prior to setting up a connection in Totango. Refer to the following steps for these common applications.

Salesforce

If you already have a Totango connection configured with Salesforce, you can use the same client ID and client secret. If you do not have a Salesforce connection configured, follow these steps to configure an OAuth connected app:

  1. Create a connected app in Salesforce
  2. Retrieve the client ID and client secret

Jira

If you already have a Totango connection configured for Jira or Jira Service Management (formerly Jira Service Desk), you can use the same client ID and client secret. If you do not have a Jira connection configured, follow these steps to configure an OAuth application:

  1. Create a connection app in Jira 

Zendesk

Follow these steps to configure an OAuth application in Zendesk: Using OAuth with your application.

    • Client Name: Choose a name for your app. This is the name that users will see when asked to grant access to your application, and when they check the list of third-party apps that have access to their Zendesk.
    • Unique Identifier: The field is auto-populated.
    • Redirect URLs: Enter the value: https://app.totango.com/auth/das/callback
    • Secret: Generate a secret key (make sure you save this key)

Create a new virtual connection in Totango

  1. In Totango, click Settings from the left nav.
  2. Expand Data Management > Customer Data Hub.
  3. From the list of active connectors (left), choose APIs.
  4. From the list of available connectors, hover over Virtual Collection, and click Connect (or View Integrations).
    mceclip0.png

    You can also initiate a new virtual collection connector from the Settings window of an account profile.
    mceclip2.png

  5. Enter a title for the widget.
  6. From the Connection drop-down, click +Create new or update existing.
  7. Enter a name and description for the connection. Because you can have multiple connections with a connector (using different authentication profiles), a name and description helps you identify the connection later.
  8. From the Type drop-down, choose OAuth2.
    mceclip1.png
  9. Additional fields appear. Add the required connection details (see below).
  10. Click Test Connection. A new window opens to enter your authentication credentials.
  11. When successful, click Add Connection.

You can now finish configuring the widget.

Connection details for common applications

Salesforce (Production)

  • Type: OAuth2
  • Client ID: Consumer Key from Salesforce app 
  • Client Secret: Consumer Secret from Salesforce App 
  • Scope: OAuth Scopes from Salesforce App
  • Authorization Endpoint: https://login.salesforce.com/services/oauth2/authorize
  • Token Endpoint: https://login.salesforce.com/services/oauth2/token
  • Redirect URL: https://app.totango.com/auth/das/callback 

Salesforce (Sandbox)

  • Type: OAuth2
  • Client ID: Consumer Key from SFDC App
  • Client Secret: Consumer Secret from SFDC App
  • Scope: OAuth Scopes from SFDC App
  • Authorization Endpoint: https://test.salesforce.com/services/oauth2/authorize
  • Token Endpoint: https://test.salesforce.com/services/oauth2/token
  • Redirect URL: https://app.totango.com/auth/das/callback 

If you are using a custom domain and are preventing login from test.salesforce.com or login.salesforce.com, your Token Endpoint and Authorization Endpoint should reflect the correct domain.

Zendesk

  • Type: OAuth2
  • client_id: Client Name from Zendesk OAuth client Client Name
  • client_secret: Secret from Zendesk OAuth client
  • scope: read
  • Authorization Endpoint : https://[your_sub_domain].zendesk.com/oauth/authorizations/new
  • Token Endpoint : https://[your_sub_domain].zendesk.com/oauth/tokens
  • Redirect URI: https://app.totango.com/auth/das/callback

Jira Service Desk

  • Type: OAuth2
  • client_id: Client ID from Jira Connected App details
  • client_secret: Secret from Jira Connected App details
  • scope: read:jira-work
  • Authorization Endpoint : https://auth.atlassian.com/authorize?audience=api.atlassian.com&prompt=consent
  • Token Endpoint : https://auth.atlassian.com/oauth/token
  • Redirect URI: https://app.totango.com/auth/das/callback

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request