A daily, hand-checked feed of real use cases from public posts: what the bot does, how it's set up (schedule, connected apps, browser or desktop use), the template when the author shared one, and a link to the original post.
Drafted EU legal notices and a European Consumer Centre complaint until eufy paid a full refund.
Setup: Drafted the legal notices and ECC complaint, tracked the return parcel, kept the evidence organised and checked Reddit for similar cases. Refund landed two days after the offer.
Pulls new stream clips, renders 9:16 edits with captions, and queues daily posts for Shorts, TikTok and X.
Schedule: Daily
Setup: Exports both a music cut and a clean-audio cut; captions avoid overlapping existing on-screen text. Author says a template link is shared in replies.
At day's end it pulls every decision and to-do from Granola call notes into Linear, then prints a paper focus list each morning.
Schedule: End of day + every morning
Setup: Calls are transcribed by Granola; the author tells the bot at end of day to extract decisions and to-dos and file them as Linear tickets.
When Cursor cloud agents hit a usage limit, the bot built on its own computer and kept scheduled posts on time.
Schedule: Scheduled
Setup: News posts and two guide rewrites still went live on schedule.
Set up an Instagram profile for the author's iOS app and posts a new Grok Imagine reel every morning.
Schedule: Every morning
Setup: Connected to Instagram; creates each reel with Grok Imagine and uploads it. Author describes it as fully hands-off.
Keeps one case file per stuck order or refund, drafts each next message, and escalates step by step.
Schedule: Reminder when due
Setup: Escalates from a firm follow-up to a public post to the official consumer channel; reminds once when a follow-up is due.
Template: Shared by the author ↗
Asked before buying a fragrance; the bot found a 20% sale elsewhere, built a cart and saved about $50.
Surfaces a few X posts worth replying to around 8:30 each morning so the author skips the scroll.
Schedule: Daily ~8:30
Setup: The author still writes every reply.
Reads the personal calendar hourly and copies events marked “Team” to the shared team calendar.
Schedule: Hourly
One scout bot reads X on Monday; other bots wake on file changes to score the idea, open a PR and draft a deck.
Schedule: Monday 09:00 + file triggers
Setup: One clock (Monday 09:00) for the scout; every other bot triggers on a new line in LEDGER.md; spends and posts go through approval. Author reports dropping from 1,176 to about 60 runs a week.
Pulls Kit campaign results into an interactive dashboard, finds which topics perform best, and recommends what to send next.
Setup: Uses the Kit newsletter connector and Grok Bot Pages.
Took photos of a faulty wall connector, replied to Tesla's support email, and tracked the replacement shipment.
Setup: Author handed the bot the photos and the support email thread; it submitted the photos, replied, and tracked the shipment.
A Bash script runs the server checks; the bot reads its one-line result each morning and stops if it says OK.
Schedule: Every morning
Setup: Replaced a long morning checklist run by the bot with a 200-line script to save usage.
Adds every chore to a Linear project, researched a sprinkler blowout from photos, and found parts at Home Depot.
Setup: Keeps a running list of household facts like car year, make, model and oil filter.
Logs every promise with owner and due date, checks twice a day, and flags who has gone quiet.
Schedule: Twice daily + weekday mornings
Setup: CSV ledger built from Gmail, Calendar, Slack and calls; weekday morning brief. Author credits it with catching a stalled proposal.
Template: Shared by the author ↗
Picks new posts from 23 ranked engineering blogs with a one-line system-design takeaway, logs them to Notion and drafts X posts.
Schedule: Daily ~8 AM
Setup: Reads RSS and checks pages without feeds; remembers what was sent. Author posts by hand.
Template: Shared by the author ↗
Blocked a month of shifts with drive time on the calendar and keeps the family list in iPhone Reminders.
Setup: Added each work day plus an hour of drive time before and 30 minutes after. Uses the phone Calendar and Reminders access. Author trims scheduled routines to save usage.
Records each purchase into a Google Sheets family budget with categories and notifies the author's watch.
Schedule: On purchase
Setup: Example: a McDonald's coffee and a $777 Amazon brake-parts order were both logged and categorized automatically.
Turns the X feed and bookmarks into EPUBs with a morning summary, stored in a private repo.
Schedule: Every morning
Setup: Everything is kept in a private Git repo as a personal library.
Reads the news each morning and writes an adult brief plus two kids' editions from real sources.
Schedule: Every morning
Setup: Covers Germany, the author's region and the world, including English editions.
A bot named Kevin sends a morning digest of YouTube platform updates and strategy.
Schedule: Every morning
Template: Shared by the author ↗
Grok Bot messages Claude Code via its CLI, and Claude Code can message back.
Setup: Author says you can ask the bot to set it up.
Set up Obsidian as a plain-Markdown shared memory where several bots read, write and hand off work.
Setup: Each bot has its own folder, status page and append-only log; handoffs go through a shared inbox; one rules file governs all bots.
30 minutes before standup it reads everything relevant and hands over one page with agenda, scope and things to raise.
Schedule: Weekdays, 30 min before sync
Setup: Reads the calendar, Notion agenda, planning notes, Slack since yesterday, Linear progress and the engineering digest. The author says the prompt is on the card in the post.
A chief of staff for client priorities plus bots for production monitoring, data takedowns, inbox cleanup and Linear triage.
Schedule: Daily / weekly
Setup: Chief of staff reads Slack, Linear, GitHub, Gmail, Calendar and Notion; a monitor watches Vercel logs, the database, GitHub and support email; a privacy guard re-checks takedowns weekly; others triage spam, LinkedIn DMs, iMessage and physical mail via Earth Class Mail's MCP.
Every email is copied to the bot's own address; it only flags what needs a decision and checks spam twice a day.
Schedule: On email + twice daily
Setup: Gmail forwarding to the bot's claimed address wakes it on each email. It never replies on its own.
Checks each listing on price, schools and 5pm commute, sends passes to the realtor, then reviews disclosures.
Setup: Uses its own computer to pull Zillow photos, floor plans and sale history; sends to the realtor via the Slack connector; estimates reno costs.
Claude Code runs on the bot's own computer, and bot project managers direct it from GitHub issues.
Setup: Author logged into Claude Code on the Grok Bot computer.
One lead bot manages the rest: monthly expense reconciliation, 3D printing, site SEO, email drafts, TV control and more.
Schedule: Daily / weekly
Setup: Reconciles bank data into Power Apps; slices and sends 3D prints and watches them; sends Monday visitor stats; weather at 9am; logs overtime in Notion. Coding goes through Claude and Codex CLIs on his own machines.
Builds a branded interactive HTML company snapshot three times a day and reads, drafts and sends texts and emails.
Schedule: 3x daily
Setup: Key business software linked via API; replaced Google Calendar with a calendar inside the report.
A long client email forwarded to the bot's address became a broken-down project in Notion.
Schedule: On email
Setup: Uses the bot's own email address.
Checks WhatsApp for replies from pitched leads, drafts nudges for quiet ones, and closes anyone who says no.
Schedule: Routine
Setup: Routine checks WhatsApp; author gives it the list of who was pitched and when.
Reviewed every email with an online dog-house seller, found it wasn't authorized, and handled the back-and-forth until refunded.
Builds next week's workouts from Strava data, puts each day's session on the calendar, and flags track conflicts.
Schedule: Weekly + daily
Setup: Also warns when a football game is on at the track the author uses.
A coordinator, a Linear PM, a builder, marketing, sales, ideas, tech news and a morning security review of commits.
Schedule: Mornings and evenings
Setup: PM fleshes out Linear issues; builder picks up Todo issues after agreeing the approach; ideas are logged in Notion. Every routine only looks at what's new since its last run.
Scans Gmail daily for phishing, fake invoices and impostor alerts, with a 0-100 risk score and the red flags.
Schedule: Every morning
Setup: Reads current alerts from the FTC, FBI, BBB, CISA and AARP daily. Read-only: never clicks, replies or deletes.
Template: Shared by the author ↗
Watches personal inboxes, surfaces time-sensitive items, and drafts replies ready to send with one click.
Setup: School announcements, calendar events and bank updates get surfaced.
Wired ThermoWorks thermometers into the bot so it pings at the stall and when it's time to pull.
Setup: The bot found an open-source connector and wired it in. Author says it took about five minutes.
Added 5 weeks of leave, cleared 24 events, emailed every participant and made a to-do list, by voice while driving.
Setup: Author talked to Grok in the car, which handed the work to his bot team.
The bot has its own Fastmail mailbox, calendar, contacts and notes, and now answers forwarded mail live.
Schedule: Was every 15 min; now on new email
Setup: Previously a routine checked the inbox every 15 minutes; now a Fastmail forward rule to the bot's own Grok Bot email address triggers it instead.
The chief-of-staff bot's own email address receives signups, verification codes, receipts and newsletters.
Setup: Nothing triggers unless a routine is set; sending still needs approval.
Collects 5 posts across 7 chosen topics, summarizes them as 3-5 minute reads, and links each to the author's goals.
Schedule: Daily 6:00 AM
Setup: A Chief of Staff bot captures the links; a Summarizer bot writes the reads.
Built a ready-made bot for the author's There Lists app that puts ingredients on the right store list.
Setup: No official connector existed, so the bot built a workaround; sign in with Apple. The app pings when you walk into that store.
Pulls viral X content, drafts new videos and repurposes the author's long-form content.
Schedule: Daily
Handles emails, reorder reports, time cards, SEO and marketing each morning.
Schedule: Every morning
Setup: Owner runs the shop without IT staff.
Prints a daily paper with Parry Sound weather, news, events, the family calendar and school bus cancellations.
Schedule: Every morning
Checked with the Tokyo property manager in Japanese, then opened the Starlink return and refund ticket.
Setup: Author says he spent under 30 minutes total and barely opened Gmail or Starlink.
A published bot that delivers a local morning paper every day, with a printed weekend edition.
Schedule: Daily + weekends
Template: Shared by the author ↗
Had Cursor agents build a repeatable pipeline; now a topic in becomes a narrated, captioned MP4 in iCloud.
Setup: Claude Code writes the script and plan, Python draws animations, Kokoro narrates, ffmpeg adds music and captions, all on the Mac mini.
One email a day with the best new AI assistant use cases and how they are set up. Signup isn't open yet, and this form collects nothing.