> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/sources/business-intelligence/looker-integration/troubleshooting-looker-integration.md).

# Troubleshooting Looker integration

### "Invalid Looker Credential" when trying to connect Looker

To troubleshoot this issue, follow the steps:

1. Verify you correctly typed the Client ID and Client Secret in the "Configure Looker Integration" pop-up window.
2. If you're using IP whitelisting on your Looker instance, make sure each of Euno's public IP addresses is one of the rules in the whitelist. Follow Looker's guide [here](https://cloud.google.com/looker/docs/admin-panel-server-ip-allowlist#adding_a_new_rule). Add a rule for each address, with **Type** set to IP Address:
   * `35.224.29.172`
   * `44.218.99.77`
   * `3.214.77.39`
3. Confirm the API key user has permission to query Looker's `system__activity` model (required during source validation). The Admin role satisfies this requirement; for custom roles, include the `see_system_activity` permission. See [Using a custom Looker role](/sources/business-intelligence/looker-integration/using-a-custom-looker-role.md).

### Integration saves but LookML resources are missing

If Looks, Tiles, and Dashboards appear but views, explores, and lineage are missing:

1. Link a Git account with read access to your LookML repositories. See [GitHub](/setup-configuration/linked-accounts/github-integration.md) or [GitLab](/setup-configuration/linked-accounts/gitlab-integration.md).
2. Check **LookML Project Includes** and **LookML Model Includes** in Advanced Settings—overly narrow patterns can exclude projects or models.
3. If **Crawl LookML Only** is enabled, application-layer content (Looks, Tiles, Dashboards) is intentionally skipped.

### Users or groups are not observed

1. Confirm **Observe users** and **Observe groups** are enabled in Advanced Settings (they are enabled by default).
2. For custom Looker roles, ensure the permission set includes `see_users` (required for user and group observation). See [Using a custom Looker role](/sources/business-intelligence/looker-integration/using-a-custom-looker-role.md).


---

# 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.euno.ai/sources/business-intelligence/looker-integration/troubleshooting-looker-integration.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.