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

# Domo

Connect & Ingest data from Domo

Domo is a cloud-based business intelligence (BI) platform that transforms the way organizations use data. The Sling Domo connector extracts metadata from the Domo Platform API, including datasets, users, groups, pages (dashboards), activity logs, streams, accounts, and projects.

{% hint style="success" %}
**CLI Pro Required**: APIs require a [CLI Pro token](/sling-cli/cli-pro.md) or [Platform Plan](/sling-platform/platform.md).
{% endhint %}

## Setup

The following credentials and inputs are accepted:

**Secrets:**

* `client_id` **(required)** -> Your Domo API Client ID
* `client_secret` **(required)** -> Your Domo API Client Secret
* `scopes` (optional) -> Space-separated OAuth scopes (default: `data user dashboard audit account workflow`)

**Inputs:**

* `anchor_date` (optional) -> Starting date for incremental data extraction (default: 1 year ago). Format: `YYYY-MM-DDTHH:MM:SSZ`

### Getting Your API Credentials

1. Log in to your [Domo instance](https://www.domo.com/login) as an admin
2. Navigate to **Admin** > **Authentication** > **API Clients**
3. Click **CREATE**
4. Enter a name (e.g., `Sling`) and description
5. Select the required scopes: **Account**, **Audit**, **Data**, **Dashboard**, **User**, **Workflow**
6. Click **CREATE**
7. Copy the **Client ID** and **Client Secret** immediately (the secret is only shown once)

{% hint style="warning" %}
**Important:** You need admin access to your Domo instance to create API clients. The Client Secret is only displayed once during creation — save it securely.
{% endhint %}

### Using `sling conns`

{% code overflow="wrap" %}

```bash
sling conns set DOMO type=api spec=domo secrets='{ client_id: "${DOMO_CLIENT_ID}", client_secret: "${DOMO_CLIENT_SECRET}" }'
```

{% endcode %}

### Environment Variable

See [here](https://docs.slingdata.io/connections/api-connections/pages/eAdVs2BHCgdr6RS8GoJC#dot-env-file-.env.sling) to learn more about the `.env.sling` file.

{% code overflow="wrap" %}

```bash
export DOMO='{ type: api, spec: domo, secrets: { client_id: "your_client_id", client_secret: "your_client_secret" } }'
```

{% endcode %}

### Sling Env File YAML

See [here](https://docs.slingdata.io/connections/api-connections/pages/eAdVs2BHCgdr6RS8GoJC#sling-env-file-env.yaml) to learn more about the sling `env.yaml` file.

```yaml
connections:
  DOMO:
    type: api
    spec: domo
    secrets:
      client_id: ${DOMO_CLIENT_ID}
      client_secret: ${DOMO_CLIENT_SECRET}
```

## Replication

Here's an example replication configuration to sync Domo data to a PostgreSQL database:

```yaml
source: DOMO
target: MY_POSTGRES

defaults:
  mode: full-refresh
  object: public.domo_{stream_name}

streams:
  # sync all endpoints
  '*':

  # incremental activity log
  activity_log:
    mode: incremental
```

This replication syncs all Domo endpoints to PostgreSQL using full-refresh mode, with the activity log using incremental mode for efficient ongoing syncs.

## Endpoints

| Endpoint       | Description                                           | Incremental |
| -------------- | ----------------------------------------------------- | ----------- |
| `datasets`     | DataSet metadata (id, name, owner, schema, row count) | No          |
| `users`        | User profiles (name, email, role, department)         | No          |
| `groups`       | Groups and their member counts                        | No          |
| `pages`        | Pages/dashboards and their structure                  | No          |
| `activity_log` | Audit log of all actions in the instance              | Yes         |
| `streams`      | Data stream configurations and execution history      | No          |
| `accounts`     | Connector account configurations                      | No          |
| `projects`     | Projects and task management data                     | No          |

## Incremental Sync

The `activity_log` endpoint supports incremental sync. Sling reads the latest `time` value from the target table and sends it as the `start` parameter. Each run fetches only the entries after that time. The first run fetches the last year of entries, or the entries since the `anchor_date` input.

The Domo activity log has no unique ID for each entry. Do not set a primary key for this endpoint.

## OAuth Scopes

The Domo API uses OAuth 2.0 with client credentials. Each scope controls access to different API resources:

| Scope       | Required For      |
| ----------- | ----------------- |
| `data`      | datasets, streams |
| `user`      | users, groups     |
| `dashboard` | pages             |
| `audit`     | activity\_log     |
| `account`   | accounts          |
| `workflow`  | projects          |

If you are facing issues connecting, please reach out to us at <support@slingdata.io>, on [discord](https://discord.gg/q5xtaSNDvp) or open a Github Issue [here](https://github.com/slingdata-io/sling-cli/issues).


---

# 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.slingdata.io/connections/api-connections/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.
