The idea in one sentence
You save a connection, write a query, and attach a schedule to it. On every trigger DataRunner runs the SQL, formats the result and delivers it through the channels you pointed at. Everything else in the product — monitors, incidents, status pages — exists so you find out when that path breaks.
The whole path
- 01Create an account at console.datarunner.app. The workspace is created with it and you own it.
- 02Under Connections, add your database. Test the connection before saving — the test runs a trivial SELECT and tells you exactly what failed.
- 03Under Queries, write the SQL and run it once. The result appears below, with the row count and duration.
- 04Save the query and attach a schedule: cron expression, timezone and output format.
- 05Point at least one delivery channel. With no channel the run still happens, but the result stays in the history.
The free plan allows one connection, five schedules and a thousand queries a month. That is enough to put a real report into production before deciding anything.
Knowing it worked
Every trigger writes a line into the query history, with start time, duration, row count, and the error when there was one. Delivery writes its own receipt: the channel, the destination, and the answer it gave. If the email did not arrive, the receipt says whether it left here.
- Run history — what the database answered.
- Delivery receipts — what each channel answered.
- Failure alerts — who was told, and when.