Send scheduled reports with an agent
⚠️
Preview — this feature is being built; the design below is the spec.
Every Monday at 07:00, an agent pulls last week’s numbers, writes a short commentary and posts it to your team. This uses a deployment with a schedule trigger.
Pieces
| Piece | What it does |
|---|---|
| Agent | Instructions for the report: which metrics, what counts as notable, tone and length. |
| Tools | An MCP server or function tools that query your metrics. A tool that posts to your chat system. |
| Environment | Only needed if the agent runs code (for example to draw a chart). |
| Deployment | cron: "0 7 * * 1", timezone: "Europe/London", overlap_policy: "skip". |
Instructions that produce useful reports
- Lead with the three numbers that moved most, with the percentage change.
- Explain a change only when the data shows why; otherwise say the cause is unknown.
- Keep it under 200 words and end with the link to the full dashboard.
Reliability
- Subscribe to
deployment.run.failed; a missing report should be noticed. - Give the session a cost budget; a runaway query loop then stops itself.
- Keep the posting tool behind approval for the first few weeks, then remove the approval once reports are consistently right.
Testing
Use Run now with a fixed date range from the past and compare the agent’s figures with your dashboard before turning the schedule on.
Was this page helpful?