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

# Looker

The Looker integration connects your Looker environment directly to Harmony, bringing license and usage data into the same place as your other SaaS applications. Once configured, Harmony automatically fetches key information from Looker so your team can monitor adoption, track spending, and make informed decisions about your Looker subscription - without switching between tools.

### What Harmony Collects from Looker

After you connect Looker, Harmony surfaces the following data from your environment:

* **License type** - see which Looker license tier your organization is on, giving you a clear picture of what you are entitled to use
* **Login trends** - track how frequently users are accessing Looker over time, so you can identify active users, spot drop-offs, and understand overall adoption
* **Cost data** - where available, Harmony pulls cost information associated with your Looker usage, helping you tie spend to actual utilization

This data appears alongside your other connected applications in Harmony, making it straightforward to compare Looker adoption and spend against the rest of your SaaS portfolio.

### Prerequisites

Before setting up the Looker integration, make sure you have the following:

* A Looker account with admin-level access
* Permission to create and manage API credentials in Looker
* Access to the Harmony Integrations settings in your organization

### Connecting Looker to Harmony

To set up the Looker integration:

1. In Harmony, navigate to **Integrations** and select **SaaS Applications**.
2. Locate **Looker** in the list of available integrations and click **Connect**.
3. When prompted, enter your Looker API credentials. You can generate these from the **Admin** panel in Looker under **Users** - select your admin user and create a new API key.
4. Provide your Looker instance URL so Harmony knows which environment to connect to.
5. Click **Save** to complete the connection.

Once connected, Harmony will begin fetching data from your Looker environment. Initial data may take a short time to appear depending on the size of your Looker instance.

### Viewing Looker Data in Harmony

After the integration is active, you can find your Looker data in the Harmony dashboard under your connected SaaS applications. From there you can:

* Review your current license tier and compare it against actual usage
* Examine login trend charts to understand how adoption has changed over time
* Check cost data to evaluate whether your current Looker plan aligns with the value your team is getting from the tool

Use this information alongside data from your other integrated applications to identify underutilized licenses, optimize spend, or build a case for scaling up or down your Looker subscription.

### Disconnecting Looker

To remove the Looker integration:

1. In Harmony, navigate to **Integrations** and select **SaaS Applications**.
2. Find **Looker** in your list of connected applications.
3. Click **Disconnect** and confirm the action.

Harmony will stop fetching data from Looker. Any historical data already collected will remain available in Harmony until it is manually cleared.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.harmony.io/integrations/saas-applications/looker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.