Reports

Markdown answers with charts, shareable by link, and scheduled to re-run themselves.

Updated 2026-04-17

A Report is the most common way to keep an answer. It’s a Markdown page with charts baked in, a stable shareable link, and an optional schedule.

Use a Report when someone (you, a teammate, or a client) will read the answer later. If they want to click and explore, you probably want a Dashboard instead.

Creating a Report

From the Keep bar under any Agent answer, click + Save as Report. No modal, no form. The Report slides into the right panel, the Agent fills it from the answer, and you can start editing immediately.

Report · weekly recap
Last week's signups — 2026-04-14 to 2026-04-20
Saved just now · re-runs every Monday 09:00 · shareable by link
Signups
184
WoW
+12%
Anomalies
1

Growth is carried by organic and Product Hunt referrals. Paid social is flat. Direct is down 6% but still the smallest source, so it doesn't move the overall picture.

Flag: Tuesday mid-day dip isolated to mobile web. Likely a referrer / landing-page issue, not a demand change. Watch for recurrence next week.

· A saved Report — Markdown + KPIs + charts, with a schedule attached

The initial Report contains three sections by default:

  • KPI strip — three or four single-number answers pulled from your analysis.
  • Narration — the Agent’s interpretation, in Markdown.
  • Charts and tables — the visuals that supported the answer.

You can rearrange, delete, or add sections. The Report is fully editable Markdown — add headings, bullet lists, embedded images, anything you’d put in a doc.

Anatomy of a Report

Every Report has:

  • Title and kicker — a category tag (e.g., “Weekly recap”) and a title.
  • Body — Markdown with inline data blocks.
  • Data blocks — named queries or Python scripts that produce the tables / charts / KPIs shown. Each block re-runs when the Report re-runs.
  • Metadata — author, last run, next run, share link, version history.

You can have as many data blocks as you want. Each is inspectable (click the data, see the query) and editable.

Scheduling

Click Schedule in the Report toolbar. Pick a cadence:

  • Weekly (default: Monday 09:00 in your workspace timezone).
  • Daily (default: 08:00).
  • Monthly (default: first business day, 09:00).
  • Custom cron — any standard cron expression.

On each scheduled run, Tablize:

  1. Re-executes every data block against fresh data.
  2. Updates the KPIs, tables, and charts.
  3. Regenerates the narration with the new numbers.
  4. Saves a dated version and increments the version history.

You can open any historical version from the version drawer. Comparing this week to last is a one-click diff.

Sharing

Three share modes:

  • Private (default) — only workspace members can open.
  • Team link — workspace members plus anyone with the link who has a Viewer seat.
  • Public link — anyone with the URL. No login required. Rate-limited but unauthenticated.

Public reports make great client deliverables. The link is stable; re-runs update the contents at the same URL.

To embed in Notion / Slack / a website, public reports support oEmbed — paste the link and most tools render it automatically.

Editing

Two edit modes:

  • Ask — tell the Agent what to change. “Add a chart of refunds by product.” “Remove the KPI about new users.” “Rewrite the summary more concisely.”
  • Direct — click any section and edit the Markdown directly. Data blocks are edited by clicking into them and changing the underlying query.

Changes are saved continuously. The “saved” indicator in the toolbar flickers once per save.

Report types

While every Report is technically a Markdown doc, three patterns cover most real uses:

  • Recap — “what happened last period?” Weekly or monthly. KPI strip + narration. Good for #updates channels.
  • Deep-dive — “why did X change?” Longer form. Multiple charts, hypotheses, evidence. Good for post-mortems.
  • Client recap — for consultants. Parameterized (see Scripts) so you can generate one per client from the same template.

You don’t pick a type up front — you evolve toward one as you edit.

Comparing versions

Version drawer → pick two versions → click Compare. You see:

  • KPI diffs (this version vs that one).
  • Text diffs in the narration.
  • Data block outputs side-by-side.

Useful for spot-checking that a scheduled run didn’t accidentally change what the Report was saying.

Deletion and retention

  • Reports soft-delete. The data lives for 30 days, recoverable from the trash.
  • Hard delete removes immediately. Reports referenced by a Dashboard can’t be hard-deleted without first removing the reference — the UI walks you through it.
  • Historical versions count against your plan’s storage.

Common gotchas

  • Report runs but the numbers look stale. Check that the Report’s data block is scoped to a relative time window (e.g., “last 7 days”), not an absolute date. Absolute dates don’t move.
  • Shared link shows “401.” The Report is set to Private. Switch to Team or Public in the share dialog.
  • Can’t find a report you swear you saved. Sidebar → Reports. If it’s not there, check the trash drawer.
  • Narration reads weird after a re-run. The Agent’s narration regenerates each run. If you want fixed prose, convert a narration section from “dynamic” to “static” in the section settings.

Next steps

  • Scripts — when the logic is the thing you want to reuse across different data.
  • Dashboards — when you need live, clickable, multi-panel views.
  • Watches — when you want to be told about a Report’s contents rather than having to read it.