Totango

Totango is an agile customer success platform. It helps manage customer relationships by simplifying the complexities of customer success through customer data, active monitoring customer health changes and driving engagements.

In order to integrate Totango with Relyance AI you will need an API Token and Account ID.

In Totango:

1. Login to your Totango account.
2. In the top right-hand corner click on your Account profile menu and select Edit Profile.
3. Click on the Integrations tab in the dialog.
4. Click on GENERATE NEW TOKEN.
5. Copy this token as your API Token for Relyance.
6. Now you'll need to specify which portfolio to retrieve by using the Account ID.
7. Either go into a report that lists the Account ID or open the Account page and grab it from the URL. or

In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the Settings Menu in the bottom left-hand side.
3. Select Integrations.
4. Click on the Vendor Integration tab.
5. Find the Totango integration card and click it to open its connections.
6. Under Authentication Method, choose Custom.
7. Paste the API Token and Account ID into their respective fields.

The Authentication step asks for:

• API Token Key: required; held as a secret.
• Enter an Account ID to retrieve its touchpoints: required.

9. Click Authenticate.
10. At this point, you should see the following result on the Vendor Integrations page:

11. Congratulations, you are now connected to Totango.

Notes:

If you wish to include more portfolios in this integration, you can add multiple integration links at the top of the integration by clicking on the page icon with the plus.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. A credential rotated at the vendor is not picked up here. API Token Key is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
2. Check the address fields before suspecting the credentials. Enter an Account ID to retrieve its touchpoints identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

resource "relyance_integration_connection" "totango" {
  vendor = "totango"
  name   = "<your connection name>"

  auth = {
    method = "access-token"
    params = {
      account_id = "<account_id>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      app-token = var.totango_app_token
    }
    secrets_wo_version = 1
  }

  scans = { "property-inspection" = { enabled = true } }
}