One of the most practical Cowork automation setups is a daily briefing task — a scheduled agent run that assembles your morning context before you start work. Here’s exactly how to build it.
What the Briefing Covers
A well-designed daily briefing task pulls from 3-5 sources and returns a single structured summary. Typical sections: today’s calendar events (from Google Calendar MCP), open priority tasks (from Notion MCP), any overnight emails that need a response (from Gmail MCP), one or two metrics worth knowing (from whatever dashboard you track), and a suggested priority order for the day. The whole thing arrives as a Notion page or appears in a Cowork run log by the time you open your laptop.
Step 1: Set Up Your MCP Connections
The briefing task needs read access to the services it pulls from. In Claude Desktop settings, confirm you have active MCP connections for the services you want to include. At minimum: Notion (for tasks and project status) and Google Calendar (for today’s schedule). Gmail is optional but adds significant value if you get time-sensitive emails. Configure these in claude_desktop_config.json before building the task.
Step 2: Write the Task Prompt
The prompt is the core of the task. It needs to be specific about what to pull, how to structure the output, and where to write it. A working prompt structure:
You are producing my daily morning briefing. Run these steps in order:
1. Check my Google Calendar for today’s events. List all events with time, title, and any location or meeting link.
2. Open my Notion [Priority Tasks database] and list any tasks marked P0 or P1 that are not yet complete.
3. Check Gmail for any unread emails received in the last 12 hours that appear to need a response. List sender, subject, and one-sentence summary.
4. Write the compiled briefing to a new Notion page titled “Daily Briefing — [today’s date]” under [your briefing parent page].
Format the briefing with clear sections: Calendar, Priority Tasks, Email Review, Suggested First Action. Keep it scannable — bullet points, not paragraphs.
Step 3: Create and Schedule the Task
In Claude Desktop, open Cowork and create a new task. Paste your prompt. Set the schedule to daily at a time before you start work — 6:00 AM or 7:00 AM typically. Make sure Claude Desktop is configured to launch at startup on your machine so it’s running when the task fires. If your machine is off or sleeping when the task fires, it will be skipped — there’s no catch-up mechanism.
Step 4: Test It Manually First
Before relying on the scheduled run, trigger the task manually once. Verify it’s pulling from the right Notion database, writing to the correct parent page, and that the calendar and email integrations are connecting. Most first-run failures are MCP authentication issues — the MCP server needs to be authenticated with each service before the task can use it.
Iteration: Making It Better Over Time
The first briefing will be useful but imperfect. After a week of runs, refine the prompt based on what’s missing or what’s noise. Common refinements: add a “what’s overdue” check from Notion, filter email to only flag certain senders or subjects, add a weather check for field-based work, or include a one-line summary of the prior day’s Cowork run logs. Each iteration takes 5 minutes to update the prompt; the task runs better every week.
Can Claude Cowork send me a daily briefing automatically?
Yes — you build a Cowork task with the briefing prompt, connect it to your MCP sources (Notion, Google Calendar, Gmail), and schedule it to run each morning. The briefing appears in Notion before you start work. Claude Desktop must be running and your machine must be awake at the scheduled time.
What MCP connections does a daily briefing task need?
Minimum: Notion (for tasks) and Google Calendar (for schedule). Optional but valuable: Gmail (for overnight emails). All must be configured in claude_desktop_config.json and authenticated before the task can use them.
Related: How Claude Cowork Can Actually Train Your Staff to Think Better — a 7-part series on using Cowork as a training tool across industries.
Leave a Reply