Connected Workflow: Weekly Team Brief

The Scenario

You're a team lead managing eight people across two time zones. Every Monday morning, you spend 45 minutes preparing a team brief: scanning the week's calendar for key meetings, checking email threads for client updates and blockers, reviewing Slack channels for anything that happened over the weekend. Then you compile all of it into a single message your team can read in five minutes.

It's useful work. It's also entirely mechanical. The information is already sitting in three systems — Calendar, Gmail, and Slack. You just need to pull it together and format it.

Today, you're going to build a connected workflow in Cowork that does exactly this. By chaining three connectors with a structured prompt, you'll produce a weekly brief that's better than what you write manually — because Cowork can scan more messages, check more threads, and cross-reference more calendar entries than you can in 45 minutes.

What You'll Learn

By completing this tutorial, you'll be able to:

• Test individual connectors in isolation before chaining them
• Design a multi-phase prompt that gathers, analyses, and formats data from three sources
• Cross-reference data from Calendar, Gmail, and Slack to produce integrated insights
• Identify and correct common failure modes in multi-connector workflows (fabricated action items, noise, stale tokens)
• Refine search criteria to improve signal-to-noise ratio across runs
• Document a reusable workflow suitable for scheduling

Prerequisites

• Claude Desktop with Cowork enabled (Pro or Max plan)
• Google Calendar connector installed and authenticated in Cowork
• Gmail connector installed and authenticated in Cowork
• Slack connector installed and authenticated in Cowork
• An active Google Calendar with events for the coming week
• Email threads in Gmail relevant to your team's work
• Slack channels your team uses for project discussion

Step 1: Define the Brief Structure

Before connecting anything, define what a good weekly brief looks like. Your team brief should contain:

1. This Week's Key Dates — meetings, deadlines, milestones from the calendar
2. Client & Stakeholder Updates — important email threads that need the team's attention
3. Channel Highlights — significant Slack messages, decisions made, blockers raised
4. Action Items — things specific team members need to do this week
5. Watch List — items that aren't urgent but need monitoring

Write this structure down in a file called brief-template.md. Include formatting preferences: do you want bullet points or paragraphs? Should action items tag people by name? Should the tone be formal or conversational?

Here's an example of what a well-structured brief-template.md looks like:

# Weekly Team Brief — Template

## Format Rules
- Bullet points for all sections (not paragraphs)
- Action items tagged with person's name in bold
- Dates in DD Month YYYY format
- Maximum 5 items per section (prioritise, don't list everything)
- Tone: professional but direct — internal team document, not a board report

## Sections

### 1. This Week's Key Dates
Meetings, deadlines, milestones. Include time, participants, purpose.

### 2. Client & Stakeholder Updates
Email threads that need team awareness. Include client name, topic, urgency.

### 3. Channel Highlights
Decisions made, blockers raised, questions that need answers from Slack.

### 4. Action Items
Specific deliverables with owner and deadline. Only items explicitly assigned or committed to.

### 5. Watch List
Items not urgent today but trending toward urgency. Early warnings.

Checkpoint: You've got a brief-template.md that defines the five sections and formatting rules for your weekly brief.

Step 2: Test Each Connector Individually

Before chaining connectors, verify each one works on its own. This isolates problems — if the chained workflow fails, you need to know whether the issue is with a connector or with the chaining logic.

Calendar test:

Show me all events on my calendar for this coming Monday through Friday. Include the event title, time, participants, and location (if any).

Verify: Does it return your actual calendar events? Are the dates correct? Are recurring meetings included?

Gmail test:

Search my Gmail for emails from the last 7 days that mention any of these terms: "deadline," "blocker," "update," "review." Show me the subject, sender, date, and a one-sentence summary of each.

Verify: Does it return real emails? Are the summaries accurate? Did it respect the 7-day window? Pay attention to whether it searches across all folders or just the inbox — important threads may be in Sent, Drafts, or custom labels.

Slack test:

Search my Slack workspace for messages from the last 7 days in channels [list your team's channels]. Show the most important 10 messages — those mentioning deadlines, decisions, blockers, or action items.

Verify: Does it return real Slack messages? Are they from the correct channels? Is the relevance ranking sensible?

Record the results of each individual test in a simple table:

This table serves double duty: it verifies your connectors work, and it gives you a baseline to diagnose issues if the chained workflow fails later. If the chained workflow produces bad Calendar data but your individual Calendar test was fine, the problem's in the chaining logic, not the connector.

Checkpoint: All three connectors return accurate, relevant data when tested individually.

Step 3: Build the Chained Workflow Prompt

Now combine all three into a single prompt. The key to multi-connector workflows is giving Cowork a clear sequence and telling it how to cross-reference the data:

Produce this week's team brief by pulling data from three sources. Follow this exact process:

Phase 1 — Gather:

1. Pull all calendar events for Monday through Friday this week (titles, times, participants)
2. Search Gmail for emails from the last 7 days mentioning deadlines, blockers, updates, or reviews
3. Search Slack channels [list your channels] for messages from the last 7 days about decisions, blockers, or action items

Phase 2 — Analyse: 4. Cross-reference: identify any calendar meetings that relate to email threads or Slack discussions 5. Extract action items: anything where someone was asked to do something or committed to a deliverable 6. Identify blockers: anything flagged as stuck, delayed, or waiting on someone

Phase 3 — Format: 7. Produce the brief following the structure in brief-template.md, with these sections: Key Dates, Client & Stakeholder Updates, Channel Highlights, Action Items, Watch List 8. Save as weekly-brief-[date].md in the current folder

Use British English. Keep the tone professional but conversational — this is an internal team document, not a board report. Name specific people when assigning action items.

Checkpoint: Your chained prompt has three clear phases (gather, analyse, format) and references all three connectors plus the template file.

Step 4: Execute and Monitor the Workflow

Submit the prompt and observe how Cowork handles the multi-connector workflow:

• Connector sequencing: Does Cowork call all three connectors simultaneously (parallel gather) or one at a time? Note which approach it takes.
• Cross-referencing: Watch for the analysis phase — does Cowork connect a calendar meeting about "Project Alpha" with an email thread about "Alpha deliverables" and a Slack message about "Alpha blockers"?
• Data volume: How many calendar events, emails, and Slack messages did it process? Is this more or fewer than what you'd have scanned manually?

The workflow will likely take 2-5 minutes depending on the volume of data across your three sources.

Checkpoint: The workflow has executed and produced a brief file. You've observed the connector sequence and cross-referencing behaviour.

Step 5: Quality-Check the Brief

Open the generated brief and evaluate each section:

Key Dates:

• Are all important meetings listed? Compare against your actual calendar.
• Are dates and times correct?
• Are any events missing or duplicated?

Client & Stakeholder Updates:

• Do the email summaries accurately reflect the threads?
• Are sensitive emails (personal, confidential) excluded or included? Note this for security considerations.
• Did Cowork identify the most important threads, or did it surface noise?

Channel Highlights:

• Are the Slack messages genuinely significant, or did Cowork grab low-value chatter?
• Are channel names correctly attributed?
• Is any confidential information from private channels included that shouldn't be?

Action Items:

• Are the action items real? Cross-check against the source emails and Slack messages.
• Are they attributed to the correct people?
• Are any fabricated? (This is the most critical check — Cowork sometimes infers action items that were never actually stated.)

Watch List:

• Are these genuinely things to monitor, or filler?

Checkpoint: You've reviewed every section, verified accuracy against source data, and noted any errors or fabrications.

Step 6: Refine the Prompt

Based on your quality review, update the prompt. Common refinements:

• Reducing noise: Add filter criteria — "Only include emails where I'm in the To field, not CC" or "Exclude Slack messages with fewer than 2 reactions"
• Improving cross-referencing: Add explicit guidance — "If a calendar meeting and an email thread share a client name or project name, group them together in the relevant section"
• Preventing fabrication: Add a constraint — "Only list action items that are explicitly stated in source messages. Don't infer commitments from general discussion."
• Adjusting scope: If the brief is too long, narrow the date range or limit the number of items per section

Run the refined prompt and compare the output with your first attempt.

Checkpoint: The refined prompt produces a noticeably better brief — less noise, better cross-referencing, and no fabricated items.

Step 7: Save as a Reusable Workflow

Create a file called weekly-brief-workflow.md that documents:

1. The final prompt (refined version)
2. Prerequisites: Which connectors must be installed, which channels to monitor, which email filters to apply
3. Execution steps: Point Cowork at this folder, paste the prompt, review the brief
4. Quality checks: The verification steps to run every time (especially the action item accuracy check)
5. Scheduling notes: Instructions for setting this up as a scheduled Monday morning task (see Domain 4 for scheduling details)

Checkpoint: The workflow is documented in a file that anyone on your team could use to produce the weekly brief.

Step 8: Test Reliability

Run the workflow a second time on different data. If possible, wait a day or two so the source data changes (new emails arrive, Slack messages accumulate, calendar events shift).

Compare the two runs:

• Is the brief structure consistent?
• Does the quality hold up with different data volumes?
• Are there any new edge cases (e.g., a calendar event with no participants, an email thread with no clear subject)?

Document any reliability issues and add them to your workflow file as known limitations.

Common reliability findings:

• Connector timeouts: If one connector takes longer than expected (Slack scanning many channels), the overall workflow may time out. Consider narrowing the Slack scan to fewer channels.
• Data volume sensitivity: A week with 200 Slack messages produces a different quality brief than a week with 20. Note whether the workflow degrades gracefully or fails entirely with high volumes.
• Cross-referencing drift: The quality of cross-referencing (connecting a Calendar meeting about "Project Alpha" with an email thread about "Alpha deliverables") may vary between runs. Some runs will make the connection; others may miss it. Note the consistency.
• Stale connector tokens: If several days pass between runs, OAuth tokens may need refreshing. Add a "verify connector health" step to your workflow documentation.

Checkpoint: You've run the workflow at least twice and documented its reliability characteristics.

Expected Output

Your deliverable is a working multi-connector workflow:

• brief-template.md — the structure template for the weekly brief
• weekly-brief-[date].md — at least one generated brief
• weekly-brief-workflow.md — the complete documented workflow with prompt, prerequisites, quality checks, and known limitations

This workflow replaces 45 minutes of manual scanning and compilation every Monday morning. It also provides better coverage — Cowork scans every email and every Slack message in the window, not just the ones you happen to remember.

Extension Challenges

1. Add a fourth source — Integrate a Notion or Google Drive connector to pull project status documents into the brief alongside Calendar, Gmail, and Slack data.

2. Personalised briefs — Modify the workflow to produce individualised briefs for each team member, highlighting only the meetings, emails, and Slack threads relevant to their projects.

3. Schedule it — Set the workflow up as a scheduled Monday morning task using Cowork's scheduling feature. Configure it to run at 7:30am every Monday and send the brief via email or Slack using dispatch. Verify it runs reliably for two consecutive weeks.