Skip to main content
The Looker integration brings your governed metrics into client work. Ask how Contoso’s basket size moved after the October price change, pull the figures behind a dashboard tile into a readout, or run a new question against an Explore, and Hebno answers from Looker with each Look, dashboard and query cited. Hebno uses your LookML definitions, so a figure in a reply matches the same figure in Looker. Hebno never writes to Looker.

​
At a glance

​
Before you start

You need:
  • An owner or admin role in Hebno.
  • Your Looker instance address, for example https://northwind.cloud.looker.com.
  • A Looker user for the integration, created by a Looker admin under Admin → Users. Give it a role whose permission set and model set cover only what Hebno should read.
  • API credentials for that user. A Looker admin opens the user under Admin → Users, selects Edit Keys under API Keys, then New API Key, and copies the Client ID and Client Secret.
Hebno calls the Looker API 4.0 and runs queries with the same row limits and access filters as the Looker interface. The integration user’s role needs these permissions: Leave out permissions such as develop, deploy, save_content, schedule_look_emails and manage_models. Hebno does not need them.

​
Connect Looker

1

Allow the integration

Open Admin → Connectors → Catalogue, find Looker under Data and analytics, and set it to Allow.
2

Connect the organisation

Select Connect, enter the Looker address, Client ID and Client Secret, then select Test connection. Hebno signs in to the Looker API and lists the models and folders the integration user can read.
3

Choose teams and data areas

Under Who can use it, choose All teams or pick teams. Under Data areas, choose which models and content each team can use. See Data areas.
4

Confirm access

Access is Read only. Looker has no write actions in Hebno.
The card shows Connected with the Looker address. Members in the selected teams can use Looker in chat straight away. Members can link their own Looker account so queries run with their own Looker role, model set, user attributes and access filters.
  1. In Hebno, open Settings → Connections, find Looker and select Link your account.
  2. Sign in to Looker and select Allow.
Linking uses Looker’s OAuth sign-in for API clients. A Looker admin registers Hebno as an OAuth client app once, with the redirect URI shown on the Looker card in Admin → Connectors. When your account is linked, you see only the content and rows your Looker access allows.

​
Data areas

Data areas control what members of the allowed teams can see through the organisation connection. They apply on top of whatever the integration user can read in Looker.
Admin connector panel showing who can use it, access and data areas

An organisation connection with team access and data areas. Financial figures default to owners and admins.

To share a margin model with delivery leads, open the Looker card in Admin → Connectors, select Financial models and add the teams that should see it.
When a member has linked their own account, Hebno uses that member’s Looker permissions instead of the organisation connection. Data areas still apply, so a member never sees more through Hebno than both Looker and your Hebno settings allow.

​
What Hebno reads

Chat reply citing a Looker dashboard tile

A Looker dashboard tile attached to a chat.

For a new question, Hebno picks the Explore, fields and filters from your LookML, runs the query, and shows them with the reply so you can open the same query in Looker. Results above the row limit are cut off, and the reply says so. Reads are live. Hebno runs each query in Looker when a request needs it and does not copy results into the knowledge index. Only what a reply used is stored with the conversation as its sources.

​
Hebno reads only

Hebno does not write to Looker. It does not save Looks or dashboards, change LookML, schedule deliveries, or create alerts. Linking marks which Looker dashboards or Looks belong to an engagement, so you can ask “how are the numbers moving?” without naming the dashboard.
  1. Open the project and select Brain.
  2. Under Linked records, select Link record, then Looker.
  3. Search by dashboard or Look title and select it. Repeat for each one in the engagement.
In chats tagged to the project, Hebno starts with the linked dashboards for any figure question. See Linked records.

​
Use Looker in chat

  • Attach: open the + menu, choose Sources → Looker, and pick a Look, a dashboard, a tile or an Explore. Or type / and choose Looker.
  • Ask: name the metric, dashboard or filter in your request. For example:
    Using the Contoso pricing dashboard, which store clusters lost margin in October?
    Show average basket size by week for Contoso since 1 September, split by region, and explain the change.
    Which Explore should I use for promotion uplift, and what do its measures mean?
  • Research runs show a Checking Looker step, with a chip for each Look, dashboard and query it ran.
  • Agents can read Looker on a schedule, for example a Monday brief on the Contoso pricing dashboard. Writes an agent proposes elsewhere appear in agent approvals for review.

​
Troubleshooting