Scheduled digests
A digest is a recurring email that delivers a saved query — daily, weekly, or monthly — to a list of recipients. Use it to push the morning numbers to a Slack-allergic exec, or to keep the team on the same retention chart every Monday.
Open Digests in the sidebar (/digests).
Creating a digest
Click New digest
Pick the saved query
The saved query is the chart that will be rendered into the email. If you leave it blank, the workspace Overview is sent instead.
Pick a cadence
daily, weekly, or monthly. Weekly sends every Monday; monthly sends on the 1st.
Add recipients
A comma-separated list of email addresses. Each recipient gets a one-click unsubscribe link in every email — unsubscribes are per-recipient, so the subscription itself is not deleted.
Save
The subscription enters the Active list with a Next run timestamp.
Timezone
The send hour is configured per workspace under Settings → Workspace timezone. A weekly digest scheduled at 09:00 will fire at 09:00 in the workspace’s timezone, not UTC.
Changing the workspace timezone reschedules every active digest on the next cron tick — you don’t need to re-create them.
Managing subscriptions
| Action | What it does |
|---|---|
| Pause | Suspends sending. Resume later with no recipient changes. |
| Resume | Re-enables a paused subscription. |
| Delete | Removes the subscription. Recipients keep already-sent emails. |
The list shows the attached saved query, cadence badge, recipient count, next run time, and status.
What the email contains
- A chart image rendered server-side from the saved query.
- A short summary line (“12% week-over-week”).
- A View in dashboard link that deep-links to the saved query.
- A per-recipient unsubscribe link.
Limits & gotchas
- Recipient cap — a soft limit of 50 emails per subscription; for larger lists, split into multiple digests or use Slack via Alerts.
- Image rendering falls back to a table view if the chart type cannot be rasterised (e.g. AI Chart with custom components).
- Send failures retry up to 3× with backoff; persistent failures (bounced address, blocked domain) mark that recipient inactive — the rest still receive.
Related
- Saved queries — the source for every digest
- Alerts — event-driven notifications (vs. scheduled digests)