Templates can be created, previewed, and run on demand regardless of
whether the background cron is wired. The Run Now button and the
POST /api/v1/reports/templates/[id]/run-now API execute the full
pipeline (sources → narrative → formats → delivery) immediately without
depending on AWS EventBridge or any external scheduler.Templates only rely on the cron when they’re attached to a
schedule and you want the schedule to fire
automatically. See EventBridge Setup
(optional during pilot).Schema
dataSources
Ordered array. Each entry references a registered data source by key:
sections
Optional presentation metadata keyed by dataSourceIndex. Use this to
override the auto-generated section title or provide an id that is
referenced by the narrator:
s1, s2, … and titles
derived from the source’s label field.
formats
Array of format keys. Each produces one artifact per run. Supported in
the current release:
pdfcsvmarkdownhtml
narrative
enabled: whenfalse, the narrator is skipped entirely.prompt: optional addendum appended to the system prompt.modelOverride: provider-specific model name. Falls back to the tenant default when omitted.
filters
Arbitrary Json used for cross-section filtering. Currently recognised:
filters.destinations: array of notification-provider UUIDs used as fallback destinations when a run is triggered via/run-nowwithout a schedule.
Running a template
Two unconditional invocation paths:- Preview —
POST /api/v1/reports/templates/[id]/previewruns every data source + narrator and returns the rendered result without persisting aReportRunor dispatching to destinations. Used by the/settings/reportslive-preview pane. - Run Now —
POST /api/v1/reports/templates/[id]/run-nowexecutes the full pipeline (persistReportRun, dispatch to every configured destination). Works independently of the cron.