Skip to main content
A domo database entry can be added by specifying type: domo in your ~/.config/oxy/config.yml file.
This integration allows Oxygen to query datasets hosted in Domo directly through its API, using your developer token and dataset ID.

Required fields

Each domo entry requires the following fields:
  • dataset_id – The unique ID of your Domo dataset.
  • developer_token_var – The name of the environment variable that stores your Domo Developer Token.
  • instance – The Domo instance name (e.g., oxygen-ai).
  • type – Must be set to domo.

Authentication

Oxygen connects to Domo using a Developer Token.
You should store this token as an environment variable and reference it via developer_token_var.
For example, if your variable is DOMO_DEVELOPER_TOKEN, make sure it’s exported in your environment before running any queries:

Sample config entry

Semantic model support

Domo databases support the semantic model through Postgres compatibility. When defining views in your semantic model, reference your Domo datasource and the dataset_id will automatically be used as the table identifier:
Important notes for Domo semantic model:
  • For column identifiers with spaces or special characters, wrap in double quotes and backticks: "Calories (kcal)"
  • Date/time types are not supported - use type: string or type: number for date/time columns instead of type: date or type: datetime
  • Postgres syntax is assumed - certain Domo-specific SQL functions may not work as Cube generates Postgres-compatible SQL

Usage notes

  • Oxygen retrieves data from the Domo dataset defined by dataset_id.
  • Your developer token must have API access to this dataset.
  • Queries are executed via the Domo API and streamed into Oxygen’s runtime for downstream processing or caching.
  • For semantic model queries, Oxygen automatically maps Domo to Postgres compatibility and uses the dataset_id as the table identifier.