A routine tells one bot to run a job on its own, on a schedule or after an event. Grok Bot routines are where it starts saving you real time, and also where mistakes can repeat while you sleep. Here’s how to set them up so they don’t.
1. Don’t automate a task that hasn’t worked yet
Grok Bot’s own docs put it in this order: do the task once, make it reliable, save the method as a skill, and only then automate it. If a task needs you to correct the bot every time, a routine just repeats those mistakes on a schedule.
Quick test: have you done this task with your bot at least twice and been happy with the result both times? If not, keep doing it by hand for now.
2. Write a routine brief with seven parts
Ask the bot that should own the job, and include:
- Owner: which bot runs it.
- Schedule and time zone: “every weekday at 8:00 AM Eastern”.
- Input: where the data comes from.
- Output: what you get and where it’s delivered.
- Approval boundary: what it must never do without you.
- Missing data: what to do if a source is down.
- Stale data: what counts as too old to use.
Here’s one you can adapt:
Every weekday at 8:00 AM Eastern, run my Daily brief skill. Post the brief in this chat. Don’t send email or change my calendar. If Calendar is signed out or data is older than today, say so instead of using old data.
After you save a routine, the bot sums up what it does and who receives the result. Read that summary. It’s your chance to catch a wrong time zone or the wrong recipient.
3. Choose schedule or event on purpose
Schedules suit regular reports: daily briefs, weekly digests, monthly audits. Event triggers suit things that should happen when something arrives: a webhook, a message in a channel, or an email to a bot’s tagged address (bots can use a form like name+shop@, and a routine on that tag runs only for its mail).
Keep event rules narrow. The docs warn against broad listeners like “every new message”: they create noise, use up your allowance and make it more likely the bot acts on something irrelevant.
4. Test before you turn it on
Use Test after creating or editing a routine. A test run does real work: it can open websites, change files and use your connected apps. So test with safe inputs, and keep anything that sends, posts, buys or deletes behind an approval. Check that it picked current data, matched the format, linked its sources, stopped at the approval point and reported failures clearly.
5. Know the limits
- A bot can own up to 50 routines, and the app keeps the 20 most recent run records for each.
- Schedules must be at least five minutes apart.
- As of October 23, 2026, all your routines together can run up to 300 times an hour, and each routine up to 200 times.
- Deleting a routine is immediate and can’t be undone. Pausing is the safer choice while you decide.
- If you’re away for a long time, Grok Bot may ask whether to keep routines running and pause them if you don’t answer.
6. Manage your Grok Bot routines by asking
You create and change routines by asking the bot in chat. To review them on desktop, open the bot’s details from its name at the top of the chat; each routine there can be paused, resumed, tested, edited or deleted.
The short version
Make it work by hand, save it as a skill, write a seven-part brief, test with safe inputs, keep sends and spends behind approval, and pause before you delete.
Sources: Grok Bot docs: Skills and routines · Grok Bot changelog (v0.75.5, Oct 23, 2026)
Swarm School is independent and not affiliated with Grok Bot’s makers. Features change often; check the official docs if something looks different.