How to Automate Tasks in Your Business with Grok Bot
Recurring work that runs with zero operator time.
By Valente Labs
About an 8 minute read · No coding needed to follow along
This is how we use Grok Bot for business work at Valente Labs. Grok Bot is an AI agent from SpaceXAI. You hand it jobs like a teammate, and it works on its own cloud computer, day and night.
We gave it one recurring job. That job now runs every month, automatically, with zero time from the business operator. The operator just reads a recap. If you want to automate your business with AI, here’s the pattern we follow.
1. Why recurring business work stays manual
Every business has jobs that come back on a schedule: invoices, reports, reminders, and follow-ups. They are simple, but they rarely run themselves. Three gaps keep them manual:
- Someone has to be there. Nothing happens unless a person sits down to do it.
- Someone has to sign in. Every site needs a login, every time.
- Every run is a little different. Steps live in people’s heads, so mistakes creep in.
2. How Grok Bot automates the work: three pillars
We close each gap with one pillar. Together they let Grok Bot run a process from start to finish.
An always-on agent
Grok Bot runs on its own cloud computer and is always available. A scheduled run doesn't need anyone present.
Persistent authentication
Logins stay connected through 1Password and Composio OAuth. The agent can act without anyone signing in each time.
Programs for full control
Small programs (scripts) handle each step the same way every time. The flow is predictable, repeatable, and auditable.
The tools, in plain words:
- 1Password is a password manager. It keeps logins in locked vaults, and the agent gets its own.
- Composio links AI agents to apps like Gmail and Google Drive. You grant access once, and the link stays live.
3. Case study: AI workflow automation with zero operator time
Here’s the real process we automated. A small rental business shares a home with a housemate. The housemate pays a fair share of the shared utilities: electric, gas, water, and internet.
Before. Each round took hours of operator time. Someone signed in to several websites, downloaded the bills, and did the math in a spreadsheet. Then they built a statement, added a charge in the rent app, and wrote an email. Notes were scattered, and we fell behind.
Now. Grok Bot runs the whole round on its own, once a month. The operator's only touchpoint is reading the recap email. They step in only if the run stops on an exception.
What the run touches
Utility websites
Downloads each new bill.
Its own 1Password vaultRent-collection app
Creates the charge.
Its own 1Password vaultGoogle Drive
Files the statement and the bills.
Composio OAuthGmail
Sends the notice and the recap.
Composio OAuthNo password ever shows up in a chat, a screenshot, or a file. On vault sites, the agent pastes one field at a time, then clears the clipboard. For Google, the owner granted access once, on Google’s own page.
The run, step by step
Each step is tagged by who does the work. Program means a small script that gives the same result every time. AI means the agent uses judgment. Template means fill-in-the-blanks text.
- Start (routine). A routine kicks off the run once a month. No one needs to be there.
- Load the rules and check access (AI and program). The agent reads the written procedure (the SOP), past decisions, and the housemate’s record. A script confirms the vault and the Google link work, without printing a secret.
- Gather the bills (AI). The agent signs in to each utility site and downloads any new bill. It reads the dates, the amount, and the usage. A bill counts toward the period it was issued in.
- Do the math (program). A script works out the housemate’s share. A second, separate check must match it to the cent.
- Check for exceptions (AI and program). The agent compares the amount with the same period last year and confirms every bill is in. If anything is off, the run stops here.
- Build the statement (program). A script makes the statement and a full packet with the original bills. It reads the totals back out of the PDF to make sure they match.
- Create the charge (AI, with fixed rules). The rent app has no direct link for software, so the agent uses its browser. It first checks that no charge exists for this period. Then it adds one charge with the statement total and due date, named like past charges. The app tells the housemate a charge is waiting.
- File the packet (program). A helper uploads the full packet to a private Drive folder. Only the housemate can open it, and there’s no “anyone with the link” access.
- Send the notice (template and AI). A template writes the email. The agent smooths the tone but never changes a number, date, or link. A clarity check confirms the dates and that only the statement is attached. Then it sends and confirms the email is in Sent.
- Send the recap (template). The owners get a short summary of the round.
- Log it (program). The agent updates the billing log and saves a new version.
The split, in plain words. Everyone who lives in the home pays an equal share of each bill, scaled by the days they lived there. Each share is rounded to the cent, then added up.
(amount minus credits) × (days the housemate lived there ÷ days on the bill) ÷ people living there = the housemate's share of that bill
Figure 1. One run, start to finish
Eleven steps in order. Start the routine. Load the rules and check access. Gather the bills. Do the math, with a second check. Check for exceptions: if anything is unusual, the run stops and drafts plus a summary go to the owner. Otherwise: build the statement, create the charge in the rent app, file the packet in Drive, send the notice to the housemate, send the recap to the owners, and update the log.
What the run produces
The statement is three pages, and every number traces back to a real bill.
Who it's for, the period, and the amount due.
Each bill with its dates, days, amount, and the housemate's share, then the total.
The method in a few bullets, plus a link to the source bills.
The full packet adds the original bills after the statement. It lives in the Drive folder, not in the email.
The notice is short and plain. Each amount sits on its own line, and the due date is written out with the day of the week. Here’s the shape, with placeholders:
Example notice, placeholders only
Hi [Housemate],
Here is the utility statement for [period], attached. The source bills are in our private shared folder: [folder link]
[Period]: [amount]
The charge is in [rent app], due [weekday, month, day].
The next statement should arrive around [date].
Thanks!
The recap goes to the owners right after the notice is sent. It lists what was sent and when, the amount, the due date, where the files are, and what’s next.
When something is off
The run stops on any of these:
- a question or dispute from the housemate
- a new fee or line item
- a change in how the housemate pays
- an unusual amount, or a check that fails
- a missing or unclear bill
- a tool or login failure
The agent checks for these before it creates the charge or sends anything, so nothing reaches the housemate. If a tool fails later in the run, it stops right there and checks what already went out before trying again. It never guesses at a missing bill, and it never moves money. Instead, the owner gets drafts and a short summary to review.
The next three sections show each pillar at work in this case.
4. Pillar one: an always-on AI agent
A routine is a scheduled task, like a calendar reminder that does the work itself. Ours starts the billing round once a month, automatically (step 1). No one has to be there.
Three things keep the agent dependable between runs:
Memory
It keeps a dated log of decisions and preferences, like business rules and the email style.
A written guide
The process is a written checklist with notes for each step. A short "skill" file points each new session to it (step 2).
Backups
The guide and the programs live in private GitHub storage that keeps every version. If the agent's computer is wiped, a setup script restores everything.
5. Pillar two: persistent logins with 1Password and Composio
Signing in reliably was the hardest part, not the math. Every site has its own login, and some ask “are you a robot?” The fix was logins that stay connected, so the agent never waits for a person.
Figure 2. Logins that stay connected, with no passwords in chat
Three lanes. Utility sites: a 1Password vault just for the agent, then copy, paste, and clear the clipboard, then the login page. Gmail and Drive: a one-time setup on Google's own page, then Composio holds a revocable permission the agent uses for Gmail and Google Drive. Sites that block bots: handled by hand, outside the billing run.
- Kept locked away
- One-time or manual
- Where the agent ends up
Utility sites and the rent app
A vault just for the agent. The agent has its own read-only 1Password vault with only the logins it needs (steps 3 and 7). It pastes each field from the vault, then clears the clipboard. The password never appears in a chat or a screenshot.
Gmail and Drive
OAuth through Composio. Google won't let the agent's browser sign in. So the account was connected once through Composio (steps 8 to 10). If the connection ever expires, it's renewed from a link, outside the run.
Secrets and bot blocks
Secrets stay out. Passwords never go in GitHub. One site we use refuses the agent's browser. It isn't part of the billing run, and we don't sneak around it.
OAuth, in plain words: instead of sharing your password, you sign in once on Google's own page and grant the app access. Google gives the app a permission slip for email and Drive. You can cancel it any time in your Google settings.
6. Pillar three: small programs for full control
Every step runs through a small program or a fixed template. Business rules, like special cases and fees, live in the SOP (the written procedure). The program applies them the same way every time.
Programs do the math and build the statement (steps 4 and 6). The charge follows fixed rules, after a duplicate check (step 7). A template writes the notice. The agent polishes the tone but never changes a number, date, or link (step 9).
The run ends with a recap email to the owners, summarizing what it did (step 10).
Why programs give full control
Predictable
Same look and same rules every time, so nothing gets forgotten.
Repeatable
Each month runs the same steps with new bills.
Auditable
Automatic checks (tests) confirm past rounds still match what was billed. A separate recount matched to the penny.
7. Results from the case
Zero operator time
The round runs every month, automatically. The operator just reads the recap.
Steps in only on exceptions
If something is off, the run stops and the owner gets drafts to review.
Caught up
We cleared the backlog of overdue rounds.
Accurate and safe
Every line traces back to a source bill. No passwords in chat, and no secrets in backups.
8. Playbook: automate your business with AI
Here’s the takeaway for any business. This path works for almost any recurring task, not just billing. Use it to set up an AI agent for small business work of any kind. Move one process along it, a step at a time.
Process → SOP → AI skill + Grok Bot → Routine
An SOP is a standard operating procedure: the written steps plus the rules. Tick these off as you go.
The end state: an always-on agent, logins that stay connected, and programs you control. The work runs with zero operator time. The operator reads the recap and steps in only on an exception.
Valente Labs article · Written with Grok Bot. The case study leaves out personal details, logins, and real amounts.