Region: If more than one squaredup-* server is connected, ask the user which one they mean before running any tools, then use that same server for every SquaredUp tool call in the task.
Scheduling dashboard reports
Email a dashboard snapshot to notification channels on a recurring schedule (a "scheduled report" / digest). This is the time-based delivery path - for health-triggered alerts use the alerting skill instead.
Prerequisites
- A dashboard to send (
dashboard_list → dash-…).
- One or more notification channels to deliver to (
channel_list → channel-…; create with channel_create, see the notifications skill).
Tools
| Tool |
Purpose |
scheduled_report_list |
List a workspace's scheduled reports. |
scheduled_report_get |
Read one report. |
scheduled_report_create |
Schedule a new report. |
scheduled_report_update |
Pause/resume, reschedule, or replace configuration. |
scheduled_report_delete |
Delete a report. |
Creating
scheduled_report_create({
workspaceId: 'space-...',
dashboardId: 'dash-...',
channels: ['channel-...'],
title: 'Weekly Ops Summary',
message: 'Last week at a glance.',
schedule: {
freq: 'WEEKLY',
byDay: ['MO'],
start: { year: 2026, month: 6, day: 15, hour: 9, minute: 0 },
timezone: 'Europe/London',
},
});
start is the first send, in local time of timezone, and must be in the future - a past start is rejected.freq is DAILY / WEEKLY / MONTHLY / YEARLY; interval repeats every N periods (e.g. WEEKLY + interval: 2 = fortnightly); byDay picks weekdays for WEEKLY.theme defaults to dark; set useSharedDashboardLinks: true so recipients without a licence can open the dashboard.
Pausing / resuming
scheduled_report_update({ workspaceId, reportId: 'task-...', status: 'disabled' }); // pause
scheduled_report_update({ workspaceId, reportId: 'task-...', status: 'scheduled' }); // resume
Common mistakes
- No channel. A report needs at least one channel; create one first.
- Editing configuration partially.
configuration is replaced wholesale, not merged - read the current one with scheduled_report_get and pass the full object back. To only pause or reschedule, use status / schedule, which leave the configuration untouched.
- Confusing with alerts. Scheduled reports send on a clock; alerting rules send when a monitor changes health.
1---2name: scheduled-reports3description: Use when the user wants a dashboard emailed on a recurring schedule (digest / scheduled report), e.g. "email the ops dashboard every Monday at 9am", "send a weekly report to the Slack channel", "pause the scheduled report", "stop the daily digest". For health-triggered alerts use the alerting skill instead.4---56> **Region:** If more than one `squaredup-*` server is connected, ask the user which one they mean before running any tools, then use that same server for every SquaredUp tool call in the task.78# Scheduling dashboard reports910Email a dashboard snapshot to notification channels on a recurring schedule (a "scheduled report" / digest). This is the _time-based_ delivery path - for health-triggered alerts use the `alerting` skill instead.1112## Prerequisites13141. A dashboard to send (`dashboard_list` → `dash-…`).152. One or more notification channels to deliver to (`channel_list` → `channel-…`; create with `channel_create`, see the `notifications` skill).1617## Tools1819| Tool | Purpose |20| ------------------------- | --------------------------------------------------- |21| `scheduled_report_list` | List a workspace's scheduled reports. |22| `scheduled_report_get` | Read one report. |23| `scheduled_report_create` | Schedule a new report. |24| `scheduled_report_update` | Pause/resume, reschedule, or replace configuration. |25| `scheduled_report_delete` | Delete a report. |2627## Creating2829```js30scheduled_report_create({31 workspaceId: 'space-...',32 dashboardId: 'dash-...',33 channels: ['channel-...'],34 title: 'Weekly Ops Summary',35 message: 'Last week at a glance.',36 schedule: {37 freq: 'WEEKLY',38 byDay: ['MO'],39 start: { year: 2026, month: 6, day: 15, hour: 9, minute: 0 },40 timezone: 'Europe/London',41 },42});43```4445- `start` is the _first_ send, in local time of `timezone`, and **must be in the future** - a past start is rejected.46- `freq` is `DAILY` / `WEEKLY` / `MONTHLY` / `YEARLY`; `interval` repeats every N periods (e.g. `WEEKLY` + `interval: 2` = fortnightly); `byDay` picks weekdays for `WEEKLY`.47- `theme` defaults to `dark`; set `useSharedDashboardLinks: true` so recipients without a licence can open the dashboard.4849## Pausing / resuming5051```js52scheduled_report_update({ workspaceId, reportId: 'task-...', status: 'disabled' }); // pause53scheduled_report_update({ workspaceId, reportId: 'task-...', status: 'scheduled' }); // resume54```5556## Common mistakes5758- **No channel.** A report needs at least one channel; create one first.59- **Editing configuration partially.** `configuration` is replaced wholesale, not merged - read the current one with `scheduled_report_get` and pass the full object back. To only pause or reschedule, use `status` / `schedule`, which leave the configuration untouched.60- **Confusing with alerts.** Scheduled reports send on a clock; alerting rules send when a monitor changes health.
squaredup