Claude Cowork Examples: Step-by-Step Workflows
Real examples you can copy, adapt, and use for your own work. Each includes the exact prompt, permissions needed, and what to expect.
File Organization Examples
These workflows show how to organize, rename, and manage files on your computer.
Example 1: Organize Downloads Folder by File Type
What it does:
Creates subdirectories (Images, PDFs, Documents, etc.) in your Downloads folder and automatically moves files into them based on type.
Permissions needed:
Read and write access to your Downloads folder on desktop.
Prompt to use:
"Organize my Downloads folder. Create subfolders for: Images (jpg, png, gif), PDFs, Documents (docx, txt, xlsx), Videos (mp4, mov), and Archives (zip, rar). Move existing files into appropriate folders. Show me what you find before moving anything." Expected result: Organized Downloads folder with ~5-10 subfolders and all files moved appropriately.
Time to run: 2-3 minutes for a typical Downloads folder (200-300 files).
Pro tip: Start by asking Cowork to only show you what it found. If the proposed organization looks right, approve the move.
Example 2: Standardize File Names with Consistent Formatting
What it does:
Renames files to follow a consistent pattern like YYYY-MM-DD_descriptive-name_version.
Permissions needed:
Read and write access to the folder containing files you want to rename.
Prompt to use:
"Rename all files in ~/Projects/Reports/ to follow this format: YYYY-MM-DD_filename-description. Use the file creation date for the date part. Remove underscores, spaces, and special characters from names. Show me the rename mapping before applying." Expected result: All files renamed consistently with dates and clean names.
Time to run: 1-2 minutes for a folder with 20-50 files.
Pro tip: Always review the mapping first. Test on 5 files to ensure the naming pattern is correct before applying to hundreds.
Example 3: Archive Old Files Automatically
What it does:
Identifies files not modified in the last 6 months, creates an "Archive" folder, and moves them there.
Permissions needed:
Read and write access to the folder you want to archive.
Prompt to use:
"Archive old files in ~/Documents/Projects/. Find all files last modified before January 2025 and move them to ~/Documents/Projects/Archive/. Create the Archive folder if it doesn't exist. List files being archived before moving them." Expected result: Old files moved to Archive folder, active files remain in original location.
Time to run: 1-2 minutes regardless of folder size.
Data Analysis & Summarization Examples
These workflows extract and analyze data from files or tools.
Example 4: Summarize and Analyze a Google Sheet
What it does:
Reads data from a Google Sheet, calculates key metrics, identifies trends, and creates a summary report.
Permissions needed:
Google Sheets connector authorized, read-only access to the sheet.
Prompt to use:
"Analyze this KPI spreadsheet [share link or name]. Extract this month's metrics, calculate week-over-week changes, identify top performers and areas of concern, and create a one-page summary with key highlights." Expected result: Summary report with trends, anomalies, and key insights ready to share with leadership.
Time to run: 1-3 minutes depending on data size and complexity.
Example 5: Extract Data from Multiple PDFs
What it does:
Reads 10-50 PDF files, extracts specific data (invoice amounts, dates, vendor names), and compiles into a spreadsheet.
Permissions needed:
Read access to folder containing PDFs; write access to save results.
Prompt to use:
"Read all PDFs in ~/Documents/Invoices/. Extract invoice number, date, vendor name, and total amount from each. Create a CSV file with columns: Invoice #, Date, Vendor, Amount. Save to ~/Documents/invoice_summary.csv." Expected result: CSV file with extracted data, ready to import into accounting software.
Time to run: 2-4 minutes for 20 invoices.
Multi-Tool Automation Examples
These workflows coordinate between multiple apps or services.
Example 6: GitHub Issue Triage Workflow
What it does:
Reviews all open GitHub issues, categorizes them, flags duplicates, and suggests priority order.
Permissions needed:
GitHub connector authorized with read access to your repository.
Prompt to use:
"Triage all open issues in owner/repo. Group by type (bug, feature, doc), flag likely duplicates with links, identify stale issues (no updates in 60+ days), and suggest a priority order for the top 10 issues." Expected result: Organized issue summary, ready for team sprint planning.
Time to run: 1-2 minutes for repos with 50-100 open issues.
Example 7: Email Summary & Draft Response
What it does:
Reads recent emails on a topic (e.g., customer complaints), summarizes themes, and drafts responses for your review.
Permissions needed:
Gmail connector authorized, read-only access.
Prompt to use:
"Read all emails from last week with subject containing 'refund' or 'issue'. Summarize the 3 main types of complaints. For each type, draft a professional, empathetic response I can send. I'll review before sending." Expected result: Summary of complaint themes + 3 draft responses ready for your review and personalization.
Time to run: 1 minute to read and summarize 5-10 emails.
Example 8: Weekly Metrics Report Generation
What it does:
Pulls data from multiple sources (Google Sheets, GitHub API, Slack), consolidates, and generates a formatted weekly report.
Permissions needed:
Google Sheets connector, GitHub connector, optionally Slack.
Prompt to use:
"Generate this week's metrics report. Pull data from: (1) KPI sheet [link], (2) GitHub releases [owner/repo], (3) email archives [topic]. Combine into a single executive summary with: KPI trends, shipped features, top issues, and team highlights." Expected result: One-page executive summary combining data from 3 sources, ready to share.
Time to run: 2-3 minutes to fetch and consolidate data from multiple sources.
Frequently Asked Questions
Can I copy these examples exactly or do I need to modify them?
Yes, you can use examples as-is, but you'll need to adapt them to your specific files, folder paths, and tools. Replace 'my Downloads folder' with your actual folder, 'my CRM' with the tool you use, etc.
What if my workflow doesn't match any example?
These are starting points. Describe your goal in natural language to Cowork, and Claude will propose an approach. You can mix and match patterns from multiple examples.
How do I make sure Cowork doesn't break my work?
Always review Claude's proposed plan before approving. For destructive workflows (deleting, renaming), test on a small set first (5-10 files) before running on thousands.
Can I automate these workflows to run on a schedule?
Yes, using Dispatch (Cowork's scheduling feature) or your own cron/automation tools. Start with manual runs to verify behavior, then schedule once you're confident.
How long does each example typically take to run?
Most examples take 1-5 minutes depending on data volume. Organizing 100 files might take 2 minutes; analyzing 1000 email summaries might take 5 minutes.
What permissions do I need for each example?
Each example states required permissions. Read-only examples need read access only. Multi-app examples need you to authorize connectors (Gmail, GitHub, etc.) first.
Ready to Build Your Own?
Use these examples as a starting point. Every workflow can be adapted to your specific needs:
How to Use Cowork
Learn the workflow patterns and best practices.
Read guide →
Use Cases
See how teams across roles use Cowork.
Explore use cases →
Sign In Guide
Web, desktop, mobile login and sync.
Get signed in →
Windows Desktop Setup
Download and install for Windows.
Windows guide →
Cowork vs Code
When to use each tool.
Compare tools →
Getting Started
Setup guide for your first Cowork task.
Get started →
Last updated: September 17, 2026 · More resources: Tested workflows library