Automating Workflows With Claude Cowork
How to use Cowork’s overlooked features to automate the boring work
Welcome to another post in the AI Coding Series, where I’m sharing the strategies and insights I’ve developed for effective AI-assisted coding.
This post is a collaboration with Ilia Karelin, who writes Prosper, a newsletter sharing tactical AI workflows with frameworks you can plug into your own setup. What drew me to Ilia’s work is that he goes deep into areas most people only skim the surface of, explaining them in layman’s terms that simplify things for both tech and non-tech folks. His complete setup guide for Claude Chat, Cowork, and Code is one of the most thorough breakdowns I’ve seen. With Cowork gaining traction, I’ve noticed a gap between people who installed it and people who know how to make it useful. Ilia bridges that gap better than anyone I’ve read, so I was glad he was open to writing this together. Subscribe to Prosper here:
Cowork is Anthropic’s answer to non-technical folks seeking the benefits of Claude Code - an agent inside the Claude Desktop app that reads your files, connects to your tools, and executes complex tasks end-to-end without you writing a single line of code. If Claude Code is built for engineers, Cowork is built for everyone who wants the same capabilities without having to open a terminal.
You point it at a folder and describe what you need in plain language: organize 200 scattered files by type and project, turn receipts into a formatted expense report, batch-rename months of screenshots with consistent dates, or synthesize five research PDFs into a single brief with citations.
Since January, I’ve been running my newsletter production inside Cowork: idea triage, outline generation, draft editing, and automations that process my raw notes every Monday morning without me touching them.
The difference isn’t my prompting skill, but three useful Cowork features: connectors, scheduled tasks, and plugins. This post covers all three with concrete workflows you can reuse.
Connectors: Cowork reads and writes to your actual tools
Connectors let Cowork plug directly into the tools you already use: Gmail, Notion, Slack, and Google Drive. and work with your actual data inside a session.
In February, Anthropic expanded connectors beyond project management tools to include popular everyday apps such as Gmail, Google Calendar, Notion, and more.
The connector I use most is Notion. It handles nested pages well, which matters for any workspace with real depth. The brain dump workflow, where raw ideas I capture on my phone get automatically triaged into structured newsletter briefs every Monday, is the next section that runs entirely through it.
Gmail is the other app worth connecting to. Even without any scheduled tasks, having Cowork read your emails during a Cowork session, rather than you pasting them in, reduces friction enough that you’ll actually use it for email-related work, such as drafting emails in your style or taking bulk actions like archiving all emails from a specific sender.
The real payoff comes when you combine a connector with a scheduled task. That’s where Cowork stops being something you open and starts being something that runs in the background.
Scheduled tasks and automated workflows
In Cowork, each piece of work you hand off to Claude is called a task.
To set one up, type /schedule in any Cowork session and pick a frequency: daily, weekly, monthly, weekdays only, or on demand. That’s useful for anything that needs to happen regularly without you having to start it each time.
How to set it up
Two paths: type `/schedule` in any session, or use the “Scheduled” tab in the sidebar to create tasks directly. You set a name, a prompt, a frequency, and which folder to work from.
Each scheduled task runs as its own full Cowork session with access to all your connectors, plugins, and folder context.
Note that your laptop must be awake for scheduled tasks to run, as they run locally. Anthropic recently added a feature (see the red arrow below) to prevent your computer from going to sleep, so tasks can continue running.
A workflow I actually use
I have a “Quick Brain Dump” widget on my phone. Whenever an idea hits, I write it into a Notion page - a text block of raw and unrefined stream of thought. Those notes will remain on this page until I manually review and organize them. That is, until I plugged in Cowork.
To make that page usable in Cowork, I first connected my Notion workspace on my phone.
Once I connected my Notion workspace to Cowork, I set up a scheduled task that runs every Monday morning.
Reads everything added to the brain dump page that week
Decides which entries have real newsletter potential
Turns the strong ones into a working title, an angle, and 3 questions I’d need to answer to write it
Saves them to my Newsletter Ideas database as “Needs Review”
I capture ideas throughout the week. When I sit down on Monday, the triage is already done.
Here’s the exact prompt running inside that task (ok to steal):
You are a newsletter research assistant. Connect to my Notion workspace
using the Notion connector.
1. Read all entries added to my “Quick Brain Dump” page this week
2. For each entry, decide: does this have real potential to become a
newsletter post? (yes/no + one sentence why)
3. Only for strong “yes” entries: generate a working title, the angle
that makes it interesting, and 3 questions I’d need to answer to
write it
4. Skip entries that look like tasks, reminders, or personal notes -
only process ideas
5. Save all results to my “Newsletter Ideas” Notion database with
Status = “Needs Review” and Source = “Brain Dump [date]”
If an entry is too vague to evaluate, add it to the database with
Status = “Unclear” and a note on what’s missing.
Here are the results in my Notion workspace:
The same pattern works for anything where raw input is collected in one place and needs to be structured: Slack threads into action items, Gmail into expense logs, Linear tickets into weekly reports.
Cowork is like a back-office assistant that once taught, does the work for you on a recurring cadence.
Chaining scheduled tasks
The output of one scheduled task can feed into the next one’s input.
The brain dump task runs early Monday and saves structured briefs to a Notion database. A second scheduled task runs after that, reads those briefs, picks the strongest one based on recency and audience fit, and drops a full working outline into my local drafts folder.
Task #1 processes raw input. Task #2 acts on structured output. No human intervention needed.
Each plugin is a full toolkit for one domain
There are dozens of plugins available for Cowork, each one a specialist kit for a specific domain. A plugin bundles skills, connectors, slash commands, and subagents around a job function like Sales, Data, or Design, so you don’t have to wire them up yourself.
Install one and you immediately get domain-specific commands and integrations tailored to that role’s actual workflows.
Here’s what the Data plugin contains, for example:
Composable Plugins
You can install multiple plugins and commands inside of those plugins, and pull from all of them in a single task with just a prompt. Pretty incredible.
Here’s a real example. I dropped a messy sales CSV into Cowork: missing values, a duplicate row, a negative amount (these numbers are not real), and ran this single prompt with both the Data and Design plugins installed:
I have a sales CSV file (sample_sales.csv) and the Prosper company logo
(image.jpeg) in this folder.
Step 1 - Data plugin:
/analyze the CSV and find:
- Total revenue by product (excluding refunded transactions)
- Month-over-month revenue trend across January, February, March
- Revenue split by region (North America, Europe, Asia Pacific)
- Any data quality issues worth flagging (nulls, anomalies, duplicates)
Step 2 - Data plugin:
/write-query to calculate the refund rate by product - which product
has the highest percentage of refunded transactions?
Step 3 — Design plugin:
/performance-report using the findings above. Format it as a clean one-page
Q1 sales report for Prosper.
Include:
- The Prosper logo at the top
- A summary section with 3 headline numbers (total revenue, top product,
top region)
- A data quality callout box flagging the issues found in Step 1
- A refund risk section showing which product needs attention
- Brand colors: blue (#4B4EE4), white background, clean sans-serif font
Save the output as prosper_q1_report.pdf
Step #1 used the Data plugin to analyze revenue by product and region, flag the data quality issues, and calculate month-over-month trends. Step #2 wrote the SQL to calculate refund rates by product, and Step #3 switched to the Design plugin and formatted everything into a branded one-page report, logo included.
One prompt. Three steps. The output went straight from a raw CSV to something you could send to a stakeholder.
Where to start
Today: Install Gmail or Slack connectors. Connect whichever tool you actually use to collect raw inputs. Notion, email, whatever it is.
This week: Set up one scheduled task. Pick something you do manually on a recurring basis: drafting a sales update, triaging weekly tasks from Jira/Linear, summarizing newsletters, and let Cowork run it instead. Use the brain dump prompt above as a template, or use Claude to generate a prompt for you by describing the task you want it to automate
This month: Install two or three plugins that are relevant for your tasks, such as Data Analysis or Designer. Then run a task that pulls data from multiple plugins in a single session. Once one scheduled task is working, consider chaining it as input to another task, e.g., a task to draft a report with another to send it via Slack and email.
The goal isn’t to use every feature. It’s to find one workflow that currently requires your manual attention and hand it off. Once that one runs on its own, the next one is easier to see.
That’s how Cowork becomes a system instead of a chatbot.
Recent related posts
 | A guest post by
|
Yes, extremely excited to share this with you all! Let us know what you think!
What a great read!