ChatGPT Work Adds Webhook-Triggered Tasks for Gmail, Slack and GitHub

Scheduled tasks can now react to supported app events

OpenAI updated ChatGPT on August 25, 2026 with webhook-triggered tasks in ChatGPT Work. Instead of repeatedly polling for a change, a supported connected app can trigger a task when an event occurs.

The currently documented webhook triggers are specific: new Gmail messages, Slack channel messages and GitHub pull-request activity.

Plus and Pro users can ask Work on web, iOS and Android to respond to those events. OpenAI gives examples such as summarizing an email when registration opens or drafting follow-up steps after client feedback arrives in Slack.

This should not be described as a universal webhook platform for every connected app. The release notes name those three supported event families.

Approval requirements remain part of the workflow

OpenAI says actions that require approval pause until the user reviews them. For Slack monitoring, @ChatGPT must be added to each monitored channel.

Those controls matter because event-driven agents can otherwise turn an incoming message into a chain of actions without the user noticing the transition from reading information to changing an external system.

Teams using webhook tasks should still constrain instructions, connected accounts, channel scope and downstream actions. Event payloads and messages can contain untrusted content, so an incoming event should not automatically be treated as trusted authorization.

Scheduled tasks can also be shared

OpenAI also added task sharing. Free, Go, Plus and Pro users can share a scheduled task so another person can inspect and customize the instructions and, where applicable, the schedule.

Recipients connect their own apps and create an independent copy. A shared webhook-triggered task requires access to Work and the recipient's own connected app.

That is a useful permission boundary: sharing a workflow definition does not mean sharing the original creator's Gmail, Slack or GitHub connection.

Free users can create up to three active scheduled tasks, but their tasks run once or recur no more than once per day using flexible scheduling windows. Free and Go users cannot create webhook-triggered tasks.

Why event-driven tasks matter for agents

A scheduled agent normally has to wake up and check whether anything changed. Webhooks invert that pattern: the external event initiates the work. That can reduce needless checks and make workflows respond closer to the time a change occurs.

The practical value is strongest for workflows such as triaging selected email events, summarizing activity in designated Slack channels or reacting to pull-request changes.

The security model is just as important as the convenience. Teams should verify exactly which event triggered a task, what data the connected app exposes, whether external content can influence tool calls, and which consequential actions still require human approval.

This release makes ChatGPT Work more event-driven, but the scope remains deliberately bounded to the supported connectors and permission controls documented by OpenAI.