Requesting a report
Press Request report and describe what you want to understand:
The report is created immediately and opens to its own page. The body starts
empty — you (or, later, an automated job) fill in the analysis.
Generation status
Every report carries a generation status shown as a badge on the list and detail pages:
Automated, AI-generated reports are not available yet, so a requested report
sits in Waiting for generation. You can write the analysis by hand in the
editor in the meantime — the body is fully editable regardless of status.
Creating and editing from chat or the API
You don’t have to use the Request report button. Ask Zelto in chat — “create a report titled … about …” — and it proposes the report for you to confirm before it’s saved. The same actions are available to scripts and external agents over the MCP server as thecreate_report and update_report
tools (with list_reports / get_report to find and read existing ones), so an
automated workflow can file a report or update its title, request, body, or
status programmatically.
Anatomy of a report
Data widgets
A data widget turns a report from a static write-up into a live dashboard. It runs a query against your analytics store and renders the result as a table or chart that re-runs every time the report is opened, so the numbers stay current as new calls come in. In the report editor, type/ and choose Data widget, then fill in:
Press Run to execute it. Use the refresh button in the widget header to
re-run on demand, the pencil to change the query, and the chart/table toggle to
switch views. Results are capped at the first 1,000 rows.
Data widgets are read-only and scoped to your organization: every query is
automatically restricted to your org’s rows on the analytics tables, and only
SELECT / WITH / DESCRIBE / EXPLAIN / SHOW statements are allowed —
writes and cross-organization access are rejected. The same querying capability
is available conversationally through Ask Zelto and over the
MCP server.

