Skip to main content
After connecting your Looker account, the following actions become available as Agent steps. Each step requires you to select a connected Looker Account from a dropdown. Profound pulls query results from Looker — rows of metrics and dimensions your analytics team has already modeled — not Looker dashboards or visualizations. Results are returned as structured data (typically JSON) that later agent steps can summarize, compare, or combine with other integrations.

​
Available actions

​
Run Look

Execute a saved Look from your Looker instance and return the result as structured data.Required inputs
  • Looker Account
  • Look — a saved Look from the selected account. The dropdown loads Looks from Looker and shows each Look’s title with its ID.
Optional inputs
  • Result Format — the format returned by Looker. Defaults to json_bi, which is recommended for downstream agent steps.
  • Row Limit — maximum number of rows to return.
Output
  • Look Results — a JSON value containing the returned Looker result.
Tip: Use Run Look when the query already exists as a saved Look in Looker. This keeps business logic governed in Looker and is the safest option for recurring agent automations.

​
What data is available

Query results depend on the Look or Explore you run. In general, Looker returns the fields defined in your LookML model: Profound returns the raw query result as structured data (typically JSON). Your agent or sheet decides what to do with it — summarize it, compare periods, or pass rows to another step.

​
Supported result formats

Both actions support multiple Looker result formats. json_bi is the default and recommended format for agent workflows because it returns structured JSON that downstream steps can parse reliably. Other supported formats: json, csv, txt, html, md, xlsx, sql, png, and jpg. Use non-JSON formats only when a later step explicitly needs that output type.

​
Limits

  • Run Inline Query defaults to 500 rows and supports up to 5,000 rows per run.
  • Run Look supports an optional row limit override up to 5,000 rows.
  • The connected Looker user’s permissions still apply — Profound cannot return data the API user cannot access.

​
Choosing an action

​
Common use cases

  • Pull a saved traffic or revenue Look into a weekly summary agent
  • Fetch governed KPIs from Looker and pass them to a content-generation step
  • Run dynamic inline queries with date windows that change based on agent inputs
  • Combine Looker metrics with data from other integrations in a single agent
  • Import a saved Look into a Sheet to analyze metrics alongside agent-generated columns

​
Best practices

  • Prefer json_bi for downstream agent steps because it returns structured data
  • Start with a saved Look when possible; use inline queries only when the agent needs dynamic logic
  • Keep row limits focused so later steps receive only the data they need
  • Make sure the connected Looker user has access to every model, Explore, field, and Look used by the agent

​
Common errors

The Look dropdown depends on the selected Looker account. Choose a Looker Account before selecting a saved Look.
The connected Looker user may not have access to any saved Looks, or the Looks may be in folders the user cannot access.
Inline queries must use Looker model, Explore, and field names exactly as they exist in Looker.
Profound uses the connected Looker API user. Update that user’s Looker role, model set, or folder permissions if the agent cannot access the requested data.