Scheduled · 0 7 * * 1-5

Morning briefing

Per-person summary of inbox, calendar, and pending decisions, delivered before standup.

Status

Active

Trigger

Scheduled · 0 7 * * 1-5

Owner

john

Steps

5

Definition

Steps, top to bottom.

  1. Pull mail since yesterday

    Read the user's Gmail since 6pm prior business day, filter signal vs newsletter.

    Fetch

  2. Pull today's calendar

    Today's meetings + any prep docs linked from invites.

    Fetch

  3. Pull pending decisions

    Open PRs, open Notion docs assigned to user, pending HubSpot approvals.

    Fetch

  4. Compose briefing

    Two paragraphs + a 3-item action list. Keep under 250 words.

    Agent → basal

  5. Deliver to Slack DM

    Post the briefing as a Slack DM from Basal at 7:00 local time.

    Deliver

Why we run this

The morning briefing is the canonical example of the workflow shape we’re optimizing for: a scheduled multi-step task that compresses a long thread of context into a structured starting point for the day.

It’s a Class B (personal) workflow — each person gets their own version with their own sources. The schedule is 7am local time on weekdays, delivered to a Slack DM from Basal. The output is intentionally short: two paragraphs and three actions, designed to fit in a glance before standup.

The workflow’s success metric is “did the user open Slack and immediately know what they were going to do today?” — which we measure indirectly through whether they trigger any of the actions in the first hour.

Run history

Mock data

Last six runs.

Durations, outcomes, and costs below are mock data — every number on this table is fabricated for the demo. The real run history will come from the workforce audit log + fleet-api Worker once Blocks 3 and 4 land (see /roadmap). The table renders the same; the source of truth changes.

When Status Duration Triggered by Version Cost
2026-05-10 07:00 Success 14.2s cron v3 $0.084
2026-05-09 07:00 Success 12.8s cron v3 $0.079
2026-05-08 07:00 Success 19.4s cron v3 $0.094
2026-05-07 07:00 Failed 11.7s cron v3 $0.012
2026-05-06 07:00 Success 13.1s cron v2 $0.081
2026-05-05 07:00 Success 16.4s cron v2 $0.090

Designer · Phase 4

Edit, version, A/B promote.

The in-UI designer lets you edit step lists, swap agents, adjust prompts and parameters, save a new version (immutable history), and promote a candidate when it wins on cost, latency, or quality. Wired with Phase 4. Today's edits go through a platform-team PR.

See /roadmap for sequencing.