Verified against ChatGPT · 2026-07-29
Set up a recurring ChatGPT Task that is worth getting notified about
A scheduling brief that gives a recurring ChatGPT Task an explicit worth-notifying threshold, so it stops sending a ping every single run regardless of whether anything actually changed.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Create a scheduled task with this exact setup. SCHEDULE Every weekday at 8am, my local time EACH TIME THIS RUNS, DO THIS Check for any news mentioning our main competitor, Northwind Logistics, in the last 24 hours WHAT COUNTS AS WORTH NOTIFYING ME ABOUT Only notify if the news involves a product launch, a funding round, or a pricing change, not routine PR RULES - If nothing meets the notify threshold this run, send a single short line saying so. Do not send a full report with "nothing new" padded into it, and do not stay silent, since I need to know the task actually ran. - Keep the notification itself under 3 sentences. I am reading this on a lock screen, not opening a document. - Do not repeat something you already flagged in a previous run unless Check for any news mentioning our main competitor, Northwind Logistics, in the last 24 hours explicitly asks you to track it over time. - Every notification must end with one line stating what it checked and when, so a silent failure is obvious rather than looking identical to nothing happened. Confirm the schedule and the first run's exact instructions back to me before saving.
Customize the highlighted detailsoptional — the prompt above already works
Why this works
A Task runs the same underlying instructions on a schedule and messages you when a run completes, executing entirely unattended, which means the entire design problem has to be solved upfront, unlike a live chat where you can redirect a bad answer the moment you see it. Stating an explicit worth-notifying threshold turns a recurring task from a guaranteed ping on a timer into an actual filter, which is what keeps a daily or weekly Task useful instead of becoming the first notification you mute because it fires every run regardless of whether anything changed. The instruction to send a short line rather than stay silent when nothing qualifies fixes a specific ambiguity in unattended automation: silence could mean nothing happened, or it could mean the task failed to run at all, and those two states are indistinguishable to you unless the task is explicitly told to report both outcomes differently. Requiring confirmation of the schedule and the exact first-run instructions before saving also catches a common setup mistake early, a natural-language cadence like every Monday getting parsed as every weekday, rather than discovering the misreading three silent, wrongly-timed runs later.
What you get back
Confirmed schedule: every weekday at 8:00 AM. First run will check for Northwind Logistics news from the prior 24 hours and only notify on a launch, funding round, or pricing change. Sample notification if nothing qualifies: "Checked Northwind Logistics news as of 8:00 AM Tue — nothing met the notify threshold today."
Verified against
ChatGPT GPT-5.1 (Tasks) · 2026-07-29
Changelog
- 2026-07-29 — Initial publish, verified against ChatGPT GPT-5.1 Tasks.
Building this for real?
This is a free starting point. If you'd rather have what Scult builds built and running for your business, that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
