@0xchromium: Right now you are doing work b...
Right now you are doing work by hand that a machine could be doing while you sleep
Every morning you check the same sources for trends, you rewrite the same post for three platforms, you pull the same numbers into the same report, you send the same follow-up email after every call
None of that is thinking, it's repetition, and repetition is exactly what automation takes off your plate
Most people use Claude like a smarter search bar, they ask a question, they get an answer, they copy it out, they move on
A workflow is different, a workflow doesn't wait for you to ask, it runs on a schedule or a trigger, it uses tools to actually do things, and it hands you a finished result instead of a reply
The chat answers, the automation acts
This article shows you exactly what to build, role by role, and how to ship your first one in 30 minutes
Part 1: What a workflow does that a chat never will
A normal chat with Claude is a conversation, you type, it responds, the work of acting on that response is still yours
A workflow has four parts that a chat doesn't:
Put those together and you stop being the person who does the task, you become the person who approves it
That's the whole shift, and once you see it you can't unsee how much of your week is just you being a slow trigger for work that doesn't need you
Part 2: What to actually build, by role
For each workflow below you get three things, what it does, how much time it gives you back, and one concrete example of it in action
Content creator
Trend workflow
Repurpose workflow
Weekly review workflow
Freelancer
Lead qualifier workflow
Client report workflow
Sales call prep workflow
Researcher or analyst
Daily digest workflow
Company teardown workflow
Keyword monitor workflow
For everyone, no matter the role
Morning briefing workflow
File organizer workflow
Follow-up workflow
Part 3: How it works, in plain language
Forget the technical version for a second
A chat is a single question and a single answer, the moment it's done, it's done, nothing happens until you type again
A workflow is a worker with a job description, you write down who it is and what it's responsible for, you give it the tools to do that job, you tell it when to start, and you tell it what to hand you when it's finished
That's it, four pieces:
If you can describe a task to a new assistant in five sentences, you can build it as a workflow
Part 4: How to build one, step by step
Step 1: write the system prompt with a role and a goal
This is the single most important part, you're hiring, so write the job description
You are a [role] for me
Your job is to [the one outcome you want] every [when]
You care about [what good looks like] and you avoid [what bad looks like]
When you're done, give me [the exact format of the result]
Be specific and concrete, never give me filler or generic outputThe more specific the role, the better the result, "you are a content strategist who finds contrarian angles for a crypto and AI audience" beats "you help with content"
Step 2: connect the tools it needs
A workflow with no tools is just a chat, decide what this job actually touches:
Give it only what the job needs, nothing more
Step 3: set the trigger
Decide when it runs, two options:
For your first workflow, use a schedule, it's the simplest and it's where most of the value is
Step 4: define what it does with the result
Tell it exactly where the output goes, send me a message, save a file to this folder, draft an email but don't send it, post to my scheduler as a draft for approval
For anything that goes to other people, keep yourself in the loop, the automation drafts, you approve, at least until you trust it
Step 5: test it and tune it
Run it once by hand before you let it run on a schedule, look at the output, then fix the prompt
The first run is never perfect, you'll see it being too generic, or missing context, or formatting wrong, so you go back to the system prompt and you add the missing instruction
Three or four rounds of this and the workflow is doing the job exactly how you would
How to connect the tools and set up your first scheduled task in Claude Cowork
Everything above is the concept, this part is the buttons you actually click, we'll wire up the morning briefing workflow end to end, then you'll have the pattern for all the others
Part 1: connect the connectors for the morning briefing
The briefing needs three things, your email, your calendar, and the web, here's how to turn each one on
1. Gmail
2. Google Calendar
3. Web search
Part 2: set it up as a scheduled task
Connectors give the workflow its hands, the scheduled task gives it a clock, this is what makes it run without you
Open scheduled tasks: in the same plus sign or slash menu, find scheduled tasks, this is where anything that runs on a timer lives
Paste the prompt: create a new scheduled task and drop in the morning briefing prompt from Part 6, the whole block, brackets filled in with your niche
Set the time: set it to run every day at 7am, or whatever time you want the briefing waiting for you, daily is the right cadence for this one
Run it once by hand: before you trust the schedule, trigger it manually once, read what it sends, then go back and fix the prompt if it's too generic or missing something, this is the same tune step from Part 4, just on the real thing
Turn on the schedule: once the manual run looks right, leave the daily schedule on, now it fires every morning on its own and the briefing is there before you open anything
For the other workflows in Part 2 you follow these exact same steps, you just change the prompt and connect different connectors for the job
Part 5: what to change for each use case
Same five steps every time, here's exactly what changes per workflow
Trend workflow for content
Repurpose workflow
Lead qualifier
Client report workflow
Daily digest workflow
Morning briefing workflow
You're not learning six different skills, you're changing the role line, the tools, and the trigger, the machine underneath is identical
Part 6: where to start, your first workflow in 30 minutes
Don't build the complicated one first, build the morning briefing workflow, it's the simplest, it touches the most useful tools, and you'll feel the value the next morning
Here's the prompt, copy it and fill in the brackets:
You are my morning briefing workflow
Every morning at 7am, send me one message with three sections:
1. TODAY, my calendar for the day, flag any meeting that needs prep
2. INBOX, only the emails that actually need a reply today, skip newsletters and noise
3. SIGNAL, one thing that happened in [your niche] in the last 24 hours that I'd want to know, two lines max
Rules:
- one message, no preamble, no sign off
- if a section is empty, say so in one line and move on
- never pad it with filler, I want the shortest version that's still completeNow do the four steps:
Run it once by hand tonight, read the output, fix anything that's off, then let it run tomorrow on its own
That's a real workflow, working for you, before lunch
What changes after your first one
The first workflow is never the one that matters most, the briefing workflow saves you 30 min, that's not the point
The point is what happens in your head after you watch it run, you stop seeing your week as a list of tasks and you start seeing it as a list of jobs you can hand off
The repurpose workflow becomes obvious, then the report workflow, then the lead qualifier, and within a month the question flips from "how do I do this" to "should I be doing this at all, or should a workflow"
The barrier was never the technology, it was thinking of yourself as the person who has to do the work
Build the briefing workflow tonight, that's where it starts



