How do I set up recurring reports?

Requires Pro

Quick answer

Recurring reports in Notory are built on saved reports: once built, you can run the same report again at any time — the numbers are recalculated fresh on every call. If a report’s schedule field carries a cadence (daily / weekly / monthly), the server generates it automatically at that cadence and stores each run as a snapshot (available via GET /reports/{id}/runs). You can also always retrieve any report manually at any time via Run or CSV export.

Prerequisites

Required role Logged-in user with access to the Reports module

— Any logged-in user of the tenant can create, change, and run reports.

Reports are a Pro feature (custom_fields). This guide assumes you already have a report set up — see Create & export a report.

Good to know

If you set schedule to daily, weekly, or monthly, a background scheduler (worker, daily) automatically runs the report at that cadence and saves each result as a snapshot. You retrieve the saved runs via GET /reports/{id}/runs; the time of the last run is stored as last_run_at on the report definition. This requires a running worker (REDIS_URL set) — without a worker, the report remains available manually via Run / CSV export, as before. The report builder in the web interface doesn’t yet show an input field for schedule; you set the cadence via the API.

Guide

GUI (web interface)

1. Reuse a report. In the Reports module, open a saved report. It keeps its object type, grouping, and metric — you don’t need to rebuild anything.

2. Run it again. The result is recalculated fresh every time you open it. This way, for example, you get the same “Contracts by status” report with current numbers every week.

   Screenshot pending berichte-zeitplan-01 Saved report being reopened, showing current numbers

   Saved reports return current numbers on every call.

3. Export regularly. For recurring reporting, use “Export CSV” on your own cadence (e.g. at month-end) to download the raw data.

API (curl)

Set the cadence on the definition — via PUT on the report. schedule is a free-form string; a cron-like notation is common.

Set the cadence (schedule)

curl -X PUT https://demo.notory.io/api/v1/reports/018f7d10-2a3b-7c4d-8e5f-6a7b8c9d0e1f \
  -H "Authorization: Bearer inv_dein_token" \
  -H "Content-Type: application/json" \
  -d '{ "schedule": "0 6 * * 1" }'

For automatic recurring reporting, call the report from your own automation (cron, CI, scheduler) at the cadence you want:

Run weekly (example cron line)

# Mondays 06:00 — save the result as CSV
0 6 * * 1  curl -s -H "Authorization: Bearer inv_dein_token" \
  https://demo.notory.io/api/v1/reports/018f7d10-2a3b-7c4d-8e5f-6a7b8c9d0e1f/export.csv \
  -o /backups/verträge-$(date +\%F).csv

What happens behind the scenes?

• The definition is reusable: The “recurring” part lives in the saved report — the definition stays, and the numbers are recalculated on every /run or /export.csv call.
• schedule is metadata: The value is stored and returned with the definition, but it isn’t executed by an internal job. It describes the desired cadence and can optionally drive your own external automation.
• No automatic delivery: Notory doesn’t send report results by email on its own. If you want that, orchestrate the retrieval externally (cron/script) against the API.
• Fresh data: Because every run aggregates live, recurring reports always reflect your tenant’s current data.

Related topics

• Create & export a report
• What reports are available in Notory?
• API introduction — authentication for automated calls