How this helps you
You can show the Bot a job instead of writing instructions, which helps with sites that have no API.
I'm going to show you how I do [task]. Watch the recording, turn it into a skill, then run it once and show me each step before we schedule it.
What they did
@EssenseViral showed Grok Bot learning a workflow by watching it once, with no prompt writing and no API docs. The example was chasing unpaid invoices: 58 seconds and 5 steps. Open every unpaid invoice from the week, log each amount in a billing portal that has no API, mark the overdue ones in a finance sheet, draft a polite reminder to each late client, and post the total owed to a finance thread. The Bot saved it as a routine called Invoice Chaser that now runs every Monday on its own cloud computer, even with the laptop closed. The author counts it as 47 clicks a week saved.
Who it's for: Anyone with a repetitive browser task, especially on sites with no connector.
Before you start
- Logins for every site in the task, saved where the Bot can use them (see the Vault tip).
- A task with clear steps you can check afterwards.
How to try it
- Pick a task you already do the same way every week, ideally one that touches a site with no API.
- Start a recording and do the task once at normal speed, including every click (Nate Herk's concepts video shows this flow).
- Stop the recording. The Bot turns what it watched into a skill.
- Run the skill once by hand and check every step.
- Ask the Bot to schedule it as a routine, for example every Monday.
What to expect
A saved routine (in the author's case 'Invoice Chaser') that repeats the same 5 steps on schedule and reports back.
Common mistakes
- Skipping steps while recording. Recording captures steps people forget to write down, so do the whole thing.
- Scheduling before one clean manual run.
Related tips
- Do it by hand, save a skill, then schedule: Most automations break because they're scheduled before they've worked once.
- Make your first task boring: Start with something checkable, then add one thing at a time.
- Write the outcome, not the recipe: Describe what you want; pasted tool calls break by week two.
- Open your Bot's screen to watch or help: Each Bot works on a real desktop you can open, watch, sign in on, and take over.
- Expense Bot: inbox receipts into a Notion table: Sonny Sangha's expense Bot scans two inboxes for receipts, logs them in Notion, and learns to fetch portal invoices with Teach a task.
- Teach a task the smart way: describe it first, record only the gap: Most of a browser job can be explained in chat. Record a 20 to 60 second clip of only the part the Bot can't work out, then add anti-jobs before you schedule it.
- Build a three-Bot starter team: Scout, Shopper and Desk: One Bot researches and checks sources, one shops and stops before checkout, one learns a weekly task by watching you once.
- Turn a repeated job into a script the skill runs: Do a weekly job once with your Bot, check it, then have it rewrite the job as a plain script and save a skill that runs the script and reports in two lines.
Worth knowingThe time and click counts are the author's own. Any routine you teach can be shared as a template, per the post. Also mentioned by @Virexontic.Next in your path →Vault: logins, cards and contact info
Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot skills tips