Elizon Docs
Guides & WalkthroughsDemo Package walkthroughs

Morning Brief

A scheduled Workflow that writes a daily brief and emails it to the team.

elizon-demo/morning-brief · version 1.0.0 · entry point workflows.morning-brief

What it does: every weekday at 07:30 local time, writes one short brief of what's open and what's overdue, and emails it to the team.

It's the smallest demo by object count (one Agent, one Workflow), and the reference for two things: a schedule with a time zone, and a Send Email node at the end of the Workflow.

The shape

elizon.yaml (excerpt)
entryPoint: workflows.morning-brief

compatibility:
  requiredCapabilities: [workflows, schedule]

agents:
  - name: brief-writer
    ref: ./agents/brief-writer.yaml
workflows:
  - name: morning-brief
    ref: ./workflows/morning-brief.yaml

triggers:
  - id: weekday-morning
    type: schedule
    cron: 30 7 * * 1-5
    timezone: Europe/Sofia
  - id: brief-now
    type: webhook

Why a Workflow? A schedule can only start a Workflow. Even with one Agent doing the writing, the entry point is a Workflow that calls it.

What the installer supplies

SlotTypeBind it to
reasoningllmThe model that writes the brief

Where the brief goes is not a Slot. After installing, open the Morning Brief Workflow and fill in its Send Email node: your SMTP server, the password as a {{secret.…}} reference to your Secrets, the sender and the recipients.

The installer also confirms or changes the schedule in the wizard. Europe/Sofia is the author's zone, not a recommendation.

Why the time zone matters

30 7 * * 1-5 alone means 07:30 UTC: 09:30 in Sofia for half the year and 10:30 for the other half. With timezone, the schedule stays at 07:30 local on both sides of every daylight-saving change.

Compliance, as declared

Personal data (the brief names whose ticket is waiting), EU, conversations kept 7 days, autonomous, EU AI Act minimal risk: it summarises the operator's own operational data for their own team and takes no decision about anyone.

What "working" looks like

  1. The evaluation passes its three cases: a day with nothing overdue says so rather than dropping the section, an empty day is one line rather than padding, and a smoke case completes.
  2. After Activate, the schedule shows its next run at 07:30 in the zone you confirmed.
  3. Call the webhook once. A brief arrives in the recipients' inboxes within a minute.
  4. The next weekday, a brief arrives at 07:30 local without anyone touching it.