> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/domo.md).

# Domo

Integration with Domo for browsing DataSets and reading their metadata and column schema.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Domo      | Credentials    |

#### Domo

Connect to Domo with an API client's Client ID and Client Secret (developer.domo.com/new-client) to browse DataSets and read their metadata and schema. Grant the client the 'Data' scope. Access tokens are short-lived (1 hour) and minted per request, making this suitable for unattended workflows.

**Set up in Domo**

1. Prepare the Domo account or service that the workflow will access. Grant access to the required resources and operations.
2. **Client ID:** The Client ID of a Domo API client. Create one at developer.domo.com/new-client and grant it the 'Data' scope.
3. **Client Secret:** The Client Secret shown when the API client was created. Grant the client only the 'Data' scope, which is all the DataSet actions need.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Domo**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                                                                                                        |
| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Client ID     | Yes      | The Client ID of a Domo API client. Create one at developer.domo.com/new-client and grant it the 'Data' scope. [Provider instructions](https://developer.domo.com/portal/1845fc11bbe5d-api-authentication).                          |
| Client Secret | Yes      | The Client Secret shown when the API client was created. Grant the client only the 'Data' scope, which is all the DataSet actions need. [Provider instructions](https://developer.domo.com/portal/1845fc11bbe5d-api-authentication). |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Domo** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### List DataSets

List DataSets in Domo.

**Inputs**

| Field         | Type            | Required | Description                                                                                                                                                 |
| ------------- | --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name Contains | string          | No       | Only return DataSets whose name contains this text. Leave empty to return every DataSet.                                                                    |
| Sort By       | select (string) | No       | The order Domo returns the DataSets in. Available values: Name (A-Z), Name (Z-A), Last viewed, Last updated, Created, Card count, Error state, Data source. |
| Max Results   | integer         | No       | Maximum number of DataSets to return (1-1000). Pages are fetched automatically up to this many.                                                             |

**Outputs**

| Field                   | Type          | Description                                                                                        |
| ----------------------- | ------------- | -------------------------------------------------------------------------------------------------- |
| DataSets                | dict\_array   | The DataSets that matched.                                                                         |
| DataSet IDs             | string\_array | IDs of the returned DataSets.                                                                      |
| Count                   | integer       | How many DataSets were returned.                                                                   |
| More DataSets Available | boolean       | True when more DataSets matched than were returned, so the list above is only part of the picture. |

#### Get DataSet

Get a DataSet's metadata and column schema.

**Inputs**

| Field   | Type            | Required | Description                                                                                           |
| ------- | --------------- | -------- | ----------------------------------------------------------------------------------------------------- |
| DataSet | select (string) | Yes      | The DataSet to retrieve. Pick one, or pass an ID directly. Options load from the selected connection. |

**Outputs**

| Field        | Type          | Description                                              |
| ------------ | ------------- | -------------------------------------------------------- |
| DataSet      | dict          | The full DataSet object Domo returned.                   |
| DataSet ID   | string        | The DataSet's ID.                                        |
| Name         | string        | The DataSet's name.                                      |
| Row Count    | integer       | How many rows the DataSet holds.                         |
| Column Count | integer       | How many columns the DataSet holds.                      |
| Columns      | object\_array | The DataSet's columns, with each column's name and type. |
| Updated At   | string        | When the DataSet was last updated.                       |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/domo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
