> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/domo.md).
# Domo
Set up the Domo connector in Pandium using OAuth2 client credentials so tenants can securely sync BI dashboards, data visualizations, and analytics insights.
## **Connector Overview**
Domo is a business intelligence (BI) platform that provides data visualization and analytics tools to help companies make data-driven decisions.
## **Authentication Type**
OAuth2
## **Webhook Supported**
No
## **Secrets**
* PAN\_SEC\_DOMO\_EXPIRES\_AT
* PAN\_SEC\_DOMO\_CLIENT\_ID
* PAN\_SEC\_DOMO\_EXPIRES\_IN
* PAN\_SEC\_DOMO\_CUSTOMER
* PAN\_SEC\_DOMO\_CLIENT\_SECRET
* PAN\_SEC\_DOMO\_USERID
* PAN\_SEC\_DOMO\_DOMAIN
* PAN\_SEC\_DOMO\_JTI
* PAN\_SEC\_DOMO\_TOKEN\_TYPE
* PAN\_SEC\_DOMO\_ROLE
* PAN\_SEC\_DOMO\_ACCESS\_TOKEN
* PAN\_SEC\_DOMO\_ENV
* PAN\_SEC\_DOMO\_SCOPE
## **API Client Supported**
No
## **Requirements for Provisioning**
In order to provision your connector, the following Domo information must be gathered:
* Client ID
* Client Secret
* Scope
* Scope
## **API Resources**
For more information on how to utilize the DHL API, feel free to reference the following [documentation](https://developer.domo.com/).
---
# 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.pandium.com/connectors/connectors-101/domo.md?ask=&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.
