Start a Grok Automation from a template

Open the Automations page, pick a suggested template, then rewrite the brief and schedule so the job matches your sources and output before you trust automatic runs. Official Automations in Grok notes that the Automations page has suggested templates to start from, and that any automation can later be paused, edited, or deleted.

Templates are a head start for consumer Automations on grok.com/automations and in the Grok apps; they are not Grok Bot role templates. For a blank Automation, see Create a scheduled Grok Automation. To turn a chat request into an Automation, see Start a Grok Automation from chat.

Pick and customize

1. Sign in and go to grok.com/automations, or open Automations in the Grok iOS or Android app, then choose a suggested template that is close to the job you want (for example a morning brief or inbox triage shape).
2. Rename the Automation so it is obvious in the list next to your other jobs, then rewrite the instructions in your own words while keeping any useful structure from the template.
3. Add your sources, the output format, topics to skip, and where the run should stop; attach files only if every run needs the same fixed context, and type @ to mention connectors the job should use on every fire when live data matters.
4. Set the schedule in your timezone — once, daily, weekdays, weekly, monthly, or yearly — pick a time you will open the report, choose how it reports back (email, app notification, both, or neither), then save and press Run now once and read the full run conversation before you leave the schedule on.

Treat the template as a draft. The first Run now is the real acceptance test for sources, tone, and output shape.

When a template is the wrong start

Skip templates when your job is narrow and already clear in your own words, and create from scratch instead. Skip them when the work belongs on a Grok Bot with a persistent computer, plugins, and Bot routines, because Automations do not give you that Bot computer. Use an email trigger when the signal is an incoming message rather than a clock; email triggers need SuperGrok.

After it is saved

Open run history after Run now and check evidence, length, and whether connectors fired. Edit the saved instructions on the Automations page if the template language is still too generic. For pause, resume, deeper edits, or delete, follow Pause, edit, or delete a Grok Automation.

Pitfalls

Leaving template wording untouched produces generic reports once the schedule starts, so rewrite the brief in your voice before you rely on automatic fires. Skipping Run now hides template defaults for connectors and report channel until a scheduled fire surprises you. Scheduling before the output format is in the saved instructions means later fires will not see a one-off chat tweak. Expecting Bot-computer behavior from an Automation template will disappoint you, because files and browser sessions on Grok Bot stay on that product.