Scheduled digests

Scheduled digests are daily briefs you set up through your own Claude MCP and receive privately, so you start the day with exactly the state you care about instead of hunting for it. You describe what you want summarized and when, and it arrives on its own each day.

A digest is not a dashboard you have to remember to open. It is a short, written brief that comes to you, built from live data at the hour you choose. Because you set it up in plain language through MCP, changing what it contains is just another sentence.

Two kinds of digest

There are two digests, aimed at the two questions marketers ask most mornings:

• My tasks: your work on the Workflow board, grouped into what you own, what is on you, and what you are tagged in, so you can plan the day in one read.
• Campaign performance: the last 24 hours of your active campaigns, the sends that delivered and fired, with recommended next steps attached.

One tells you what to do, the other tells you how yesterday's work landed. Many people run both, one to plan the morning and one to steer the sends already in flight.

The recommended next steps are what make the performance digest more than a report. If a send underdelivered against its usual rate, the digest can suggest the obvious follow-up, so the brief hands you a first move instead of leaving you to work one out. You still decide, the digest just saves you the cold start.

Private by default

Personal digests are private. The default delivery is a direct message in Claude from a Digest coworker bot, a note meant for your eyes only. Your morning brief is yours, and it does not post your task list or your numbers into a shared channel unless you decide it should.

Privacy here is not a setting you have to remember to switch on. Personal digests start private, so sharing one is the deliberate act, never the accident.

When a digest is meant for the group, you can point it somewhere shared instead. Delivery can be any of:

• A private direct message in Claude, the default for personal digests.
• A team workflow note on the shared board.
• Slack, for a channel or a person.
• Email, for a plain inbox brief.

You own your digests

Digests are per-person. Each person creates, pauses, resumes, or deletes their own, and sets the hour it runs. There is no admin assigning briefs to the team, just individuals wiring up the summary they want. Setting one up is a single request:

You: Every weekday at 8am, send me a private digest of my
tasks and my campaign performance from the last 24 hours.

Digest: Scheduled for 8:00am on weekdays, delivered as a
private message here. Pause, resume, or delete it anytime.

Pausing a digest while you are out and resuming it when you are back is the same kind of one-line request. Because it is yours, you are never waiting on anyone else to change it.

You choose the hour, and the digest runs on your schedule, every day or every weekday, quietly in the background. If it stops being useful, you delete it and it is gone. No ticket, no admin, and no shared setting that someone else depends on.

Why a written brief beats another dashboard

The digest leans on the rest of the harness to be useful. It reads the same Workflow board your team already works from and the same campaign records the orchestration layer keeps, then writes them up for you. There is nothing new to instrument, just a standing summary of what is already there.

It also works in the other direction: a my-tasks digest can surface a task you own but have not touched, or a handoff still waiting on you, before it slips. The brief becomes a small daily nudge that keeps your slice of the board from going stale.

That is the MCP-native pattern in miniature: you say what you want in plain language, and a coworker bot delivers it on a schedule. The brief meets you where you work instead of asking you to go find it.