Designing Automation Workflows

What You Need to Know

Domain 4 has covered each automation tool individually: Computer Use for screen interaction, Dispatch for remote control, and Scheduled Tasks for recurring automations. This lesson brings them together. Real-world automation rarely uses just one tool — it combines multiple capabilities in a single workflow, choosing the fastest and most reliable tool for each step.

The skill being tested here is architectural: given a business problem, can you design a workflow that uses the right tool for each step, handles failure gracefully, and produces verifiable output? This is the synthesis lesson, and the exam tests it heavily.

The tool priority hierarchy in practice

You learned the hierarchy in lesson 4.1: Connectors > Browser > Computer Use. Designing automation workflows means applying this hierarchy at every step of a multi-step chain.

For each step in your workflow, ask: "Does a Connector exist for this?" If yes, use the Connector — it's faster and more reliable. If no Connector exists but the data is available on a website, use browser navigation. If the data only lives in a desktop application with no API or web interface, use Computer Use as a last resort.

A single workflow might use all three:

• Step 1: Pull calendar events via the Google Calendar Connector (fastest)
• Step 2: Check a competitor's pricing on a website via browser navigation (no Connector available)
• Step 3: Export data from a legacy desktop CRM via Computer Use (no API, no web interface)
• Step 4: Save the compiled report to a shared Google Drive folder via the Google Drive Connector (fastest)

Each step uses the highest-priority tool available. No step uses a slower tool when a faster one would work.

Standard automation patterns

Most business automation workflows fall into recognisable patterns. Knowing these patterns lets you design faster — you're not starting from scratch each time.

Daily briefing: Pulls together email, calendar, and messaging data each morning into a single summary. Connectors for Gmail and Calendar, local file output.

Weekly report: Aggregates data from multiple sources into a formatted document on a recurring schedule. Connectors for data retrieval, Skills for formatting, local file output, optional Connector for distribution.

Competitive intelligence: Monitors competitor websites or industry sources and flags changes. Browser navigation or Computer Use for data that isn't available through Connectors, local file output for the audit trail.

Client-facing automation: Processes incoming requests (email, form submissions) and generates standardised responses or documents. Gmail Connector for intake, custom Skill for processing logic, Connector for delivery.

Hybrid orchestration

The most powerful workflows combine multiple Cowork capabilities in a single scheduled task. A weekly competitor pricing report might:

1. Use Computer Use to scrape data from a legacy desktop dashboard (no API)
2. Use a custom Skill to format the data according to the company's reporting template
3. Use the Google Drive Connector to save the report to a shared team folder
4. Use the Slack Connector to notify the team that the report is ready

No single capability could handle this entire workflow alone. Computer Use can't post to Slack. The Slack Connector can't read a desktop application. The Google Drive Connector can't format data. Each component does its job, and the workflow chains them together.

Designing for resilience

Automation workflows fail. The computer sleeps. A Connector token expires. Computer Use misclicks. A website changes its layout. Designing for resilience means anticipating these failures and building in recovery.

Skipped runs auto-execute: Scheduled tasks that miss their window run automatically when the machine wakes up. This is built-in resilience for the sleep problem — you don't need to handle it, just understand it.

Persistent Dispatch thread: Dispatch maintains a single continuous conversation thread. Multi-day workflows where you check progress in the morning and add instructions in the afternoon all share the same context. Claude remembers what happened earlier.

Verifiable intermediate outputs: Break complex workflows into steps that produce visible, checkable outputs. If step 3 of a 5-step chain saves a file before step 4 emails it, you can verify the file independently if the email step fails.

Breaking tasks into verifiable steps

This is the most important design principle for automation workflows, and the one most people ignore.

A single enormous prompt — "Check all my emails, organise my files, update my CRM, create a report, and send it to my team" — is impossible to debug when something fails. Which step broke? Was it the email retrieval, the file organisation, the CRM update, or the report generation? You can't tell, and you have to run the entire thing again.

Better: break the workflow into steps that produce observable outputs.

1. "Retrieve unread emails from the Leadership Team label and save them to /Documents/Email-Triage/"
2. "Process the emails in /Documents/Email-Triage/ and extract action items to /Documents/Actions.md"
3. "Generate a summary report from /Documents/Actions.md and save to /Documents/Reports/"
4. "Post the report summary to #leadership-updates via Slack"

Each step reads from and writes to a known location. If step 2 fails, you can see exactly what step 1 produced and diagnose the problem. If step 4 fails, the report still exists locally — you can post it manually and fix the Slack step later.

The sleep problem: solving it once

Every automation capability in Domain 4 — Computer Use, Dispatch, and Scheduled Tasks — requires the host computer to be awake. This isn't three separate problems; it's one infrastructure issue that you solve once.

Go to System Settings > Energy (or Battery > Options) and configure your Mac to prevent sleeping when connected to power. This single change makes all of your automations reliable. Without it, every scheduled task, every Dispatch command, and every Computer Use session is at risk of failing when the machine decides to nap.

---

Common Mistakes

---

Hands-On Activity

---

Practice Question

---

Sources

• Let Claude use your computer in Cowork — Anthropic
• Schedule recurring tasks in Cowork — Anthropic
• Put Claude to work on your computer — Anthropic
• Claude Dispatch: Control Cowork From Your Phone — FindSkill.ai