Grok Bot Routines Examples for Ops, Inbox, and X
The short answer
A Grok Bot routine runs a skill on a schedule. A useful one names the bot, the time and time zone, where the inputs come from, what "done" looks like, what it must not do without you, and what to do when a source is missing. Three examples cover most solo businesses: a morning ops brief, inbox and calendar, and a weekday X draft.
Morning ops brief
Weekdays at 8:00, the founder bot checks revenue pace against the monthly goal and whether the site is up, then posts a short brief. Fridays at 4:00 it reviews the week and suggests experiments. Tuesdays and Thursdays at 10:00 it finds prospects and drafts outreach. The brief is a report. Sending, refunds, and price changes wait for you.
Inbox and calendar
A chief-of-staff bot triages mail at 7:30 and again at 12:30, and saves reply drafts. At 5:00 on weekdays it writes a one-page brief for tomorrow's external meetings. Sunday at 6:00 it flags conflicts and overload. It does not send mail, and it does not accept or move events.
X drafts, not auto-posts
A content bot scans public X on weekday mornings at 8:30 and leaves 3 to 5 drafts. At noon it finds conversations and drafts replies with links. Monday at 9:00 it reports what performed. It can read public posts without your X login. It does not post, like, follow, or DM until you approve the exact text.
Confirm six things before you enable it
Grok Bot asks you to confirm the routine before it runs. Check the owning bot, the schedule and time zone, the input source, the expected result, the approval boundary, and what happens if a source is down. Schedules need at least five minutes between them. A bot can own up to 50 routines, which is more than you want. Start with two or three.
Test run, then leave it
Use Test run once before you enable the routine. A test run does the real work, so point the first one at something low stakes. If a source is missing, the routine should say so and skip that number, not reuse yesterday's figures. Approvals that nobody answers expire after about 10 minutes, so do not schedule a send for a time you are offline.
Paste a setup instead of inventing the schedule
The Solo Founder CEO, Chief of Staff, and Content & X Growth setups each include the routines above, plus the skills they call, a connector checklist, and Auto-review rules. Paste them, fix the time zone, and run one by hand. The founder CEO guide on this site walks through the profile and the goal if you want that piece first.
Related
- Template: Grok Bot Setup: Solo Founder CEO
- Template: Grok Bot Setup: Inbox & Calendar Chief of Staff
- Template: Grok Bot Setup: Content & X Growth
FAQ
What is a Grok Bot routine?
A scheduled message to a specific bot. You describe when it runs, what it should read, what it should return, and what it must not do without approval. The bot confirms those details before you enable it.
Do test runs spend usage?
Yes. Test runs and live routines both use your Grok Bot allowance, which resets weekly. Schedule only the checks you will actually read.
Can a routine post or send on its own?
Only if you tell it to, and you should not. Write the approval boundary into the routine, and add Ask-first rules for sending, posting, and spending. A routine that only drafts is the one to start with.
Agent Drop: the weekly newsletter
One new agent template, one tool worth using, three links. Free, weekly.