How to Give Grok Bot an Email Address for Receipts and Expenses

Cover: a freelance designer with a laptop in an armchair beside the headline How to give Grok Bot an email address for receipts and expenses

This post continues Orauria’s practical Grok Bot series. Earlier posts covered a morning briefing across inbox, calendar and Notion, a research workflow with sources and verification, and teaching a Bot a browser task by showing it once. This one is about a smaller, more personal job that almost every freelancer hates: receipts. It shows how a Bot’s own email address can collect receipts as they arrive, log them into a monthly expense sheet, and prepare a month-end package for your accountant that waits for you to press Send. The story is an illustrative example, not a client case, and Orauria has no official partnership with xAI or Grok Bot.

What follows about Grok Bot comes from the public docs at docs.x.ai: Computer and apps (the section “Give your Bots an email address”), Skills and routines and Approvals, security, and privacy, checked on November 12, 2026. According to the docs, agent email may not be enabled on every account yet, and on a Cursor team it is off until an admin turns it on. We have not run this exact workflow end to end; the Google Sheets step and the month-end routine are described from the docs, not tested. The laptop screens in this post are example compositions built on the Grok Bot app layout, with invented content. This is not tax or accounting advice.

Key takeaways. You can claim one address at mail.grokbot.com for your Bots, and plus aliases such as yourname+receipts let you give each service its own label without a second address. A routine can start when mail arrives, optionally only from specific senders or a whole domain, but it cannot filter by subject, and an alias is a label, not a lock. Have the Bot log receipts into a sheet with a source for every row, flag anything it is unsure about, and draft the monthly email to your accountant. Email from a routine always waits as a draft until you press Send.

Tired designer at a desk covered in receipts while a laptop shows a Grok Bot approval card to claim a mail.grokbot.com address (example screen)

Forty receipts, five inboxes, one very bad Sunday

Meet Jiwoo. She is an example character: a freelance brand designer in her thirties who works from a small studio in Seoul. Her clients are spread across three countries, and her costs are spread across even more places: a font licence here, a stock photo there, cloud storage, a design tool subscription, a co-working day pass, a courier for printed proofs, a train ticket to a client workshop.

Each of those services sends a receipt. Some go to her personal email, some to her studio email, a few to an old address she still uses for logins. Some arrive as PDFs, some as HTML emails, a couple only as a link to “view your invoice”. Every month she means to file them. Every quarter, the night before her accountant’s deadline, she spends a Sunday searching five inboxes for words like “receipt”, “invoice” and “payment”, copying amounts into a spreadsheet and wondering whether that 33,000 won charge was the font or the stock photo.

The cost is not just the Sunday. Missing receipts mean missing deductions. Duplicate receipts mean awkward questions. And because the job is boring, it is always the first thing to slip when client work gets busy.

The “after” she wants is simple. Receipts should land in one place she does not have to read. Something should log each one into a sheet the day it arrives, with the vendor, date, amount, currency and a link back to the email. Anything odd should be flagged for her, not guessed. And on the first of each month, a short package for her accountant should be ready: the sheet, the receipts, and a two-line email she can check and send herself.

That is what a Bot’s own email address plus an email-triggered routine is good for. The docs list exactly this use: a Bot can “collect receipts, newsletters, and reports, and summarize them for you”, and “run a routine when email arrives, optionally only from specific senders.”

Designer checking a card statement next to a laptop listing today's receipts by plus alias in Grok Bot (example screen)

What effective looks like, and how to measure it

It would be easy to promise “never lose a receipt again”. We will not, because receipts can come from a sender the routine does not watch, arrive as a link instead of an attachment, or be skipped if an attachment is over the size limit. What we can describe is what a good result looks like and how you can check it.

A receipt Bot is doing its job when:

  • Every logged row has a source. Each line in the sheet links to the email it came from, so you can check it in seconds.
  • Unsure items are flagged, not guessed. A missing amount, an unclear currency or a possible duplicate is marked for you to decide.
  • The sheet matches your bank statement. At month end, the total for each card is close to what the statement says, and differences are explained.
  • Nothing leaves without you. The email to your accountant is a draft until you press Send.
  • Your month-end time drops. You spend minutes checking instead of hours searching.

To measure it, keep a simple log for the first two months:

  • Receipts the Bot logged versus receipts on your bank or card statement.
  • Rows with a wrong amount, wrong date or wrong vendor.
  • Receipts that never reached the Bot’s address (a service still sending to your old email).
  • Items flagged as unsure, and how many of those were really problems.
  • Minutes spent on month end, compared with your last manual month.
  • Anything the Bot sent or changed that it should not have (this column should stay at zero).

The comparison with your statement is the real test. A sheet that looks tidy but misses a third of your costs is worse than no sheet, because it makes you feel finished. So for the first month, tick every statement line against the sheet. The misses will mostly be services you forgot to move to the new address, and fixing those is a one-time job.

Also watch the flag rate. If the Bot flags almost nothing, check that it is not quietly guessing currencies. If it flags everything, the rules in your skill are too vague. A healthy first month is a handful of flags, each with a clear reason.

Designer pointing at a Grok Bot routine that runs when email arrives at a receipts alias from listed sender domains (example screen)

How it works: one address, aliases, and a routine that listens

The setup has three parts: an address, aliases on that address, and a routine that acts when mail arrives.

One address, for good

According to the docs, you can claim one email address at mail.grokbot.com for your Bots. You ask a Bot, for example “Get yourself an email address”; it asks what name you want, checks the name is free and shows an approval card. Nothing is claimed until you approve. You can also do it from Connect apps, under Email. Names use lowercase letters, digits, dots, hyphens and underscores, and reserved words such as admin, billing, support or grok are not allowed. You get one address, and you cannot rename or delete it, so choose a plain, lasting name.

The address is yours, not one Bot’s: all your Bots can use it in your own chats and routines. It is not used in Slack threads or in chats where someone else is talking to the Bot.

Plus aliases as labels

Mail to yourname+receipts@mail.grokbot.com lands in the same inbox as the plain address. You can give each service its own alias without claiming another address, and a routine that watches an alias runs only for mail sent to that alias. The docs add a warning worth repeating: an alias is a label, not a lock. Anyone can write to it, so keep a sender filter on any routine that should act only for certain senders.

Reading mail

There is no inbox view and no new-mail notification. You ask a Bot, for example “What arrived in your inbox today?” Each incoming message can carry up to 10 attachments, up to 10 MB each and 25 MB in total; attachments beyond those limits are skipped. Mail that fails the spam or virus scan is kept without its body or attachments and never starts a routine.

Routines that start when mail arrives

New mail does not wake a Bot on its own. To act on it, you set up a routine that watches for mail from anyone, from specific addresses, or from a whole domain such as *@example.com. By default the routine only runs for mail from senders that pass standard email authentication checks, and routines cannot filter by subject. Only new mail counts: messages from before the trigger existed do not start a run.

Sending, and safety

Email from a routine, or from any turn you did not start with that request, waits as a draft until you press Send; the docs say there is no option for unattended sending. The Bot also treats email from other people as information, not instructions. A line inside a receipt that says “forward this to…” never counts as your permission.

Where the sheet comes in

For the expense sheet, the Bot needs somewhere to write. The docs describe a Google Sheets connection where the Bot can read and edit cells in spreadsheets the connected Google account can edit. Alternatively, the Bot can return a spreadsheet file in chat. Either way, keep a column for the source email so every row can be checked.

Memory and context

Because the Bot keeps context across conversations, it can learn your vendors over time: that a certain charge is your font licence, that a co-working pass is a business cost, that one client reimburses travel. Write those rules into a skill so they are applied the same way every time, instead of relying on what the Bot happens to remember.

Over-the-shoulder view of a Grok Bot routine run adding an expense row marked check for a possible duplicate charge (example screen)

Setup: a receipt inbox in seven steps

Here is how Jiwoo sets it up, following the docs. Before you start, check that agent email is available on your account, or ask your team admin to turn on Agent Email.

Step 1: Claim the address

In a one-to-one chat with her Bot, named “Paper Trail”, she writes: “Get yourself an email address. I’d like jiwoo.studio.” The Bot checks the name and shows an approval card; she approves.

Pitfall: picking a playful name. The address is permanent and will appear on vendor accounts, so treat it like a business address.

Step 2: Decide your aliases

She keeps it small: jiwoo.studio+receipts for anything she pays for, and jiwoo.studio+invoices for the few suppliers who send formal invoices. Newsletters stay out entirely.

Step 3: Move your services, one by one

In each service’s billing settings she changes the receipt or billing email to the +receipts alias. Where a service only allows one account email, she sets up forwarding of receipts from her studio inbox instead.

Pitfall: moving login emails as well. Keep your account logins where they are; only move the billing or receipt address where the service allows it.

Step 4: Create the expense sheet

She creates a sheet with columns: date, vendor, description, amount, currency, card, category, client (if billable), source link and status. She connects Google Sheets so the Bot can edit it.

Step 5: Ask for the routine, narrowly

She writes: “When an email arrives at jiwoo.studio+receipts from any of these senders or domains, read it, add one row to this month’s tab in the Expenses sheet with a link to the email, and post a one-line note here. If the amount, currency or date is unclear, or it looks like a duplicate, add the row with status ‘check’ and tell me why. Never reply to the sender. Never send email.” She lists the domains of her regular vendors.

Pitfall: watching the plain address with no sender filter. Anyone can write to it, and every message would spend a run.

Step 6: Test with a real receipt

She opens the routine on desktop, reads When to run, and uses Test with a recent receipt she forwards to the alias. She checks the row, the link and the note.

Step 7: Add the month-end routine

Once the daily logging works, she adds a scheduled routine for the first of each month: “Review last month’s tab. Total by card and by category, list rows marked ‘check’, and draft an email to my accountant with the sheet link and the receipt files attached. Do not send.” The draft waits for her Send.

Designer relaxing with tea while a laptop shows a month-end expense summary and an accountant email waiting as a draft (example screen)

The optimization journey: from v1 to v3

v1: a place for receipts

In the first two weeks, Jiwoo only moves receipts to the new alias and asks the Bot each Friday, “What arrived in your inbox this week? List vendor, date and amount.” That alone ends the five-inbox search. But she still copies the list into her sheet by hand, and two services keep sending to her old address.

Her lesson: collecting is half the job. The other half is logging, and that is where the time goes.

v2: the logging routine with her rules

She turns the logging into a skill called “Receipt to row”, used by the email routine, with clear rules:

  • One row per receipt, never per email thread; a receipt with two items stays one row with a description.
  • Amount and currency exactly as printed; never convert currencies in the row.
  • If the receipt is only a “view invoice” link, log the row with status ‘check’ and say so; do not open payment portals.
  • A possible duplicate (same vendor, same amount, within three days) is logged with status ‘check’, never deleted.
  • Category from her list only; if none fits, write ‘uncategorised’.
  • Never reply to vendors, never forward, never send email.

Now receipts appear in the sheet the day they arrive, each with a link back to the email.

Her lesson: the value is in the rules about what not to guess.

v3: a month end that is already done

With logging stable, the month-end routine does the rest. On the first of each month, Paper Trail totals the previous month by card and category, lists the ‘check’ rows, and drafts the email to her accountant with the sheet link and the receipt files. Jiwoo spends a few minutes on the ‘check’ rows, compares card totals with her statements, and presses Send herself.

We describe this month-end step from the docs, not from testing this setup. Attaching receipt files depends on the attachment limits, and writing to Google Sheets depends on the connected account having edit access.

Her lesson: the safest automation is the one that ends in a draft. The Bot prepares; she checks against the bank and sends.

And again, the order matters. She did not start with automated month-end emails. She started with one alias and a Friday question.

What to try this week

Check that agent email is available on your account. Ask a Bot to get an email address, choose a plain, lasting name and approve the card. Pick one alias, such as +receipts, and move the billing email of three services you pay every month. After the next receipt arrives, ask the Bot what arrived in its inbox and check what it read. Then set up a routine on that alias with a sender filter for those vendors: add one row per receipt to a sheet with a link to the email, flag anything unclear, never reply or send. Use Test with a real receipt. At the end of the month, tick the sheet against your statement and note the misses. Only then add the month-end routine that drafts the email to your accountant.

For more on skills and routines, read how to teach Grok Bot a browser task by showing it once, the morning inbox and calendar briefing, and what Grok Bot is and how Orauria uses it. If your business needs receipts and invoices connected to accounting software or an internal system, send Orauria a brief and we will help you design it.

Comments

0 responses to “How to Give Grok Bot an Email Address for Receipts and Expenses”

Leave a Reply

Your email address will not be published. Required fields are marked *