Looker
Lets agents run Looks and explores, read dashboards and LookML models, and manage content through the Looker API.
Connect it with: API key. Looker's own documentation: https://cloud.google.com/looker/docs/api-auth.
What agents can do
Connect Looker so the agents working your tasks can reach it. With it connected, they can:
- Run a Look, an explore query or inline SQL through SQL Runner, and read the results as JSON or CSV.
- List and read dashboards, Looks and folders, and create or update them.
- Read LookML projects and models, and validate LookML on a development branch.
- Schedule deliveries and check the state of existing schedules.
Before you start
- A Looker (Google Cloud core) or Looker (original) instance, and its address.
- A Looker admin who creates the API keys: on Looker (original), Admin > Users > choose a user (a dedicated service user is best) > Edit > Edit Keys > New API Key; on Looker (Google Cloud core), the admin enables API keys on Admin > Users and the user requests them on their Account page.
- A role on that user that allows what agents should do; the API acts with exactly the user's permissions.
- For a customer-hosted instance, the API port (19999 by default) reachable from the internet.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Looker
Jaah connects to Looker with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- Instance URL: The address you open Looker at, such as https://yourcompany.cloud.looker.com. A customer-hosted instance whose API runs on port 19999 takes that port: https://looker.yourcompany.com:19999.
- Client ID: Looker (original): Admin > Users > the API user > Edit > Edit Keys > New API Key. Looker (Google Cloud core): an admin turns on API key management on Admin > Users, then the user opens their Account page > API keys > Request new API key. Copy the Client ID.
- Client secret: Shown beside the Client ID on the same Edit User API Keys page; select Reveal to copy it.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Looker card.
- Name the secret and choose who can use it.
- Fill in Instance URL, Client ID, Client secret.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Looker with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah first signs in at POST <Instance URL>/api/4.0/login with the client ID and secret, then calls Looker's API once with the token it got back (GET <Instance URL>/api/4.0/user), and shows who it answered as, or which value Looker refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: base_url, client_id, client_secret.
Tell the agent in your task description which secret to use, for example “use the Looker secret org/looker”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Looker once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Looker's side too, revoke or delete the key at Looker.
Limitations
- The API acts as the user the keys belong to; agents cannot see content that user cannot see.
- Looker issues an API session token that lasts one hour; Jaah's Test logs in fresh each time, and agents log in with the stored keys when they start.
- A Looker instance reachable only on a private network cannot be tested or used from Jaah.
- Agents can do only what the connected Looker account allows.
Troubleshooting
Test says Looker rejected the client ID and client secret (404)
Looker answers a wrong key pair with 404 Not found on purpose, and so does a login sent to the wrong address. Copy the Client ID again from the user's API keys, reveal and copy the Client secret, and check the user is not disabled. If the keys are right, the API is on another host or port: ask your Looker admin for the API Host URL under Admin > Platform > API, and use it as the Instance URL (a customer-hosted instance usually adds :19999).
Test says Looker cannot be reached at that address
Check the Instance URL is the address you open Looker at, starts with https://, and for a customer-hosted instance includes the API port (:19999). Instances on a private network are not reachable from Jaah.
Test says Looker rejected the access token it issued (403)
The keys are valid but Looker refused the session they opened. Check on Admin > Users that the user is not disabled or locked, and that its role is not empty.
Still stuck? Select Test and read the result: it names the value Looker refused and the status it answered.
FAQ
Should I use my own API keys?
A dedicated service user is better: its role limits what agents can do, and its keys keep working when people change roles or leave.
Does this connect to Looker Studio?
No. Looker Studio (formerly Data Studio) is a different product with no API keys; this connects to Looker instances.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Looker account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.