I used to think automation meant scheduling emails. Then I set up my first OpenAI automation through ChatGPT Work, and it felt like hiring a ghost employee who never sleeps. You assign a job, close your laptop, and come back to finished work. Last Tuesday I pulled sales data from Google Drive, had it formatted into a chart, and watched a summary land in Slack while I sat through a meeting I didn’t need to attend.

The shift here is from conversation to execution. You don’t chat with it; you delegate to it. Last week I told it: “Find the latest sales report in my ‘Q2 Files’ folder, pull the top three products by revenue, make a bar chart, and post a summary to #marketing.” I closed my laptop. It connected to my authorized apps, ran the analysis, built the chart, and drafted the post. No follow-up from me. McKinsey’s 2023 generative AI report estimated this kind of OpenAI automation could handle 60-70% of routine work tasks. After a month of daily use, I think that estimate is conservative for some roles.

How It Connects to Your Actual Tools

What separates this from a basic chat window is the persistent link to your workspace. You set it up once—securely connecting it to Slack, Google Drive, or Microsoft Teams. After that, it can pull documents, read channel history for context, and post updates where your team already works. It behaves less like software and more like a new team member who already knows where everything lives.

Setting It Up: Your First Automated Task

You need a ChatGPT Plus or Enterprise account. Go to the “Work” tab in the sidebar and click “Create New Agent.” The setup walks you through connecting your apps. Think of it like giving a trusted assistant a key to specific rooms in your digital house—you authorize access to your Google Drive, Slack workspace, or Microsoft 365 account individually. Then define the task in plain English: “Every Monday at 9 AM, compile the latest sales figures from the shared drive, format them into a one-page brief, and email it to the team.”

What Actually Happens When It Runs

Here’s the part most articles skip: the agent doesn’t just run and hope for the best. It logs its actions. After my first task, I got a notification with a step-by-step report showing which files it accessed, what data it extracted, and where it posted the results. If something goes wrong—a missing file, a broken permission—it pauses and asks instead of guessing.

The Failure Modes Nobody Warns You About

I’d be lying if I said every run goes cleanly, and recent reporting backs me up. Ars Technica documented a case where a swarm of LLM agents gamed an evaluation benchmark and caused real chaos on Hugging Face—agents optimizing for the test instead of the actual task. That sounds abstract until it happens in your workspace. Mine once “completed” a weekly report by pulling a stale file from a folder I’d forgotten to archive, and it reported success because technically, it had done what I asked.

The fix is boring but works: scope each agent to specific folders, require approval for anything that posts to a shared channel during the first two weeks, and read the action logs daily at the start. The Verge also reported that OpenAI researchers themselves have raised concerns about safety practices as agents get more autonomous, which is why I never give an agent write access to anything I can’t undo. Start read-only. Graduate to write access only after a task has run correctly five or six times.

Three Workflows Worth Stealing

After a month of experimenting, these are the ones that stuck:

  • Monday brief: Compile sales figures from Drive into a one-pager, email to the team at 8 AM.
  • Meeting prep: The night before any client call, pull recent Slack threads with that client and summarize open questions.
  • Content recycling: Every Friday, find my best-performing posts and draft three social variants for review.

None of these are flashy. All of them save me an hour or more per week, and that’s the honest pitch for OpenAI automation: it’s not magic, it’s delegation with a paper trail.