Create a scheduled Grok Automation

Build a saved job on grok.com/automations so Grok runs the same brief on a schedule you choose, then reports back in a full conversation. Official Automations in Grok covers schedules, email triggers, Run now, and report channels on grok.com and in the Grok iOS and Android apps.

Automations are consumer Grok jobs, separate from Grok Bot routines on the Bot computer. If you already have a chat brief you like, you can also start from chat or start from a template.

What you need

You need a signed-in account on grok.com or the Grok mobile apps, plus a clear job that states what to check, what done looks like, and what to send you. Bring optional connectors or skills only when the job should use them on every run. Scheduled automations are available broadly; email triggers need SuperGrok — see Set an email trigger on a Grok Automation.

Create the Automation

1. Open grok.com/automations while signed in, or open Automations in the Grok iOS or Android app, then start a new Automation and give it a name you can find later in the list.
2. Write the instructions the way you would brief a coworker, and put the output format in this brief: sections, length, links to cite, and anything the run should skip.
3. Attach files only when the job needs fixed context every run; prefer connectors for live sources, and type @ to mention a connector the job should use on every fire when the work needs mail, files, or another connected tool.
4. Pick a schedule in your timezone — once, daily, weekdays, weekly, monthly, or yearly — and choose a clock time you will actually open the report.
5. Choose how it reports back: email, app notification, both, or neither if you prefer to check run history yourself, then save and press Run now once so a real conversation appears in run history before you trust the schedule.

Every later fire is a fresh request with the same instructions and current data, so a one-off chat reply after a run does not rewrite the saved brief.

After the first Run now

Open the run conversation and check whether Grok used the right sources, met the output format, and stopped where you wanted. Edit the saved instructions on the Automations page if the run was weak, then Run now again. When the manual run looks right, leave the schedule alone and wait for the next automatic fire. To stop, change, or remove the job later, use Pause, edit, or delete a Grok Automation.

Name note

Marketing calls these Automations. Some older links still say Grok Tasks and point at grok.com/tasks, so prefer Automations when you teach the feature.

Pitfalls

Vague instructions produce vague runs, so put the output format in the saved brief before you rely on the schedule. Skipping Run now hides prompt and connector bugs until the first automatic fire. Mixing this up with Grok Bot routines sends you to the wrong controls: Bot schedules live under a Bot's Routines panel, while Automations live at grok.com/automations. Leaving the report channel on neither without a habit of checking run history means you will miss finished work.