Domo

Domo is a Business Intelligence (BI) software-as-a-service (SaaS) platform developed to help companies gather and transform raw data stored across one or more databases or repositories into focused reports, dashboards and graphs. It specializes in business intelligence tools and data visualization.

In order to integrate Domo with Relyance AI you will need a Domo Client ID and Client Secret.

In Domo:

1. Login to your Domo account.
2. Using your subdomain, go to https://developer.domo.com/
3. Click New Client from the top right-hand menu My Account.
4. Provide a name, description, and scopes (user, data) for this new API client.
5. Click Create to save this new client.
6. Copy the Client ID and Client Secret to be used in Relyance AI.

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 Domo integration card and click it to open its connections.
6. Under Authentication Method, choose Custom.
7. Paste the Client ID and Client Secret into their respective fields.

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

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 user. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. A credential rotated at the vendor is not picked up here. Client Secret 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.

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" "domo" {
  vendor = "domo"
  name   = "<your connection name>"

  auth = {
    method = "client-credentials"
    params = {
      client_id = "<client_id>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      client_secret = var.domo_client_secret
    }
    secrets_wo_version = 1
  }

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