Workflows · Reporting

The weekly report,ready before your coffee.

Every Monday at 09:00 the lead agent’s own daily prompt starts the chain. It hands the sales export to one helper and the helpdesk to another, waits for both, merges their numbers into one note and sends you the draft in Telegram. You answer from your phone; the team chat gets the report only after you allow it.

Two helpers, one note, one reply from your phone. Allow the post when the lead asks.

The lead’s daily prompt fires at 09:00; helpers pull sales and support numbers, the lead merges them into a note and sends you the draft in Telegram.

A lead and its helpers

Arrows from the lead to each helper are the delegation: agent_send hands out the work, agent_wait collects it.

Each on its own model

The helpers can run on different harnesses — Codex for the spreadsheet, Qwen for the web dashboard.

Starts by itself on Monday

The lead card’s daily prompt fires every morning and does the report only when the day is Monday.

You approve the post

The draft comes to your Telegram; your reply is the lead’s next prompt, and the team chat waits for your Allow.

Workflows · Reporting

From two sources to one approved report

Three agents, a browser, a note and a Telegram bot.

01
Delegate
The lead sends each helper its source.
02
Pull
Sales export and helpdesk dashboard, in parallel.
03
Merge
One report note, in your format.
04
Approve
Your reply in Telegram, then the post.
Related scenarios

More in Workflows

Other live scenarios from the same shelf — and a few close relatives.

Browse all 40 scenarios

Stop assembling the same report by hand

Your agents pull the numbers; you only read and approve.

Download for WindowsWindows 10 / 11 · 64-bit

macOS and Linux are coming later.

The first-run wizard installs an agent CLI, Git and the dictation model for you — or skips each step.