Nexra
Start in the sandbox
All connectors

Looker

Analytics, databases & data platforms

Bring your business data together in Looker, and act on it in the apps your team already uses.

13 ways to read, 2 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Looker with Nexra

Connected, approved, proven.

The things teams do most with Looker, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Save a queryqueries.createApproval by rule
  • Send a schedule nowscheduled_plan_runs.sendApproval by rule
  • Run a saved Looklook_results.listRead

Example flow

  1. Looker · Run a saved Looklook_results.listDone
  2. Looker · Save a queryqueries.createMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Looker.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Looker
  • Looker's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Looker: find and run saved Looks, dashboards and queries, run Explore queries without SQL, list models, folders and schedules, save queries and send a schedule now.

Google Cloud API docs
Source actions
13
Destination actions
2
Data types
11

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

current user1
  • Check the connected Looker userSource

    Reads the Looker user whose API key the connection uses.

dashboards2
  • Get a dashboard and its tilesSource

    Reads one dashboard with its tiles and the Look or query behind each tile.

  • Find dashboardsSource

    Lists dashboards, optionally by title or folder.

explores1
  • Get an Explore's fieldsSource

    Lists the dimensions and measures you can pick in an Explore.

folders1
  • Find foldersSource

    Lists folders, optionally by name or parent folder.

look results1
  • Run a saved LookSource

    Runs a saved Look and returns its rows (capped).

lookml models1
  • List models and ExploresSource

    Lists the LookML models you can query and the Explores in each.

looks2
  • Get a saved LookSource

    Reads one Look: its title, folder, owner and the query behind it.

  • Find saved LooksSource

    Lists saved Looks (reports), optionally by title or folder, newest change first.

queries1
  • Save a queryDestinationNot retried automaticallyApproval before production

    Saves an Explore query (fields, filters, sorting) so it can be run again by its ID or opened in Looker. No SQL is written.

query results2
  • Run a saved querySource

    Runs a saved Looker query by its ID (for example a dashboard tile's) and returns its rows.

  • Run a query on an ExploreSource

    Picks fields, filters and sorting from an Explore and returns the rows, without saving anything. No SQL is written.

scheduled plan runs1
  • Send a schedule nowDestinationNot retried automaticallyApproval before production

    Delivers an existing schedule once, right now, to the recipients already saved on it. The schedule itself is not changed.

scheduled plans2
  • Check a schedule's last runSource

    Reads one schedule, including when it last ran and the status of that run.

  • List schedulesSource

    Lists scheduled deliveries of Looks and dashboards with when each last ran and its status.

Access and limits

Authentication
Looker API key (client ID and client secret)
Plans and access
Any Looker (original) instance or Looker (Google Cloud core) instance with API access. Looker (Google Cloud core) editions include different monthly API call allowances. The API key acts as the Looker user it belongs to: it sees only the content, models and schedules that user can. Looker (Google Cloud core) needs an admin to enable API keys for the user first.
Test environment
Looker has no separate sandbox. Create a dedicated API user with a restricted role (for example Viewer on a test folder) on your instance, or use a development/staging instance if you have one.
Rate limits
Looker returns 429 when calls come too fast and limits each user to 15 running queries at a time (queued queries wait up to 10 minutes). Sending schedules is rate-limited separately. Looker (Google Cloud core) editions also cap monthly API calls. Nexra backs off and honours Retry-After.
Pagination
Search reads (Looks, dashboards, folders, models) use limit and offset. Query and Look runs return one capped page of rows.
Provider events
Looker can deliver a schedule or alert to a webhook address you configure in Looker; there is no change-event webhook for content. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Runs return at most 5000 rows; Nexra never asks Looker for unlimited results.
  • Only Explore queries built from model, Explore, fields, filters and sorts are offered. SQL Runner and custom SQL fields are not offered.
  • Looker's search reads have no 'changed since' filter, so there is no incremental read; use the Looks list sorted by most recently changed, or deliver a Looker schedule to a webhook.
  • Only Looker addresses on the standard HTTPS port (443) under looker.com or looker.app are accepted. Instances that still use port 19999 must set an API Host URL on port 443 (Admin → Platform → API); custom domains and customer-hosted Looker are not supported.
  • Send a schedule now delivers to the schedule's saved recipients only; it is approval-gated like other message sends and never repeated automatically.
  • Intentionally excluded: SQL Runner, deleting or editing Looks, dashboards, folders and schedules, creating schedules or alerts, user, role, group and permission management, LookML projects and Git, connections and other admin settings.

Developer reference

  1. Create the Google Cloud credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Looker, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Google Cloud docsAPI referenceGoogle Cloud docsAuthenticationGoogle Cloud docsRate limits

Machine-readable detail: GET /api/public/connect/connectors/looker and the Connections API.