Gainsight

Gainsight is a customer success platform that helps businesses drive retention and growth by tracking customer health, automating workflows, and analyzing usage data.

Gainsight can be connected with Relyance AI using either:

• Custom - Subdomain and API Access Key
• OAuth2 / App Token - Subdomain, Client ID, and Client Secret

Generating an API Access Key in Gainsight:

1. Login to your GainSight account.
2. Once logged in, you should see a URL that looks like this: https://demo-relyance.us2.gainsightcloud.com/ https://demo-relyance.us2.gainsightcloud.com/

3. In the above example “demo-relyance.us2” is what you need to copy. This is your GainSight Subdomain. 4. To generate your API Access Key: 4.1 Navigate to Administration> Integrations> Connectors 2.0

4.2. Click on the Create Connection button

4.3. On the Connector drop-down choose Gainsight API, click on Generate Access Key and copy the result. This will be your API Access Key.

In the Relyance AI application:

1. Login to your Relyance AI account.
2. Navigate to the Settings Menu in the bottom left-hand side.
3. Select Integrations.
4. Search for the Gainsight tile and click it to open its connections.
5. Choose Custom under Authentication Method. under the Create Connection section.
6. Paste the Gainsight Subdomain and the API Access Key into their respective fields.
7. Click Authenticate.
8. Congratulations! You are now connected to Gainsight and should see the following result on the Vendor Integrations page.

Creating an OAuth2 app in Gainsight:

1. Login to your GainSight account.
2. Once logged in, you should see a URL that looks like this: https://demo-relyance.us2.gainsightcloud.com/ https://demo-relyance.us2.gainsightcloud.com/

3. In the above example “demo-relyance.us2” is what you need to copy. This is your GainSight Subdomain. 4. Creating an OAuth2 app in Gainsight: 4.1 Navigate to Administration> Users and Permissions> User Management 4.2 Once on this page, Click on Authentication. 4.3 Click OAuth Applications >Add Application. 4.4 Here give your OAuth application a name, adjust the permissions scope (Read, Read/Write), and enter in the URL: https://root.relyance.ai/api/oauth2. 4.5 Click Add Application to finish creating an OAuth application.

In the Relyance AI application:

1. Login to your Relyance AI account.
2. Navigate to the Settings Menu in the bottom left-hand side.
3. Select Integrations.
4. Search for the Gainsight tile and click it to open its connections.
5. Select the OAuth2 / App Token under Authentication Method.
6. Enter in your Subdomain, Client ID, and Client Secret that was created in the "Creating an OAuth2 app in Gainsight" section above.
7. Click the Authenticate button.
8. Once the connection is successfully established, then the Connection Summary can be reviewed.

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 feature you enabled returns nothing. Some scopes belong to a feature rather than to the connection: Data subject requests needs Default. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. Authorised, then empty. The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
3. A credential rotated at the vendor is not picked up here. Subdomain, API Access Key and Client Secret are 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.
4. Check the address fields before suspecting the credentials. Subdomain 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.

Access key

resource "relyance_integration_connection" "gainsight_0" {
  vendor = "gainsight"
  name   = "<your connection name>"

  auth = {
    method = "access-key"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      SUBDOMAIN = var.gainsight_subdomain
      API_ACCESS_KEY = var.gainsight_api_access_key
    }
    secrets_wo_version = 1
  }

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

OAuth (browser authorization)

The OAuth (browser authorization) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example gainsight/<connection_id>) or reading it with the relyance_integration_connection data source.