Last updated
Scheduled PDF reports from your database
Rahoto is automated recurring reporting software that turns data in PostgreSQL, MySQL, SQL Server, Oracle Database, SAP HANA and MongoDB, or a warehouse such as Snowflake, Google BigQuery and Amazon Redshift, into a designed PDF report delivered on a schedule. On each run it refreshes the data, rebuilds the pages and sends the PDF by email or to storage, with no export script to maintain.
Read-only connections to the database you already run, a report designed once, and a PDF that is the issue, exactly.
- Read-only connections
- Designed pages
- Scheduled PDF
- Email, S3, Drive, SFTP
How it works
From a database table to a scheduled PDF in four steps
- Connect the database Add the connection and choose the tables, views or collections to read. Connections are read-only by default.
- Design the report Place text, charts, tables, shapes and images anywhere on the page, and bind each chart and table to its dataset.
- Set the schedule Choose the cadence and time zone, and set the dataset to refresh on publish so each run reads the latest rows.
- Choose where the PDF goes Pick email recipients, an S3 bucket, a Google Drive folder or an SFTP server, or post it to Slack or Teams.
Sources
The databases and warehouses it reads
Databases: PostgreSQL, MySQL, SQL Server, Oracle Database, SAP HANA and MongoDB. Warehouses: Snowflake, Google BigQuery and Amazon Redshift.
Snowflake connector · Google BigQuery connector · PostgreSQL connector · Every data connector
Each run
Refreshed, checked, then sent
-
Refresh, rebuild, deliver
Set the cadence once; Rahoto refreshes, rebuilds and delivers.
-
Preflight
Preflight checks every page before it goes out. It advises; it never blocks your download or share.
-
Review when it matters
If a run finds something material, it waits for your approval.
-
Retries
A failed delivery is retried automatically, and you are told if it still doesn’t go out.
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.
- Seven of the eight delivery channels need a paid plan; the web link is on every plan.
- A table shows up to 100,000 rows in the editor and carries up to 10,000 rows into each published edition; for more, narrow the data at the source.
- Delivery is tried up to three times and is not exactly-once.
Questions people ask
Which databases can a scheduled PDF report read from?
Databases: PostgreSQL, MySQL, SQL Server, Oracle Database, SAP HANA and MongoDB. Warehouses: Snowflake, Google BigQuery and Amazon Redshift. Rahoto reads their tables, views and collections, and connections are read-only by default.
Does Rahoto query the database on every scheduled run?
For datasets set to refresh on publish, yes: each run refreshes them, then rebuilds the pages and delivers the PDF. A dataset that is not set to refresh keeps its last copy, so show “data as of” on the page to say when the data was read.
How is the PDF delivered?
By email, inline or attached, or dropped into S3, Google Drive or an SFTP server, and it can be posted to Slack or Teams. The web link is on every plan; the other seven channels come with every paid plan.
Is the PDF vector?
Where fonts allow, yes, with a raster fallback where they do not. The PDF is that issue, exactly; the live web link keeps showing the latest run.
What happens if a column is renamed in the database?
When a source renames or drops a column, Rahoto tells you what moved and helps you remap it. By default a run repairs a change it can map with confidence, such as a renamed column, and stops rather than publish an issue on a change it cannot repair, until you remap it.
Retire the export script
Connect the database, design the report once and set the schedule. Start with a 14-day Starter trial, no credit card.
Prefer email? [email protected]