Skip to content
← Guides

How to monitor ChatGPT scheduled tasks

Scheduled tasks are great until one quietly skips a day. ChatGPT can't run curl, so the check-in has to come from somewhere else. Here's what works today, honestly.

The problem with scheduled tasks

ChatGPT scheduled tasks run on OpenAI's side. When one doesn't run — a platform incident, a paused task, a usage limit — there's usually no error to catch. You find out when you notice the brief didn't arrive, sometimes days later.

People running many tasks describe the same chore: opening each one every morning to check that it actually ran.

What works today: relay the notification email to your ping URL

Did It Run? check-ins today are HTTP requests to a watch's unique ping URL. A ChatGPT task can't make that request itself, but it can email you when it finishes, and an automation tool that watches your inbox can turn that email into a ping:

  1. Create a watch with the same schedule as the task, e.g. every weekday by 9:15am in your timezone, with 15–30 minutes of grace.
  2. Turn on email notifications for the task, so each completed run emails your account address.
  3. In an automation tool that can watch your inbox (n8n, Make, or Zapier on a paid plan), trigger on new emails from ChatGPT that mention the task, then send an HTTP POST to the watch's ping URL with the email text as the body.

If the task doesn't run, no notification arrives, no ping arrives, and you get an alert. It needs that second tool, so it isn't zero-setup, but it works with what's live today.

Coming soon: email check-ins

The simpler setup, forwarding the notification straight to a watch's own email address with an inbox rule and no other tool, needs email check-ins. They aren't live yet; they're coming soon. Until then, there's no way to watch a ChatGPT task with Did It Run? without a relay like the one above.

Catch "ran, but said nothing"

Ask the task to end its answer with a fixed marker such as BRIEF-OK, send the notification text as the ping body, and set the marker as the watch's required keyword. If the notification includes the task's reply and that reply is an apology, a refusal, or an empty result, you get an empty alert.

One roll-call for every agent

If you run tasks in ChatGPT, routines in Claude, and workflows in n8n or Zapier, the daily roll-call digest puts all of them in one email: ✅ what ran, ❌ what's missing, ⚠️ what came back empty.

FAQ

Can a ChatGPT task ping a URL directly?

Not reliably. A task with browsing can sometimes open a URL, but don't count on it as a heartbeat. Relaying the task's notification email to the ping URL through n8n, Make or Zapier is the dependable option today.

Can I just forward the notification email to a watch?

Not yet. Email check-ins are coming soon. Today every check-in is an HTTP request to the watch's ping URL.

Will this expose my emails?

Only what your relay sends in the ping reaches us. We store the first 500 characters, the size and the item count for history and checks, and you can delete a watch and its history at any time.

Does it work with Gmail?

Yes, as long as your relay tool can watch your Gmail inbox. n8n, Make and Zapier all have Gmail triggers.

Know the next time it doesn't run

Know when your AI agents and automations didn't run. Free for 3 watches.

Start free