Scheduled tasks and automations

# Scheduled tasks and automations

ChatGPT can wake up on its own, run a prompt on a schedule, and message you the result, so "every Monday, summarize this week's industry news" becomes a recurring job instead of something you remember to type. This feature is called Scheduled Tasks (often just "Tasks"), and it turns ChatGPT from a thing you poke into a thing that reaches out to you.

This lesson goes deep on how Tasks actually work, how to wire one up well, where they break, and when to graduate to the APIAPIApplication Programming Interface: a standardised interface that lets applications communicate and exchange data without knowing each other's internal workings.View full definition → instead.

What a scheduled task actually is

A Task is a saved prompt plus a schedule plus a delivery mechanism. When the schedule fires, ChatGPT runs that prompt in a fresh, isolated conversation on the server side (you do not need the app open), then notifies you with the output via in-app notification and, if enabled, email or push.

Three things matter and are easy to get wrong:

• Tasks run without you in the loop. No mid-run clarifying questions. The prompt has to be complete and unambiguous on its own.
• Each run is a clean slate for the conversation, but it still has access to your account-level memory, custom instructions, and any Connectors you've authorized.
• There is a cap on how many active Tasks you can have. The exact limit varies by plan and changes over time, so check your account rather than assuming a number.

The official reference lives at help.openai.com. For the broader agent feature set this slots into, see openai.com.

Setting up the Monday news brief

Let's build the real thing. Goal: every Monday at 8:00 AM, get a tight summary of the past week's developments in your industry, scannable in 60 seconds.

Step 1: Write the prompt as a standalone job

Since there's no follow-up, the prompt carries all the structure. Open a normal chat and type something like this:

> Every Monday at 8am, search the web for the most significant developments from the past 7 days in enterprise AI tooling. Return exactly 5 bullets, each one sentence, ordered by importance. After each bullet, add a source link in parentheses. End with one line: "Worth watching:" and a single forward-looking item. If nothing notable happened, say so plainly instead of padding.

Notice what's doing the work:

• A real trigger phrase ("Every Monday at 8am"). ChatGPT detects the scheduling intent and offers to create a Task.
• An explicit tool instruction ("search the web"). Tasks can use ChatGPT's web search, but only if the prompt makes clear it should. Don't assume.
• A fixed output contract (5 bullets, one sentence each, sources, one closing line). Recurring output you'll skim should look identical every week.
• A failure instruction. Telling it what to do on a slow news week prevents hallucinated filler.

Step 2: Confirm and refine the schedule

When ChatGPT proposes the Task, it shows the parsed schedule. Adjust the time and recurrence if it guessed wrong. You can also create or edit Tasks from your profile menu under the Tasks view, where every active and paused Task is listed.

If you want to be precise about cadence in your prompt, plain English works ("the first Monday of each month", "every weekday at 7am"). ChatGPT translates it; you verify it.

Step 3: Scope it inside a Project (optional but smart)

If you run this brief for a specific client or domain, create the Task from within a Project so it inherits that Project's custom instructions and files. A Task born inside a Project titled "Acme competitive intel" can be told to weight Acme's competitors automatically, no repetition needed.

Reviewing and tuning the output

The first run is a draft, not a deliverable. Treat the first two or three Mondays as calibration.

What to check:

• Did it use the tool you expected? If the brief reads like it came from training data, not this week, the web search didn't fire. Make the search instruction more forceful and add a date anchor ("only items from the last 7 days").
• Is the format stable? Drift in length or structure means your contract is too loose. Tighten it ("exactly 5 bullets", not "a few bullets").
• Are the links real? Spot-check them. If sources are weak, instruct it to prefer primary sources and to skip any item it can't link.

To edit, open the Task and revise the prompt directly. You don't recreate it. You can also pause a Task (useful during a holiday) and resume later.

A clean tuning loop:

1. Read Monday's output.

2. Note the single biggest flaw.

3. Edit the prompt to fix exactly that one thing.

4. Wait for next run, repeat.

Resist rewriting the whole prompt at once. You won't know which change helped.

Making Tasks more powerful: Connectors and the agent

A web-search brief is the easy case. Tasks get genuinely useful when they touch *your* data.

Connectors

Connectors link ChatGPT to external systems (Google Drive, Gmail, GitHub, Outlook, and others, depending on availability and plan). A Task can read from a connected source at run time. For example:

> Every Friday at 4pm, check my connected Google Drive folder "Weekly reports", summarize any document modified this week into 3 bullets each, and flag anything mentioning "delay" or "blocked".

Now the Monday brief or Friday digest is grounded in your actual files, not just the public web. Authorize Connectors once at the account level; the Task uses them on every run.

The ChatGPT agent

For multi-step jobs, the ChatGPT agent can browse, click, fill forms, and operate a virtual computer to complete a task end to end. A scheduled agent run can do things a single prompt can't, like navigating a site that has no clean search.

The tradeoff: agent runs are slower, can hit login walls or CAPTCHAs, and may pause for your confirmation on sensitive actions. For an unattended scheduled job that needs zero human input, a focused prompt with web search is usually more reliable than a full agent run. ReachReachThe number of unique people exposed to your message in a given period. Unlike impressions, reach counts each person once, no matter how often they see it.View full definition → for the agent when the task genuinely requires interaction, not just retrieval.

When to leave ChatGPT and use the APIAPIApplication Programming Interface: a standardised interface that lets applications communicate and exchange data without knowing each other's internal workings.View full definition → instead

Scheduled Tasks are excellent for *personal*, *human-readable* automations delivered to *you*. They hit a ceiling fast when you need any of the following:

• Delivery somewhere other than the ChatGPT app (post to Slack, write to a database, trigger another system).
• Strict, machine-readable output that downstream code can parse every time.
• Volume, many runs or many users, beyond personal limits.
• Version control and testing of the prompt itself.

At that point you move the schedule out of ChatGPT and into your own infrastructure (a cron job, a serverless function, a workflow tool), and call the OpenAI API on each tick. You provide the scheduling; the API provides the intelligence.