Collection · 6 use cases
Read-only watchers
Jobs where your dot only looks and reports: prices, competitors, mentions, pull requests, traffic. A safe way to try scheduled work.
Scheduled work is where dots differ most from a normal chat. These jobs are the easiest way to try it: each runs on a schedule, reports only what changed, and never acts on what it finds.
Why read-only first. A watcher can’t send, buy or change anything, so the worst case is a noisy report. That makes it a low-risk way to learn how your dot handles time zones, end dates and “nothing new this week” before you give it anything that reaches other people.
Tuning them. Most watchers use your dot’s own cloud browser, and OpenAI notes that some websites block cloud browsers or ask for extra verification. If a site won’t load, remove it from the list or check it yourself. Every prompt here has an end date; renew the ones that earned their place and let the rest expire.
-
Competitor pricing watch
Once a week your dot checks named public pricing pages in its cloud browser and reports only what changed, with before and after.
-
Watch prices for a drop
Once a day your dot checks the product pages you list and messages you only when a price falls below your target. It never buys.
-
Watch for brand mentions
Once a day your dot searches the public web for new mentions of your brand and reports each one with a link and a sentiment note.
-
Weekly topic digest
Every week your dot finds the five most important new developments on a topic you name, with links, and skips anything it already reported.
-
Open pull request digest
Every weekday morning your dot checks open pull requests in your repo and lists what waits on you, what's stale and what's failing.
-
Weekly traffic summary
Each Monday your dot reads the analytics export you drop in a Google Drive folder and summarizes top movers and pages that dropped.