Claude Cowork Singapore: How to Set Up Your First Automated Workflow

The first time Claude Cowork does something automatically — without you opening it, without you typing anything — is the moment it clicks. You start thinking about your whole working week differently. Instead of asking "how do I use AI to help with this?" you start asking "what else can I hand off?" That shift in mindset is the real value of Claude Cowork. The automation is just the mechanism that triggers it.

This guide walks you through setting up your first real automated workflow in Claude Cowork, step by step, from a standing start. No technical background required. By the end, you will have a workflow that runs on its own schedule, producing something useful, without any input from you after the initial setup.

Before You Open Cowork: Know What You Want to Automate

This is the step most people skip, and it's the reason many first attempts feel disappointing. Don't open the app and then decide what to automate. The app is capable enough that you'll be overwhelmed by possibility, and you'll end up with something half-formed that doesn't quite do what you wanted.

Pick one specific recurring task before you open Cowork. Good candidates are tasks that happen on a regular schedule, produce a clear output, and involve inputs that are already in a digital format — your inbox, your calendar, a folder on your computer, a Notion workspace. The best first workflows have one primary input and one clear output.

Good first choices: your Monday morning inbox triage (input: Gmail, output: Slack summary), your weekly content ideas session (input: your industry and recent news, output: 5 draft LinkedIn posts), your Friday client update drafts (input: meeting notes folder, output: email drafts ready for review).

Bad first choices: anything that depends on six different tools simultaneously, anything where the output requires complex judgment calls, anything where the definition of "done" is fuzzy. Keep it simple. A workflow that runs reliably and produces something useful is worth ten ambitious ones that never quite work.

Step 1 — Download and Open Cowork

Download Claude Cowork from claude.com/download. The app is available for both Mac and Windows. The file is straightforward to install — open it, follow the prompts, and you're done in about five minutes.

Sign in with your Claude account when the app opens. If you don't have a Claude account yet, you can create one for free at that same page. The free tier is sufficient to explore Cowork and run your first workflow, though paid plans offer higher usage limits and access to a wider range of connectors. For getting started, free is fine.

Once you're signed in, take a moment to look at the interface before doing anything. The main area is where you create and run tasks. The sidebar gives you access to settings, connectors, and task history. There is no chat interface in the traditional sense — you are in a task-oriented environment, not a conversation one.

Step 2 — Set Your Global Instructions

This is the most important step, and it's the one most people skip because it doesn't feel like "doing" anything yet. Go to Settings and find the Global Instructions field. This is where you write the standing context that Claude Cowork will apply to every task you ever give it.

Think of global instructions as the briefing you would give to a new assistant on their first day — who you are, what your work involves, how you communicate, and the rules you want them to follow without being told each time. Write it in plain English, as if you were writing to a person. A good set of global instructions covers four things: your professional context (who you are and what you do), your formatting preferences (bullet points, length, tone), any hard rules (never delete files, always ask before sending anything), and how you want ambiguity handled (ask a clarifying question rather than guessing).

Here is an example of what strong global instructions look like for a Singapore professional:

That paragraph, written once, shapes every output Cowork produces for you from that point forward. It is the highest-leverage 15 minutes you will spend with the tool.

Step 3 — Connect Your Tools

Go to Connectors in the sidebar. This is where you link Claude Cowork to the external tools your workflow will need to access. Cowork can connect to Gmail, Google Calendar, Slack, Notion, and a growing list of other services.

The key discipline here is to connect only what your chosen workflow actually needs. If your first workflow is a morning briefing from Gmail and Calendar to Slack, connect those three. Don't connect Notion yet just because you also use it. Every connector you add is one more surface area where something could go wrong with a new workflow. Start minimal and expand as you build confidence.

Each connector walks you through an authorisation flow — you'll be asked to sign into the relevant service and grant Cowork the permissions it needs. These permissions are scoped — Cowork can read your Gmail, for instance, but it can't access your Google Drive unless you separately connect that. Read the permission prompts carefully and only grant what your workflow requires.

Step 4 — Create Your First Scheduled Task Using /schedule

Start a new task in Cowork. The input field accepts plain English — you do not need to learn any special syntax or commands. But there is one command worth knowing for this step: /schedule.

Type /schedule at the start of your task description. This tells Cowork that you want this task to run on a recurring basis rather than once. After /schedule, describe your workflow in plain English — what you want done, when you want it done, where the input comes from, and what you want the output to look like.

Here is an example of a well-written scheduled task description:

Notice what this task description includes: a specific trigger time (7:00am weekdays), a clear input source (Gmail, last 24 hours), a clear filtering logic (needs a reply, from clients, has a deadline, marked urgent), a clear output channel (Slack #daily-briefing), a formatting instruction (bullet points, five or fewer), and an edge case handler (what to do if there's nothing urgent). The more specific your task description, the more reliably Cowork will produce what you actually want.

Step 5 — Test It Manually First

Before you trust the schedule, run the task manually. Ask Cowork to execute it immediately — "do this now, not on schedule" — so you can see what it actually produces before you commit to having it run automatically every day.

Review the output carefully. Does the format match what you asked for? Did it surface the right kind of information? Did it miss anything obvious? Are there any instructions it seems to have ignored or misinterpreted?

If the output is close but not quite right, refine your task description and run it again. This iteration loop — describe, test, refine, test again — is how you get to a workflow that you trust enough to run on a schedule. Most people need two or three iterations before they feel confident. That is completely normal. The goal is not to get it perfect on the first try. The goal is to get it reliable before you hand it over to run automatically.

Only once you're satisfied with the manual output should you activate the schedule. From that point, Cowork will run the task at the time and frequency you specified — with no further input required from you.

What to Build Next

Once your first workflow runs reliably — and you've lived with it for a week to make sure it's doing what you expected — it's time to add a second. The process is identical: pick one specific task, describe it clearly with /schedule, test manually, refine, activate.

The Cowork SG community runs a wide range of workflows that you can use as inspiration. Members are automating weekly content calendars (generate LinkedIn post ideas every Sunday based on recent industry news), competitor monitoring alerts (check specific websites weekly and flag anything new), client brief summaries (when a meeting note appears in a designated Notion page, summarise it and draft a follow-up), and download folder cleaners (sort files in Downloads into categories every Friday afternoon).

The pattern across all of them is the same: one clear trigger, one clear input, one clear output. Start there. Complexity can come later, once you understand how Cowork handles the basics.

For more on what Claude Cowork is and how Singapore professionals are using it, see our overview post Claude Cowork Singapore: What It Is and Why Professionals Are Using It. For a broader introduction to the tool, including how to think about global instructions and connectors, the Claude Cowork for Beginners guide is a good companion to this one.