Automation and safe working: from one-off task to workflow
Combine Skills, Connectors, Dispatch and scheduled tasks into useful workflows. Learn where human oversight remains essential.
Recognize suitable recurring work
Good automation starts with a recurring process that is predictable enough to describe. Define the trigger, required information, steps, desired output and what should happen when data is missing. Do not automate a process that is still unclear.
Dispatch and scheduled tasks
Scheduled tasks are available on paid Claude plans. You can run a task at set times or on demand. Many scheduled tasks run in the cloud and can continue when your computer is off. Tasks using local files or apps, and some older tasks created before October 6, 2026, run locally and need your computer to stay on. Dispatch is different: it lets you send a task from the Claude mobile app to Claude Desktop on your computer. Dispatch is a limited beta on some Pro, Max and Ultra accounts, is not available to new users and requires both the mobile app and a computer with Claude Desktop open.
Build in control
Combine a Skill for the standard workflow with a Connector for the required information. Have the workflow create a draft or report first. Build in an approval step before emails are sent, records are changed or anything is published externally.
Privacy and safe working
Safe working is part of every workflow. Share no more personal or business information than necessary. Never put passwords or secret keys in prompts. Watch for instructions hidden in documents or web pages. Check the first runs and make sure someone is responsible for the outcome.
Claude Meetings: turn discussions into action
Claude Meetings is a beta for Team and Enterprise organizations. You can add Claude as a visible participant to a Google Meet call. Google Calendar must be available to the organization and connected to Claude. Claude takes notes, answers questions and builds documents, whiteboards and slides during the meeting. It stores a transcript, summary and screen descriptions, but not audio. Before adding Claude or enabling automatic joining, everyone in the meeting must agree to transcription. The feature is unavailable to some organizations, including environments with ZDR, HIPAA-ready configuration or CMEK.
Learning objectives
- Recognize recurring tasks suitable for automation
- Understand Dispatch and scheduled tasks at a high level
- Design a workflow with review and approval steps
- Consider privacy, access and human responsibility
- Explain how Claude Meetings works and what consent and organization settings are required
Step by step
- 1Choose a recurring task with a clear beginning and end
- 2Describe the trigger, sources, steps, output and exceptions
- 3Decide which steps Claude may perform independently and where approval is required
- 4Test the workflow with sample data and review the first runs
- 5Before a test meeting, check availability, the Google Calendar connection, participant consent and organization settings
Pro tips
- ·Automate a small process first and measure whether it saves time
- ·Check the approval mode for every workflow and review external communication and irreversible actions by default
- ·Assign an owner to monitor the workflow and its quality
- ·Do not enable auto-join until participants know Claude will transcribe the meeting
Real-world examples
A weekly management briefing
Task prompt:
“Every Monday, prepare a draft briefing based on these approved sources. Summarize anomalies, link to the data used and identify uncertainties. Do not send anything or change source data. Ask for approval before sharing the briefing.”
Result: A recurring draft overview that an employee reviews before sharing it with others.
Turn a Google Meet into an action plan
Task prompt:
“Use Claude Meetings during an internal test meeting to capture decisions, action items and open questions. During the meeting, create a draft document with an owner and deadline for each action. Do not share or send anything automatically. After the meeting, review the transcript and summary with participants.”
Result: A draft action plan and meeting notes that participants can review and update afterwards.
Common mistakes
- ✕Confusing Dispatch with scheduled tasks and assuming both continue in the same way when your computer is off
- ✕Forgetting what should happen if a source is missing or an action fails
- ✕Failing to assign an owner or approval step
- ✕Adding Claude Meetings without first obtaining consent for transcription
Practical exercise: Final assignment: design a safe workflow
Choose a recurring process from your work. Design the workflow on paper before activating it. Do not use real personal data in the first test.
Task prompt
Design a safe Claude workflow for this recurring task: [describe the task]. Specify: 1. trigger, 2. required sources and permissions, 3. steps and any Skills, 4. desired output, 5. review and approval points, 6. exceptions and error handling, 7. owner and measurable time savings. Present a design first and do not activate or send anything.
- The trigger, sources and desired output are specific
- Access and actions are limited to what is needed
- A person approves risky actions
- The workflow has been tested with sample data
Knowledge check
What belongs in responsible automation?


