Nine Grok Bot Routines That Run Your Day While You're Not Looking

If Hands On: Grok Bot was the org chart, this is the calendar. Routines are the part of Grok Bot that matter when you are not staring at the screen: a Bot wakes on a schedule, does a job it has already proven it can do by hand, and leaves you a numbered list to act on — or waits for approval if the next step would send, delete, book, or spend.

xAI calls this "always-on agents." The four creators who have spent real hours in the beta make it more concrete. Matthew Berman schedules inbox triage for 7:30 a.m. Peter Yang runs travel fare checks on Monday mornings and research digests on a daily cadence. Claire Vo turns successful chats into standing jobs across a chief of staff and specialists. Alex Finn keeps a revenue researcher on a loop without giving it send rights.

Below are nine routines worth installing first. For each one: who demonstrated it, what it does, a schedule, a starter prompt or description block, and the permission rule to paste in before you connect anything. Run every routine manually once. Correct it. Then schedule it. Never promote a chat that failed in front of you into a job that runs while you sleep.

Global permission sentence (put this in every bot description unless you deliberately remove it later):

Do not send, delete, archive, cancel, unsubscribe, purchase, book, move files, change permissions, or message anyone outside this chat without my explicit approval. Show me a numbered list of what you plan to do and wait.

---

1. Overnight inbox triage — daily 7:30 a.m.

Source: Matthew Berman
Bot: Inbox / email agent
Connector: Gmail (Plugins → Add → Connect)

Berman's standing job scans overnight mail and the previous day's leftovers, archives the obvious noise, batches what needs a human, and asks for decisions. He does not hand it the send key by default.

Starter prompt (after Gmail is connected and the approval sentence is in the description):

Every day at 7:30 a.m. local time, review new Gmail since my last review plus any unfinished items from yesterday. Archive pure notifications and receipt spam. Group everything that needs me into a numbered list of at most 10 items. For each item: sender, subject, one-line why it matters, and a draft reply if one is needed. Do not send, delete, or label beyond archive without my say-so.

Turn the successful run into a routine. Keep drafts as drafts until you trust the voice.

---

2. Morning YouTube / niche research — daily

Source: Peter Yang
Bot: YouTube researcher
Connector: Browser / computer

Yang's researcher finds outlier videos in his interests, reports channel performance against a recent baseline, surfaces themes and top comments, and delivers a morning watch list. Schedule it for the hour you actually open YouTube, not for midnight vanity.

Starter prompt:

Every weekday morning, find outlier YouTube videos from the last 14 days in [your niches]. For each of the top 5: title, channel, link, view velocity vs that channel's recent baseline, the theme in one sentence, and the three most useful comments. End with three angles I could film next. Number everything. Do not subscribe, comment, or message anyone.

---

3. X Scout — weekly report

Source: Peter Yang
Bot: X / social scout
Connector: X plugin or browser

Yang's weekly scout prompt is already structured well enough to steal. Scope, grouping, and a forced creative ending are the whole lesson.

Starter prompt:

Find the most viral X posts from the last 7 days in my niche and create a weekly report with the top 10 tweets from people I follow, engage with, or bookmark grouped into a few categories. Include a full tweet copy, link, and your analysis. And end with three content ideas for me to tweet about next.

Schedule it for Sunday evening or Monday morning. Ask for a numbered list so follow-ups are "expand 3 and 7."

---

4. Travel fare watch — Mondays 9:00 a.m.

Source: Peter Yang
Bot: Travel concierge
Connector: Browser (Google Flights)

Yang hands the bot trip requirements, dates, and legs, then schedules a Monday 9:00 a.m. re-check. In his example it returned a Tokyo itinerary roughly $2,700 cheaper than his open-jaw plan. He talks about booking and check-in as future steps — keep approval on purchases and bookings.

Starter prompt:

Every Monday at 9:00 a.m., re-check flights for this trip: [paste dates, cities, cabin, max stops, hard constraints]. Compare against my current hold: [paste itinerary or price]. Report only if you find a meaningfully better option (price drop of at least $X, or same price with better timing). Include full link, total, and what changed. Do not book, hold, or enter payment details without my approval.

---

5. Subscription and Drive cleanup — weekly

Source: Peter Yang ("Marie Kondo")
Bot: Cleanup / finance hygiene
Connectors: Gmail + Google Drive (optional: bank MCP only if you accept high privilege)

Yang connects Drive and Gmail, then asks for categorized numbered lists of paid subscriptions and large or abandoned Drive files. He explicitly forbids move, delete, unsubscribe, cancel, or alter without approval. His refinement that makes the list usable: max 10 items per category, no random labels, and only show Gmail unsubscribes, Drive deletions, and subscriptions he actually wants to cancel. He then instructs by number.

Starter prompt:

Once a week, scan Gmail receipts and Google Drive for: (1) paid subscriptions I may not need, (2) Drive files larger than [N] MB that look abandoned, (3) newsletters I never open. Cap each category at 10 numbered items. For each: what it is, evidence, recommended action, and risk if wrong. Do not move, delete, unsubscribe, cancel, or alter anything without my numbered approval.

---

6. Chief-of-staff multi-inbox sweep — daily

Source: Claire Vo
Bot: Chief (or your named coordinator)
Connectors: Gmail (and Slack only after voice is trusted)

Vo's Chief sweeps multiple inboxes and Slack workspaces — triage, research, draft follow-ups, coordinate specialists. Her discipline before that access: she tested the model's writing until it sounded like her.

Starter prompt / description block:

You are my chief of staff. Each weekday morning, sweep [list inboxes / Slack workspaces]. Produce: (1) what needs me today, numbered, max 10; (2) what you drafted for my review; (3) what you handed to specialist bots and why. Prefer drafts over sends. Do not send external messages without approval. Match my tone; if unsure, ask.

Then schedule the sweep. Use group threads so specialists report back into the same conversation.

---

7. Family morning newspaper — daily

Source: Claire Vo (TradBot)
Bot: Family / TradBot-style
Connector: optional browser for weather/sports; output designed for paper

TradBot's job is a kitchen-table newspaper for Vo's kids — offline, physical, not another dashboard. The routine teaches a useful design rule: decide the artifact before you decide the tools.

Starter prompt:

Every morning by 7:00 a.m., produce a one-page family newspaper for [kids' ages/names]: weather, one local or sports blurb, one silly comic caption, and one question for the breakfast table. Keep language age-appropriate. Output as clean printable text. Do not post anywhere or email anyone unless I ask.

Print it. That is the point.

---

8. Revenue / prospect research loop — daily or every weekday

Source: Alex Finn (Cindy)
Bot: Revenue ops researcher
Connector: Browser; CRM only if available and scoped

Finn's Cindy researches prospects and companies to support revenue work. The important part of his setup is what she cannot do: he does not give her permission to send email. Pair her with an orchestrator that consumes the research and asks you before outreach.

Starter prompt:

Each weekday, research [N] new prospects in [ICP]. For each: company, why now, relevant trigger in the last 30 days, likely buyer, and a draft outreach note in my voice. Number 1–N. Do not send email, LinkedIn messages, or CRM updates without my approval. Never invent contact details.

If you later add a Hermes or other research agent as a tool to your orchestrator, keep the same approval gate on anything that leaves the building.

---

9. Calendar and meeting prep — daily evening or morning

Source: Matthew Berman (calendar + meeting summary chapters)
Bot: Calendar / meeting prep
Connector: Calendar plugin; meeting notes or transcript as input

Berman shows a calendar agent and a meeting-summary flow. Exact permission scopes vary by connector — verify write access before enabling it. The safe routine is read-heavy: tomorrow's agenda plus prep briefs, with event creates or edits held for approval.

Starter prompt:

Every evening at 8:00 p.m., list tomorrow's calendar events in order. For each: purpose, people, what I owe them, and a 5-bullet prep brief. If I attach notes or a transcript after a meeting, produce decisions, owners, and due dates as a numbered list. Do not create, move, or cancel events without my approval.

---

How to install any of these without regret

1. Create the bot with a human name and paste the global permission sentence into the description.
2. Connect only the connector that routine needs.
3. Run the starter prompt once by hand. Fix tone, caps, and false positives.
4. Ask: "Turn this into a routine on [schedule]. Keep the same approval rules."
5. Let it run for a week before you remove a single restriction.
6. Prefer numbered outputs so your replies stay short: "do 2 and 5," "expand 3."

xAI also describes teach-by-following — watch a workflow, save it as a routine, learn corrections. Use that when it works; use explicit schedules when you need reliability. Official eligibility and separate Bot usage are on the xAI announcement; dollar prices and numeric limits are not published there.

For the broader setup path — advisor bot, org design, connectors, cloud computer, migration from OpenClaw — start with Hands On: Grok Bot.

---

Sources

• Claire Vo (How I AI) — 7 Grok Bot agents I use every day —
• Peter Yang — Grok Bot: 5 Must-Try Use Cases for Work and Life —
• Alex Finn — 8 Grok Bot use cases I promise will change your life —
• Matthew Berman — 11 Grok Bot Use Cases That Feel Like Cheating —
• xAI — Introducing Grok Bot — x.ai/news/introducing-grok-bot

Schedules, prompts, and connector steps above are reconstructed from creator demonstrations and captions as of early September 2026. Grok Bot is in early beta; verify permissions in the app before granting them.