ChatGPT Scheduled Tasks and Webhook Automation: From Timed Reminders to Event-Driven Workflows

ChatGPT scheduled tasks (Scheduled tasks) are ChatGPT's built-in automation: define a task in natural language, let it run on a time schedule, or -- as of 2026-08-25 -- trigger it automatically from Gmail, Slack, and GitHub webhook events. This article covers the difference between the two trigger generations, how to wire the three event sources, the per-plan limits, and the pre-launch event-source check that prevents the most common failure: a task that is created but never fires.

Note: the product facts in this article (event types, limits, sharing rules) were verified line-by-line against the official ChatGPT Release Notes (docs-checked version); the pre-check commands come from the official GitHub and Slack documentation.

1. Two Trigger Modes: Time Schedules vs Webhooks

The selection rule in one line: fixed rhythms use schedules, event responses use webhooks. "Give me a report at 9am every day" is a schedule; "summarize PR activity in our repo as it happens" is a webhook.

2. Limits and Plans: Check This Table Before Creating

Experience-value note: the official documentation explicitly states the Free cap ("up to 3 active tasks", "once per day") and that "Free and Go cannot create webhook tasks"; the exact caps for Go / Plus / Pro are not published -- go by what ChatGPT shows in-product. On Free, spend the 3 slots on the highest-value tasks and consider Plus for event-driven needs.

3. Pre-Check the Event Source Before Launch

The number-one cause of "created the task, it never fires" is a dead event source. The chain is "external event -> ChatGPT Work -> task run"; any broken link looks like silent non-firing. So verify both ends from the command line first.

Verify the GitHub PR source (confirm the repo you will monitor is reachable and has activity):

curl -s "https://api.github.com/repos/OWNER/REPO/pulls?state=open&per_page=5" | jq '.[].title'

If this lists open PR titles, the repo and access are fine. Swap in the OWNER/REPO of the repo your task will monitor and eyeball that it actually has PR activity.

Check one PR's key fields (confirm the exact monitored object is visible):

curl -s "https://api.github.com/repos/OWNER/REPO/pulls/123" | jq '{title, state, author: .user.login}'

Verify the Slack outbound webhook (confirm your workspace allows webhook delivery):

curl -X POST -H 'Content-type: application/json' \
  --data '{"text":"ChatGPT task webhook pre-check"}' \
  https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXX

Swap in your own incoming webhook URL; seeing "ChatGPT task webhook pre-check" in the channel means the pipe is open. Only after Slack-side success should you connect the app inside ChatGPT.

Both commands come from the official GitHub and Slack documentation -- they are generic pre-checks that verify "the event source side is alive"; the ChatGPT-side connection state is governed by the app authorization inside ChatGPT Work.

4. Writing the Task: Instructions Decide Output Quality

After connecting apps in ChatGPT Work, write the task in natural language. Three habits that stabilize output:

• Specify the output structure: "summarize each PR's title, author, and current status in a table" -- same principle as structured prompting: the more specific, the steadier.
• Specify scope and cadence: for webhook tasks, "only open PRs", "only today's mail"; for schedules, "weekdays at 9am".
• Specify what happens after: report only, or also suggest next actions -- otherwise the closing behavior drifts run to run.

5. Sharing and Collaboration

A task is not done when you build it. Per the official sharing mechanism: Free / Go / Plus / Pro can all share tasks via link, recipients can review and customize the instructions, connect their own apps, and create an independent copy -- your original is untouched. One restriction to remember: running a shared webhook-triggered task requires the corresponding Work access, so check a teammate's plan before sharing a webhook task to a Free account.

6. Troubleshooting

Frequently Asked Questions

1. What is the difference between a schedule and a webhook trigger?

A time-scheduled task "runs when the time comes" -- daily briefings, weekly summaries, fixed rhythms. A webhook task "runs when something happens" -- new Gmail messages, Slack channel messages, or GitHub PR activity start it automatically. The former is cron thinking, the latter is event-driven; pick by task nature.

2. Can Free users use scheduled tasks?

Yes, with limits: up to 3 active tasks, each running at most once per day, and no webhook-triggered tasks. Time schedules and receiving shared tasks are available on Free. Event-driven automation requires Plus or Pro.

3. Which event sources do webhook tasks support?

Three official sources: new Gmail messages, Slack channel messages, and pull request activity in a GitHub repository. Connect the app and pick what to monitor inside ChatGPT Work. Webhook tasks can be created on web, iOS, and Android (Plus / Pro).

4. After I share a task, can teammates change mine?

No. Recipients can review and customize the task instructions, connect their own apps, and create an independent copy -- your original task is untouched. Note that running a shared webhook-triggered task requires the corresponding Work access.

5. What should I check before launching a webhook task?

Pre-check the event source: verify from the command line that GitHub PR queries and your Slack webhook actually produce events (commands in this article), confirm the monitored repo / channel is right, then connect the app and create the task in ChatGPT. Launching without source checks is the number-one cause of "my task never fires."

6. Where do task results show up?

After a task runs, results are available inside ChatGPT. Recipients of a shared task get the copy's results in their own conversations.

Next Steps

• When did webhook triggers ship, and what else updated? Read OpenAI Ecosystem Week 41 Flash (2026-08-28/29): Cursor Cutoff, Google Accounts, DALL·E Sunset.
• Want the full tour of ChatGPT's product capabilities? Read ChatGPT Complete Guide (2026): From Beginner to Power User.
• Memory and project organization for teams? Read ChatGPT Projects Complete Guide: File RAG, Custom Instructions, and Team Collaboration.