Start a Grok Automation from a chat message
Ask Grok in a normal chat to set up a repeating job, then open the saved Automation so you can confirm the brief, schedule, and report channel before the first automatic fire. Official Automations in Grok shows you can create automations straight from chat — for example, asking Grok to check the news every morning and flag anything about pricing.
This path is for consumer Automations on grok.com and the Grok apps. Grok Bot routines are a different product; create those inside a Bot. For a blank form on the Automations page, see Create a scheduled Grok Automation. For suggested starters, see Start a Grok Automation from a template.
Ask in chat
- Open a Grok chat on grok.com or in the Grok iOS or Android app, then state the job and the cadence in one message that includes what to check, what done looks like, the output shape, and when it should run in your timezone.
- Let Grok create the Automation; when it confirms, open grok.com/automations (or Automations in the app) and select the new entry by name.
- Read the saved instructions carefully and edit them if the saved brief is vaguer than what you said in chat, because every later run uses the saved text rather than the rest of the chat thread.
- Confirm the schedule (once, daily, weekdays, weekly, monthly, or yearly) and how it reports back — email, app notification, both, or neither — then press Run now once so a full conversation lands in run history before the schedule fires on its own.
If the job should watch your inbox instead of a clock, switch to an email trigger after you open the Automation — Set an email trigger on a Grok Automation. Email triggers need SuperGrok.
Mentions and tools
In the saved instructions, type @ to mention a connector the Automation should use on every run. Attach files only when the same document must travel with every fire, and prefer connectors for live mail, drives, or other accounts so each run sees current data.
Keep the brief durable
Every run is a fresh request with the same instructions and current data. Put standing rules in the Automation's instructions: output format, sources to prefer, topics to ignore, and when to stop and report failure. A follow-up you type only inside one run conversation does not stick for the next fire. When you need to pause, reshape, or remove the job, use Pause, edit, or delete a Grok Automation.
Pitfalls
Trusting the chat setup without opening the Automations page leaves you exposed to a weaker saved brief than the one you spoke. Leaving the output format only in the original chat message means later runs will not see it unless you move that format into the saved brief. Expecting a chat follow-up after one run to change future fires will disappoint you — edit the Automation itself. Confusing Automations with Grok Bot routines sends schedule work to the wrong product surface.