Choose how a Grok Automation reports back
Pick how each Grok Automation notifies you when a run finishes so you see the result without hunting through history by habit. Official Automations in Grok states that you choose email, app notification, both, or neither if you prefer to open run history yourself. Every fire still opens a full conversation and stores it in run history whether or not a notification fires. Automations live on grok.com/automations and in the Grok iOS and Android apps; they are separate from Grok Bot routines. Create or open the job first with Create a scheduled Grok Automation, then set the report channel before you trust the schedule. More Automations jobs sit on the Automations hub.
What you need
A signed-in account on grok.com or the Grok mobile apps, an Automation that already has a clear brief and a schedule or email trigger, and a decision about where you will actually read the output. Email delivery needs an inbox you check; app notifications need the Grok app installed on the phone you carry. If the job should wake from inbox filters instead of a clock, set that with Set an email trigger on a Grok Automation before you tune the report channel.
Set the report channel
- Open grok.com/automations while signed in, or open Automations in the Grok mobile app.
- Select the Automation by name so you edit the saved job rather than a one-off reply inside an old run thread.
- Find the report-back or notification control on that Automation. Choose email, app notification, both, or neither.
- Save the Automation. Press Run now once so a real conversation appears in run history and you can confirm the channel behaved the way you expect before the next automatic fire.
- Open the run conversation from history. Confirm the brief used current data, met the output format, and stopped where you wanted. Adjust instructions on the Automations page if the run was weak, then Run now again.
Neither is a valid choice when you already open Automations on a fixed cadence; it is a weak choice when you will forget to look. Email alone suits a morning brief you read at a desk. App notification alone suits a short flag you want on your phone. Both suits high-priority filters where missing a fire is costly.
After you pick a channel
Treat the notification as a pointer into the run conversation, not as the full output. Continue the thread from history when you need a follow-up; a chat reply after one run does not rewrite the saved brief for later fires. To pause noisy jobs, reshape the brief, or remove the Automation, use Pause, edit, or delete a Grok Automation. For a manual check without waiting on the schedule, use Run a Grok Automation now.
Pitfalls
Leaving the channel on neither without a habit of checking run history means finished work sits unread. Editing only inside an old run conversation leaves the saved report setting untouched for the next fire. Expecting the notification body to replace the full run thread hides sources and follow-up context. Mixing this control up with Grok Bot notification settings sends you to the wrong product — Bot alerts live under the Bot app, while Automation report-back lives on the Automations page.