Cowork · Lesson 06 Pro+ ~15 min read Scheduled tasks + artifacts

Automation: where Cowork stops being a tool.

The last Cowork capability is the one that changes the relationship: scheduled tasks and live artifacts. Scheduled tasks run on cron-like schedules — every morning at 7am, every Monday, every hour. Live artifacts are persistent dashboards that pull fresh data from your connectors each time you open them. Together they turn Cowork from 'a thing I open' into 'a thing that delivers value while I sleep.'

Workflow 01 Set up your first scheduled task

1

A daily 7am briefing in your inbox

Scheduled tasks are recurring Cowork sessions that fire on a schedule. The classic first one is a morning briefing — by the time you open your laptop, the report is waiting.

The prompt that works

Daily briefingCreate a scheduled task with these settings: Name: Morning briefing Schedule: Every weekday at 7:00am Central Task: Look at: • My unread email from the last 24 hours • My calendar for today • Any new messages in the #leadership Slack channel • The 3 KPI dashboards I track Produce a single email to me at 7:05am with sections: • Today's calendar (with travel-time gaps flagged) • Inbox priorities (top 3 things needing attention) • Notable Slack activity (only flags, not summaries) • KPI status (green/yellow/red for each metric vs. target) Keep it under 300 words total. No fluff.

Best use cases

  • Morning briefing for your day
  • Friday afternoon weekly retrospective
  • Sunday-night week-ahead prep
  • End-of-day inbox triage
Don't schedule tasks more often than they're useful. A daily briefing is great; an hourly one becomes noise you ignore. Match cadence to actual decision points.
Time savings: Morning prep: 30 min reactive → 5 min reading the briefing.

Workflow 02 Recurring weekly reports

2

Friday afternoon weekly recap that writes itself

Anyone in a role that requires regular status reports knows how much time they consume. A weekly Cowork report aggregates your sources (email, CRM, project tool, etc.) and produces the recap automatically.

The prompt that works

Weekly statusCreate a scheduled task: Name: Weekly status report Schedule: Every Friday at 4:00pm Task: Compile a weekly status report covering: • Major customer interactions this week (pulled from Salesforce/HubSpot) • PRs merged or features shipped (from GitHub) • Significant decisions or escalations (from Slack #leadership) • Calendar review — meetings worth flagging • Asks for next week (one ask per major stakeholder) Output format: Markdown file saved to my 'weekly-reports' folder, named 'YYYY-MM-DD-status.md'. Also send me a Slack DM with the link.

Best use cases

  • Status reports to your manager
  • Project updates to stakeholders
  • Weekly customer-success summary
  • Sales pipeline review automation
Treat the auto-generated report as a draft. Read it, refine, then send. Reviewers can tell when something was auto-sent without human review — and they remember.
Time savings: Weekly report: 90 min → 15 min including your review.

Workflow 03 Live artifacts — dashboards that refresh

3

Build a persistent view that updates every time you open it

Live artifacts are saved HTML views Cowork can persist and update. Unlike a one-time report, the artifact pulls fresh data from connectors each time it opens — making it a real dashboard, not a snapshot.

The prompt that works

Live artifact dashboardBuild a live artifact called 'team-pulse-dashboard' with these sections: • Open PRs awaiting my review (from GitHub MCP) • Tickets assigned to my team (from Linear or Jira MCP) • Sales pipeline by stage (from CRM MCP) • Recent customer feedback (from a Slack channel or NPS tool) • System status (from monitoring MCP) Design: • Dark mode matching my Cowork theme • Each section is a card with metric + small data table • Reload button at the top to refresh • Mobile-friendly (I'll check it on my phone too) Save it as a persistent artifact I can open daily without rebuilding.

Best use cases

  • Personal command-center dashboard
  • Sales pipeline at-a-glance
  • Team-lead pulse view
  • Executive 'state of the company' view
Live artifacts only refresh what their connectors can see. If you reorganize a CRM or change a Slack channel, you'll need to update the artifact. They're not magically self-healing.
Time savings: A daily dashboard: replaces 10-15 min of clicking through tools.

Workflow 04 Chain tasks for sophisticated automation

4

Multi-step workflows that run on schedules

Once you have the basics, the real power is chaining: one scheduled task produces output that another task processes. Or a task watches for a condition and only acts when triggered.

The prompt that works

Task chain with conditionsBuild this chained workflow: Task 1 — Daily at 7am: Pull all customer support tickets opened in the last 24 hours. Categorize each by severity (P0/P1/P2/P3) using ticket content. Save as a CSV. Task 2 — Daily at 7:15am (15 min after task 1): Read the CSV. If there are any P0 tickets, send me an urgent Slack DM with the top 3. Otherwise, do nothing. Task 3 — Weekly on Friday: Aggregate the daily CSVs from the past week. Compute trends: ticket volume by severity, average time to resolve, top 5 customers by ticket count. Save a weekly summary report. With conditional logic: Task 2 only fires Slack if there's a P0. Don't spam me with 'no P0 today' messages.

Best use cases

  • On-call escalation workflows
  • Pipeline / lead-routing automation
  • Multi-stage report generation
  • Threshold alerting (only ping when condition met)
Chained tasks compound complexity. Start with one task working perfectly, then add the second. Don't build a 5-step chain on day one — debugging it is painful.
Time savings: Sophisticated workflows: 30+ min daily → fully automated.
Run before you schedule

Always run a task manually once or twice before scheduling it. If the output is wrong, you want to know now — not in a week when six bad reports have been sent. The 'preview before scheduling' habit prevents 80% of automation regrets.

Build one scheduled task that runs tomorrow

Pick the recurring task that costs you the most time each week — a status report, a daily briefing, a Friday recap. Configure it as a scheduled task. Run it manually once tonight to verify the output. Schedule it. Tomorrow morning, see what arrives without you doing anything.

Back to Copilot Mastery → Try a prompt in the playground →

What you can do now

  • Configure your first scheduled task
  • Run any new task manually before scheduling it
  • Use conditional logic to avoid notification fatigue
  • Save the artifact-dashboard pattern for daily check-ins
  • Audit scheduled tasks monthly — kill the ones you no longer read
Pro+
Up next in Copilot Mastery

The agent ecosystem

Now that you've mastered Cowork, the broader agent ecosystem is the next horizon — each AI has its own agents. Claude Code for development, Computer Use for desktop control, plus the agent SDKs that let you build your own. See the track →