ThoughtSpot

ThoughtSpot is a web-based business intelligence and big data analytics platform that helps you explore, analyze and share real-time business analytics data easily. It is designed to help organizations in finance, manufacturing, communications, healthcare, and other sectors analyze data in real-time and receive automated insights using artificial intelligence (AI).

In order to integrate ThoughtSpot with Relyance AI you will need a ThoughtSpot Subdomain, Username, and Password.

In ThoughtSpot:

1. Login to your ThoughtSpot account.
2. You will use the same Username and Password in Relyance.
3. Note the Subdomain in your browser URL bar:

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 ThoughtSpot integration card and click it to open its connections.
6. Under Authentication Method, choose Custom.
7. Paste the Subdomain, Username, and Password into their respective fields.

The Authentication step asks for:

• Subdomain: required; held as a secret.
• Username: required.
• Password: required; held as a secret.

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 ThoughtSpot.

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. Subdomain and Password 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.
2. 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.

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

  auth = {
    method = "username-password"
    params = {
      username = "<username>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      subdomain = var.thoughtspot_subdomain
      password = var.thoughtspot_password
    }
    secrets_wo_version = 1
  }

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