Run a Grok Automation now
Fire a saved Automation immediately with Run now when you want a full test conversation before you trust the schedule or email trigger. Official Automations in Grok states that you can start a run yourself with Run now, which is handy for testing an automation right after you build it. Automations live on grok.com/automations and in the Grok iOS and Android apps; they are consumer Grok jobs, separate from Grok Bot routines on the Bot computer.
What you need
A signed-in account with at least one saved Automation that already has clear instructions, optional connectors or skills you intend to use, and a report channel you can check (email, app notification, both, or neither). Create the Automation first with Create a scheduled Grok Automation, Start a Grok Automation from chat, or Start a Grok Automation from a template. Email triggers need SuperGrok; Run now still works for testing scheduled jobs without waiting for the clock.
Start Run now
- Sign in and open grok.com/automations, or open Automations in the Grok iOS or Android app.
- Select the Automation by name so you see its instructions, schedule or trigger, connectors, and report settings.
- Confirm the brief still matches the job you want to test — rewrite anything that would waste a live connector call — then choose Run now.
- Wait for Grok to open a real conversation for this run; every fire is a fresh request with the same instructions and current data.
- When the run finishes, open it from run history, read the full thread, and decide whether to leave the schedule or trigger armed, or to pause, edit, or delete the Automation before the next automatic fire.
After the run
Treat Run now as your dry run for connectors and output shape. If the report channel is wrong, change it on the Automation before the next scheduled fire so you are not hunting for results in the wrong inbox. If the brief is close but the cadence is wrong, edit the schedule (once, daily, weekdays, weekly, monthly, or yearly in your timezone) rather than relying on manual runs. For inbox-driven jobs, pair this test path with Set an email trigger on a Grok Automation after Run now proves the instructions.
Pitfalls
Running now on a paused Automation may surprise you if you expected silence until resume — check pause state first. Leaving a broken brief armed after a failed Run now means the next scheduled fire repeats the same failure. Forgetting that each run is a full conversation makes it harder to reopen and continue from run history. Mixing Automations with Grok Bot routines confuses two products with different setups. Skipping Run now after you attach a live connector can burn a real side effect on the first automatic fire.