Skip to content

Reports that run themselves

Rahoto runs a report on the schedule you set: it refreshes the data, rebuilds the pages and delivers them. Before an issue goes out it checks the pages, notices when a source changed shape, and waits for you if something material changed.

Schedule, editions per audience, eight channels, preflight, drift detection and review before delivery.

Start free Talk to sales
  • Schedules
  • Edition per audience
  • Eight channels
  • Preflight
  • Review before delivery
Setting a schedule on a publication: switch it on, choose a cron trigger and a cadence such as weekdays at 8am, and pick the time zone.

Schedule

Set the cadence once

  • Refresh, rebuild, deliver

    Set the cadence once; Rahoto refreshes, rebuilds and delivers.

  • A link that stays current, a PDF that is the issue

    The link opens the live report, kept up to date on your schedule; the PDF is that issue, exactly.

  • Freshness on the page

    Show “data as of” on the page, filled in on every run.

  • Sources

    Rahoto reads from 73 data sources: warehouses, databases, SaaS tools, files and documents.

Browse the connector catalogue

Editions

One report, an edition per audience

One composition, an edition per client or region, each with its own data and recipients.

Before it goes out

Checked, then sent

  • Preflight

    Preflight checks every page before it goes out. It advises; it never blocks your download or share.

  • Schema drift

    When a source renames or drops a column, Rahoto tells you what moved and helps you remap it.

  • Review when it matters

    If a run finds something material, it waits for your approval.

  • Words checked against numbers

    Before each scheduled issue, Rahoto checks the text against the data. If something material changed, the run waits for your review.

Delivery

Where it goes, and in what form

  • Eight channels

    Email, Slack, Teams, a web link or embed, webhook, S3, Google Drive and SFTP. The web link is on every plan; the other seven come with Pro.

  • Output formats

    PDF, PowerPoint, PNG and a live web link.

  • Retries

    A failed delivery is retried automatically.

  • Spreadsheet appendix

    Attach the rows as a spreadsheet.

A worked example: the board pack

Limits

What to know before you rely on it

  • Refresh applies to datasets set to refresh on publish. It does not query every source live on every run.
  • PDF is vector where fonts allow, with a raster fallback. PowerPoint keeps editable shapes and text and breaks charts into editable parts, with some image fallback.
  • PowerPoint is a format, not a channel. Seven of the eight channels need the Pro plan.
  • Delivery is retried up to three times and is not exactly-once.
  • The spreadsheet appendix is off by default, capped at 50,000 rows, and skipped for editions scoped to a recipient.
  • “Data as of” shows when the data was read. It is not proof that every source is current.
  • The text check is not a guarantee that a statement is true, and web-link-only runs skip the narrative refresh.

Questions people ask

Is every source queried live on every run?

No. Rahoto refreshes the datasets that are set to refresh on publish, then rebuilds the pages and delivers them.

What happens when a source renames or drops a column?

Rahoto tells you what moved and helps you remap it. Preflight checks every page before it goes out; it advises and never blocks your download or share.

What if a delivery fails?

A failed delivery is retried automatically, up to three attempts with a growing wait. Delivery is not exactly-once, so a recipient can occasionally receive a repeat.

Is PowerPoint a delivery channel?

No. PowerPoint is an output format, alongside PDF, PNG and a live web link. The delivery channels are email, Slack, Teams, a web link or embed, webhook, S3, Google Drive and SFTP.

Bring the report you rebuild every month

Set its sources, layout, editions and schedule once, and let the next issue arrive without you.

Start free Talk to sales