Stay informed without logging in#
Briefings deliver a formatted email digest to the workspace owner after a routine run completes. They transform raw pipeline output into a scannable summary you can read from your inbox.
How briefings work#
- A routine runs through the briefing pipeline
- Step results are aggregated into a digest (tasks, due dates, memories)
- The digest is formatted as both HTML and plain text
- An email is sent to the workspace owner's address on file
Triggering a briefing#
Briefings are triggered by routine runs. When a routine completes, you can send the results as an email via the briefing email endpoint.
There is no separate "briefing schedule" — briefings follow the cadence of the routines they summarize.
| Trigger path | What happens |
|---|---|
| Routine completes on schedule | Digest is generated and optionally emailed |
| Routine completes reactively | Same digest flow, same email delivery |
| Manual run via API | POST to the briefings/run or briefings/email endpoint |
Email delivery#
Briefings are delivered via Resend. The email includes:
- A subject line with the routine name and date
- An HTML body with structured sections for each step result
- A plain-text fallback for email clients that strip HTML
info Email delivery failures never crash the pipeline. If the email cannot be sent, the API returns
sent: falsewith an error message, and the digest is still available in the response.
Quota limits#
Briefing runs count against your workspace's daily event quota. If the quota is exceeded, the endpoint returns a 429 with a Retry-After header.
warning Make sure the workspace owner has a valid email address in their profile. If no email is found, the briefing generates the digest but cannot deliver it.
Next step#
Configure where and how you receive alerts with Notifications.