Which ChatGPT Work workflow should I try first?

Start with a task you already know well and can quality-check—month-end variance analysis, a campaign brief, or sales meeting prep. OpenAI recommends these because you can verify output quickly.

ChatGPT Work Tutorial: 6 Role-Based Workflows, Prompt Templates & Automation Recipes (2026)

Q: How long should a ChatGPT Work prompt be?

Aim for 150–400 words focused on data sources, output format, and constraints. Do not micromanage every step—that is what Work mode plans for you.

Q: Do Scheduled Tasks run when my laptop is off?

Desktop Scheduled Tasks require the device to be online and logged in. For true background automation, use web Workspace Agents on Plus plans and above.

Q: What is the difference between Work mode and Workspace Agent?

Work mode is personal agent mode inside ChatGPT. Workspace Agents are team-built, admin-governed automations in Business and Enterprise plans with Admin Console controls.

Q: Can I use generated slides and reports externally as-is?

Treat them as 80% drafts. Always human-review financial numbers, customer names, and external statements before publishing or presenting.

Q: What can Free users run from this guide?

Free users can access Work mode on desktop with usage limits. Start with lightweight tasks like invoice reconciliation before scheduling long-running automation.

Table of Contents

This is a hands-on companion to our ChatGPT Work launch guide (Codex merge, feature overview, Cowork comparison). For coding-assistant positioning see our Cursor vs Claude Code comparison.

01 · Summary: What to Do on Monday Morning

On July 9, 2026, OpenAI launched ChatGPT Work and folded the standalone Codex app into a unified ChatGPT desktop experience. If you already read the launch coverage, you know the headline: an agent that runs for hours across apps and ships finished documents, spreadsheets, slide decks, and lightweight web apps. The harder question is operational: what do you actually hand it on Monday morning?

OpenAI's own onboarding advice is deliberately modest—start with a task you already know well. A month-end variance analysis. A campaign brief. A sales meeting prep doc. Something where you can judge quality in minutes, not days. This guide follows that philosophy with copy-paste prompts organized by role, Plan Mode review checklists, Scheduled Tasks automation recipes, and metered-usage optimization tactics drawn from OpenAI's internal validation cases, early adopters at Zapier and Nvidia, and the Workspace Agent Cookbook.

Three numbers frame the opportunity: 1,400+ plugins in the unified directory; roughly 5 million weekly Codex users (with more than 1 million already running non-coding workflows); and OpenAI's internal claim that month-end close workflows compressed from days to hours. The sections below turn those capabilities into repeatable playbooks—not another launch recap.

02 · Three Pain Points Worth Taking Seriously

Most teams treat Work like Chat and burn quota. Work mode plans its own execution path. If you micromanage every click ("open Salesforce, export CSV, then…"), you pay for redundant reasoning and still get mediocre output. The fix is outcome-based prompts with explicit data sources and deliverable formats—covered in Section 03 and 04.
Plan Mode is skipped on high-stakes jobs. Finance exports, customer-facing emails, and compliance-sensitive reports need step-by-step approval before autonomous execution. Approving a plan that pulls the wrong month's data or auto-sends an external email is a career-limiting move. Section 04 includes a review checklist; every role template below flags constraints.
Scheduled Tasks fail silently on sleeping laptops. Desktop Scheduled Tasks require the device online and logged in. Teams that schedule a 6:30am dashboard brief on a MacBook that sleeps overnight wake up to nothing—and blame the product. Section 11 covers trigger design; Section 13 covers troubleshooting. For true background automation, Plus-and-above web Workspace Agents are the safer path.

03 · Three Principles That Decide Success

Before you copy a prompt, internalize how Work differs from everyday Chat:

Principle	What it means	Practical tip
Describe outcomes, not steps	Work plans its own path	❌ "Open Salesforce, export, then…" → ✅ "Build a weekly pipeline PPT from @Salesforce deals in the last 30 days, flagging at-risk opportunities"
Connect tools first	Plugins are Work's data layer	Authorize Gmail, Slack, Drive before starting; use `@AppName` to pin sources
Plan Mode is your brake	Review before execution	For external emails, financial reports, and client deliverables, approve every step

3.1 Pick the Right Mode: Chat / Work / Codex

Using the wrong mode wastes quota and produces the wrong artifact type:

Your need	Use	Why
Quick Q&A, brainstorming, single-turn copy	Chat	Lightweight, fast
Multi-app projects, finished deliverables, hours-long tasks	Work	Plugins + Plan Mode + Computer Use
Code review, PRs, multi-repo development	Codex	Developer-native workflows
Recurring background automation	Work + Scheduled Tasks	Triggered or scheduled execution

3.2 Desktop vs Web: Where to Run Each Workflow

Scenario	Recommended environment
Local file read/write, Computer Use, Free-tier trial	Desktop (Mac / Windows)
Team collaboration, monitor task progress on the go	Web / mobile (Plus and above)
Sales meeting brief auto-generation + email notification	Web Workspace Agent + scheduled dispatch
Local Excel reconciliation, folder batch processing	Desktop Work mode

04 · Universal 5-Step Workflow

Regardless of role, run every Work job through this sequence:

1. Connect plugins → 2. Write goal + output format → 3. Review Plan Mode → 4. Steer mid-flight → 5. Accept deliverable & iterate

4.1 Work Mode Prompt Formula

[Role] + [Data sources @plugins] + [Task] + [Output format] + [Constraints] + [Acceptance criteria]

Example skeleton: You are a [role]. Pull [data type] from [time range] via @Salesforce and @Gmail. Complete [specific action], output as [Google Docs / Excel / PPT / Sites]. Constraints: [do not modify source data / two decimal places / no external email]. Notify me via [Slack / save to folder] when done.

4.2 Plan Mode Review Checklist

Before approving execution, confirm each item:

Are data sources correct (right account, right month)?
Any high-risk actions (send external email, delete, overwrite files)?
Does output match your team's template?
Can any steps be removed to save usage?
Do you need a human approval checkpoint?

05 · Sales Workflows

Sales teams were among the earliest Work adopters. OpenAI's internal case: a discovery conversation converted into a customized PoC proposal within 24 hours—a process that traditionally took weeks. The templates below adapt official Cookbook patterns and Zapier-style pipeline repair workflows.

5.1 Scenario A: Daily Customer Meeting Briefs (Scheduled)

Pain point: Reps spend 1–2 hours daily assembling client background, recent news, and meeting agendas. Work solution: Scan tomorrow's calendar, pull CRM notes, search public news, generate briefs, and email a summary.

Create a scheduled task running every weekday at 4pm: 1. Check tomorrow's customer meetings in @Google Calendar (exclude internal-only) 2. For each customer meeting: - Pull 30-day account notes and interaction history from @SharePoint / @Salesforce - Search 30-day public news and executive moves for that company - Write a 2–3 sentence background summary for each external attendee 3. Generate a 2–3 page brief per meeting, save as @Google Drive documents 4. Email me a summary with links via @Gmail Output format: email subject "Tomorrow's Customer Meeting Briefs — [date]", body as table (Client | Meeting time | Key topics | Brief link)

5.2 Scenario B: Live Account Command Center (Sites + Daily Refresh)

Pain point: Enterprise account intel lives across CRM, email, and Slack—with no single live view. Work solution: Build an interactive Sites dashboard that refreshes on a schedule.

Based on all opportunities, contacts, and recent activity for [Account Name] in @Salesforce: 1. Create an interactive account command center (Sites) including: - Pipeline overview (stage, amount, expected close date) - 7-day key signals (email threads, meetings, support tickets) - Prioritized next actions 2. Set Scheduled Task: refresh every weekday at 8am 3. Slack me on major changes via @Slack DM Constraints: do not auto-send external emails; amounts must match CRM source data.

5.3 Scenario C: Lead Review & Pipeline Repair

Pain point: Thousands of monthly leads with invisible follow-up gaps. Work solution: Cross-reference CRM and email touchpoints, surface broken handoffs, estimate pipeline loss.

Analyze @Salesforce leads from the last 30 days cross-referenced with @Gmail sales outreach. Find: 1. Leads with no follow-up for 48+ hours (grouped by source) 2. Broken handoff points (where response rate drops sharply) 3. Estimated pipeline loss amount Output: - Excel detail table (Lead ID | Source | Last follow-up | Gap type | Recommended action) - 1-page executive PPT highlighting seven-figure opportunity risk - A repeatable weekly review workflow suitable for Scheduled Task automation

06 · Marketing Workflows

6.1 Scenario A: Research → Brief → Multi-Market Assets

Pain point: Research, campaign briefs, and regional asset adaptation are typically split across people—with context lost at every handoff. Work solution: One instruction chain with phase gates.

I uploaded the following customer research: [attachment / @Google Drive link] Complete an end-to-end marketing workflow: Phase 1 — Brief: - Extract target audience, core pain points, competitive positioning - Output Campaign Brief (Google Docs) with messaging pillars and channel recommendations Phase 2 — Asset generation: - Based on the Brief, generate: 1 acquisition email, 3 LinkedIn posts, 1 landing page copy outline - Save to @Google Drive "Campaign / [Product Name]" folder Phase 3 — Regional adaptation: - Adapt core assets for US, EU, and APAC (language, cultural references, compliance wording) - Flag sensitive phrases requiring human review in each version Pause after each phase for my approval before continuing.

6.2 Scenario B: Slack / Teams → Meeting Agenda Sync (Weekly Scheduled)

Set a scheduled task running every Monday at 7am: 1. Summarize important discussions from the last 7 days in @Slack #product-launch and @Microsoft Teams "Go-to-Market" channel 2. Extract: decisions made, open questions, blockers needing alignment 3. Update the "Weekly Agenda" document in @Google Drive (preserve version history) 4. Post a summary of 5 bullets or fewer to @Slack #leadership Constraints: quote only public discussions; do not leak messages marked confidential.

07 · Finance Workflows

7.1 Scenario A: Month-End Variance Analysis (OpenAI-Validated)

Pain point: Month-end close and forecast adjustments consume days of manual data hunting and spreadsheet work. Work solution: Auto-locate source data, build reconciliation sheets, draft narrative, produce management deck. OpenAI reports compressing close cycles from days to hours.

Assist with [Month] month-end budget variance analysis: 1. Pull actuals from @Google Drive "Finance / Actuals" and forecast from "Finance / Forecast" 2. Create a reconciliation workbook in @Google Sheets: - Summarize actual vs forecast variance by department - Flag line items with variance >5% or >$50K - Preserve all original formulas; do not overwrite source files 3. Draft performance narrative (Google Docs) categorized by Revenue / COGS / OpEx with plausible explanations 4. Build a 5–8 slide management deck with charts following attached template style 5. List 3 key judgment calls requiring human finance sign-off Constraints: do not modify any source data; cite source cell for every number.

7.2 Scenario B: Invoice vs. Payment Register Reconciliation

You are an accounts payable specialist. Compare: - Payment register: [@Google Drive link] - Invoice list: [@Google Drive link] Flag the following anomalies (return as table): | Issue type | Vendor | Invoice # | Amount | Recommended action | - Amount difference >2% - Missing tax ID - Duplicate invoice number - Vendor name mismatch Do not initiate payments; output review table for human verification only.

08 · Operations Workflows

8.1 Scenario A: Daily Dashboard Morning Briefing (Scheduled)

Run automatically every weekday at 6:30am: 1. Visit [internal dashboard URL / @SharePoint report page] 2. Compare to yesterday's snapshot; extract significant changes (>10% swing or new red indicators) 3. Generate a 1-page morning brief (Google Docs) structured as: - Today's TOP 3 items to watch - Metric change table - Recommended follow-up owners 4. Email ops-leads@company.com via @Gmail If the dashboard is unreachable, stop and notify me in Plan Mode—do not fabricate data.

8.2 Scenario B: Customer Feedback Clustering → Product Priorities

Monitor new customer feedback from the last 14 days across: - @Slack #customer-feedback - @Gmail label "NPS-Detractor" - @Google Drive "Support Tickets Export" 1. Cluster feedback into 5–8 themes (with representative quotes) 2. Rank by frequency × impact × implementation effort 3. Output a prioritized product review list (Notion / Google Docs format) 4. Set a Scheduled Task to refresh this document every Friday Constraints: anonymize all customer references; no customer names in output.

09 · Product Workflows

9.1 Scenario A: Launch Readiness Review (Jira + GTM Cross-Check)

Pain point: Product launches require simultaneous checks across engineering progress, marketing plans, and support docs—manual and error-prone. Adapted from Nvidia's cross-system readiness pattern.

Launch readiness review for [Product/Feature Name]: 1. Pull linked Epic / Story completion status and open blockers from @Jira 2. Pull the corresponding GTM plan from @Google Drive "GTM Plans"; verify key milestones 3. Extract unresolved discussions from @Slack #product-launch in the last 7 days 4. Output Launch Readiness report (Google Docs): - Readiness score (Red / Yellow / Green) - Blocker list (Owner | Due date | Risk level) - Recommended Go / No-Go judgment with rationale Do not auto-update Jira status; flag high-risk items for human decision.

10 · Engineering: Work + Codex in the Same App

Engineering scenarios split cleanly: Codex mode handles code implementation; Work mode handles cross-team documentation and announcements. Both live in the same desktop app—switch modes without changing tools.

10.1 Scenario A: PR Review → Release Notes → Team Announcement

In Codex mode: 1. Review PR #123 in [repo/name], focusing on [security / performance / test coverage] 2. Leave line-by-line review comments in the PR sidebar 3. If approved, draft Release Notes Switch to Work mode: 4. Format Release Notes for @Confluence 5. Draft @Slack #engineering announcement (do not auto-send)

10.2 Scenario B: Multi-Repo Weekly Engineering Summary

In Codex mode, across [frontend-repo] and [backend-repo]: 1. Summarize this week's merged PRs and open P0/P1 issues 2. Generate engineering weekly report in Markdown Switch to Work mode: 3. Convert to Google Docs and insert burndown chart from @Jira 4. Set Scheduled Task: generate every Friday at 5pm

11 · Scheduled Tasks Recipe Library

OpenAI highlights four high-frequency automation patterns teams adopt first:

Recipe	Trigger	Action	Best for
Monday agenda refresh	Mon 7am	Slack digest → update agenda doc	Marketing / Ops
Daily metrics brief	Weekdays 6:30am	Dashboard diff → email report	Ops / Finance
Feedback clustering	Fri 4pm	Multi-channel → priority list	Product
Account daily refresh	Weekdays 8am	CRM changes → update Sites dashboard	Sales

11.1 Scheduled Task Prompt Pattern

Set Scheduled Task: - Frequency: [daily / every Monday / 1st of month / when keyword appears in @Slack channel] - Time: [timezone + specific time] - Action: [specific workflow description] - Notification: [Slack channel / email / none] - Human approval: [which steps require my sign-off first]

11.2 Safety Checklist Before Going Unattended

Minimal plugin scope—connect only what the workflow needs
No auto-external-send unless explicitly intended
Output archive path set to avoid accidental overwrites
Enterprise: agent network policy confirmed with admin
Run 2–3 manual single-shot tests before enabling the schedule

12 · Usage Optimization: Do More for Less

ChatGPT Work shares a metered usage pool with Codex—not a flat monthly feature. The same workflow can cost 5× more depending on how you write the prompt and structure the plan.

12.1 Billing Factors (Simplified)

Factor	Impact on usage
Task step count	More steps = higher consumption
Context size	More documents and emails pulled = higher input cost
Output length	Output tokens cost roughly 6× input tokens
Cache hits	Repeated reads of the same doc cost ~1/10 of fresh input
Model selection	GPT-5.6 deep reasoning costs more than lightweight tasks need

12.2 Seven Cost-Saving Tactics

Draft in Chat first, then hand a tight brief to Work for execution
Trim Plan Mode steps, especially duplicate pulls from the same data source
Reuse template documents in Scheduled Tasks to benefit from cache discounts
Request concise outputs—"table + 3 bullets" beats a narrative report
Split large projects into phases to avoid expensive full re-runs
Free users: test small desktop tasks before scaling automation
Enterprise: set workspace / group / individual limits in Admin Console

12.3 Pre-Launch Usage Test

1. Pick a real task you know the human time cost of (e.g., month-end variance table, usually 2 hours manually) 2. Run once in Work with Plan Mode; note step count 3. Check consumption against your plan's included usage 4. Extrapolate daily / weekly / monthly cost at that run rate 5. If high → apply Section 12.2 tactics and re-run to compare

13 · Common Pitfalls & Troubleshooting

Issue	Cause	Fix
Codex projects missing	Incomplete app migration	Update Codex app → becomes ChatGPT desktop; if broken, clean reinstall from chatgpt.com/download
Plugin connected but no data	Insufficient scope or wrong `@name`	Re-check plugin permissions; use explicit `@Salesforce` not "the CRM"
Good plan, wrong output	Stale context or AI inference	Pause and steer; attach explicit source files
Scheduled task didn't fire	Device asleep / logged out	Use web Workspace Agents for true background; desktop tasks need device online
Usage higher than expected	Verbose output, redundant pulls	See Section 12 optimization tactics
Work vs Cowork confusion	Different workflow philosophy	Cloud SaaS orchestration → Work; local folder batch jobs → Cowork (see launch guide Section 06)

14 · 30-Day Onboarding Roadmap

Week	Goal	Action
1	Single-task fluency	Run 3 manual Work tasks you can quality-check; practice Plan Mode review
2	Plugin depth	Connect 3 core tools (email + collaboration + files); complete 1 cross-app deliverable
3	Automation	Convert Week 1 task to Scheduled Task; verify 3 successful triggers
4	Team rollout	Document role-specific prompt library; Enterprise teams set admin usage limits

15 · Frequently Asked Questions

Q: Which workflow should I try first?
A: The task you know best and can verify—month-end variance, campaign brief, or sales meeting prep. OpenAI recommends these because you can judge quality quickly.

Q: How long should my prompt be?
A: 150–400 words focusing on data sources, output format, and constraints. Do not micromanage steps—that is Work's job.

Q: Do Scheduled Tasks run when my laptop is off?
A: Desktop tasks need the device online. For true background automation, use web Workspace Agents on Plus plans and above.

Q: Work mode vs. Workspace Agent?
A: Work is personal agent mode inside ChatGPT. Workspace Agents are team-built, admin-governed automations in Business and Enterprise with shared governance.

Q: Can I use generated slides and reports externally as-is?
A: Treat them as 80% drafts. Always human-review numbers, names, and external statements.

Q: What can Free users run from this guide?
A: Desktop Work with usage limits. Start with lightweight tasks like invoice reconciliation before scheduling long-running automation.

16 · Conclusion

ChatGPT Work is not valuable because it exists—it is valuable when it removes a workflow you already resent doing manually. The fastest path to ROI is not reading more launch coverage; it is picking one task you know intimately, running it three times, tuning the prompt, and then automating it with Scheduled Tasks.

Start with the workflow closest to your desk. Let Plan Mode earn your trust on a low-stakes run before you approve a finance export or customer email. Then let Scheduled Tasks handle the boring repetition—while you keep human review on anything that leaves the building.

17 · Validate Workflows on an Isolated Mac Before Production Rollout

Every template in this guide assumes OAuth access to production Gmail, Slack, Salesforce, and Drive—and on desktop, Computer Use can read and edit local files. Running a month-end variance workflow or a sales brief automation on your primary MacBook means granting an agent broad permissions on the machine where your Xcode signing identities, personal documents, and browser sessions live. A misconfigured Scheduled Task that overwrites a shared Drive folder or sends a draft email externally is a real operational risk—not a hypothetical one.

Windows and Linux users can sample web-side Work, but they cannot fully exercise macOS-specific paths: Codex default-icon behavior, Metal-accelerated Computer Use latency, and developer flows that parallel Xcode and GitHub Desktop. If you need Apple-faithful acceptance testing before team rollout, rent an M-series Mac mini for a day—run plugin authorization → three-mode smoke test → one role workflow from this guide → destroy the node—instead of polluting your daily driver. See M-series Mac compute pricing for billing and SSH access; for agent isolation patterns see the Agent Skill complete guide.

18 · References

OpenAI Blog — ChatGPT for your most ambitious work
OpenAI Cookbook — Sales Meeting Prep Agent
ChatGPT Learn Changelog — learn.chatgpt.com/docs/whats-new
SiliconANGLE — OpenAI debuts ChatGPT Work agentic tool
Developers Digest — ChatGPT Work Codex desktop merge analysis

Last updated: July 11, 2026. Work rollout timelines, plugin availability, and usage billing may change—confirm on OpenAI's official channels.