Skip to content

Scheduled operational reports

Recurring reports that have to run without anyone remembering to run them, and arrive somewhere useful.

What it produces

A document, or a set of documents, produced on a schedule and delivered to email, Google Drive, SharePoint, S3, SFTP, or a local volume.

How you build it

  1. Build the report and confirm it renders with real data
  2. Create a Report Generation Job
  3. Add parameters the schedule should vary — a reporting period, for example
  4. Turn on Enable scheduled generation and set the recurrence
  5. Add one or more deliveries and set their targets
  6. Watch the first runs in the job's run history

What makes it tricky

  • A job can have several deliveries. The same run can email a summary and drop the file on SFTP, each with its own condition.
  • Delivery conditions are evaluated per entry. In a repeating job that means a delivery can fire for some rows and not others.
  • Folder paths accept text templates. {$record.tier}/{$params.period} builds the destination path per entry, and missing folders are created.
  • Schedules run on the server's clock. Check it before assuming a 1st-of-the-month run lands on the 1st in your timezone.
  • Jobs cannot be created through the API — the V1 API triggers and monitors runs, but jobs themselves are built in the UI.

Report Generation Jobs · Google Drive Delivery · SMTP Settings · API