Scheduled tasks in ChatGPT Work can now trigger when a Gmail message lands or a Slack channel updates, and any task can be shared. Free plans get three.
Until now a scheduled prompt ran on a clock. It now runs on an event, and the first events OpenAI chose are the two places a seller's day actually changes: an inbox and a Slack channel. A prospect replies, and a draft of the next step can be waiting before you open the thread. Sharing turns a manager's best task into something a whole team runs identically.
A scheduled task is a standing instruction ChatGPT runs on your behalf without you typing it again. Until now it ran on a timer: every morning, every Monday. A webhook is a signal an app sends the moment something happens, so the task now runs when the event occurs rather than when the clock says.
Sharing a task does not share your data. The recipient gets the instructions and connects their own Gmail or Slack, so the copy runs against their inbox, not yours.
The short version: a scheduled prompt can now be an event-triggered prompt, and your best one can be handed to a colleague in one step.
OpenAI updated scheduled tasks in ChatGPT on August 25, 2026. Tasks in ChatGPT Work can now use webhooks to run when something changes in a connected app, and any task can be shared with another person, who reviews the instructions, connects their own apps, and runs an independent copy.
Triggers supported at launch: a new Gmail message, a message in a Slack channel (add @ChatGPT to each monitored channel), and GitHub pull request activity.
Who gets triggers: Plus and Pro users, on web, iOS and Android. Free and Go users cannot create webhook-triggered tasks.
Sharing: Free, Go, Plus and Pro users can share tasks. Running a shared webhook task requires access to Work and the recipient's own connected app.
Free tier: up to three active scheduled tasks, running once or recurring no more than daily.
Approvals: actions that require approval pause until the user reviews them.
What it doesn't do: the announcement lists no CRM, calendar or Outlook triggers, and no Business or Enterprise availability for webhook tasks. A Slack trigger only sees channels where @ChatGPT has been added.
SDR — The obvious build is a reply handler: when a prospect answers a sequence, classify the reply and draft the next touch before you see it. Keep the approval step on; a webhook that sends without review is a webhook that sends the wrong thing at volume.
AE — Point it at the Slack channel where your deal team talks. Every time a customer comment lands, a summary of what changed and a proposed next step is waiting. The gap is CRM triggers, which are not in this release, so deal-stage changes still need a timed task.
Manager — Sharing is the feature. Build one task, share it, and the team runs the same process the same way. Decide what the standard is before you distribute it, because a shared task is a shared habit.
RevOps — Webhook tasks are Plus and Pro only and OpenAI names no Business or Enterprise availability. Reps will set these up on personal accounts against work inboxes. Have a policy for that before it is a discovery.
Event-triggered work only pays off if the instruction is precise about what to do with the event. Start from a scheduled prompt that already defines the input, the judgment and the output, then swap the timer for a trigger.
Two minutes, once a week. What changed in AI, and what to run because of it.