Grok Bot for property ops: bills, utilities and a platform switch

You can hand a Grok Bot the back-office chores that eat a property manager's week: sending every emailed vendor bill into AppFolio, turning a phone photo of a mailed water bill into an entered bill, and checking that each unit's utilities got paid. This playbook follows one property management company that runs all three today, and shows how to set up the first one with a copyable prompt. It fits anyone in operations who lives in an inbox full of invoices, not only property managers.

Not tested: The Daily Bot has no AppFolio account, vendor inbox or bank linked to a Grok Bot, so we haven't run any of this. Everything below comes from the linked posts and Cursor's docs.

Who runs it#

The setup belongs to @ChrisTwiggsPM, Chris Twiggs, listed as Company President of Blair Allen Property Management on the Blair Allen team page. His X bio says the company manages property in South Dakota, Montana and Arizona. On Oct 8 he posted his roster of 20 numbered Bots (two still being built) and how he picks their jobs: "Admin work is a misuse of those valuable labor hours!" His rule for each one: "Figure out what you are hiring for, hire a bot, train that bot, verify results, then trust but verify going forward".

What ops uses it for#

• Emailed invoices. AppFolio can enter a bill you email to it. Its engineering blog says Smart Bill Entry lets managers upload PDF invoices "by forwarding an email to a specific inbox" (AppFolio). The catch, per Twiggs on Oct 13: "Appfolio can read attachments, but not an attachment on a forwarded email, so can't simply forward to AppFolio's email for bill entry". So his Bot "takes all invoice emails once per day, scans the bill and email body for anything needing attention (vendors will often leave notes or ask questions in the email) then takes the attached bill and emails it to the platform for payment". It then replies to the vendor with "received, thank you!", labels the email "invoice" and "removes from the inbox" (post).
• Mailed city bills. Trash, water and sewer bills "are more often than not still mailing invoices and we dont get electronic copies". Now, he says, "we take a picture of it in Grok Bot, it emails to Appfolio" (post). He later clarified that "it takes the bill image, converts to PDF, and then emails to Appfolio" because "Appfolio doesn't accept JPG" (post).
• Utility payment checks. His Rental Bill Pay Bot has "READ ONLY BANK ACCESS", "Watches all of our units and ensures all bills are paid, especially utilities", and "Logs into each utility provider to confirm". It "already caught one with a running toilet, water bill was $100 higher than normal" (post).
• Reconciliation and inspections. A Bank Reconciliation Bot "Double checks bank reconcile for all accounts" and "Watches for price increases in services" (post). An Inspection Tracker "Watches appfolio for completed inspections. Schedules next inspection for 6 months out in Todoist" (post).
• A platform switch. Moving from Buildium to AppFolio, "Only gross income moves forward to the new platform", so he "Had Grok bot go to old platform and download monthly detailed expenses, P&L's, cash flow, and all invoices for every owner". The Bot put them in a Google Drive folder per owner, emailed each owner the folder, and is "set to do the same on January 2nd". It asked each owner whether to share the folder with their accountant, and only for "The one's that responded with accountant info and approval to send" did it email the accountant, copying the owner (post). It is also "moving all accounting activity for October from old platform to new" (post).

Why it matters at work#

Because AppFolio won't read a forwarded attachment or a JPG, someone otherwise has to open each invoice email, pull the bill, send it in, thank the vendor and file the email, and handle every paper bill by hand. In this setup one Bot does the daily sweep and a phone photo covers the paper. Twiggs says Grok Bot has "basically replaced a full time admin position at our property management company at this point" (post). That's his own estimate, not a measured figure. Bills still land in AppFolio's own approval and payment step, so a person still decides what gets paid.

Set it up#

Our suggested order follows his "train that bot, verify results" rule and Cursor's advice to "Start with a one-time task, make it reliable, save the method as a skill, and only then automate it" (Cursor docs).

1. Create one Bot for bills. Give it the job and its limits in the first message: what it may send, and that it never approves or pays.
2. Sign it in. Twiggs's Bot "logs in through browser so I can keep tabs on what it's doing more easily. No API access" (post). When a site asks for a password or two-factor code, "The Bot hands you the computer", per Cursor's docs. Connect your email from Connect apps if a plugin exists for it.
3. Find your AppFolio bill-entry address and paste it into the prompt below.
4. Run the prompt once by hand on one day's mail and check every bill that reached AppFolio against the original.
5. Make it a routine. Ask the Bot to run the same instruction once a day. A new routine "waits for its next scheduled time", so use Test to try it now; "A test does real work", per the routines help page.
6. Add paper bills. Snap the bill in the Bot's chat and ask it to convert the image to PDF and email it to the same address.

Once a day, go through every email in my inbox from the last 24 hours that contains a vendor invoice or bill. For each one: 1) Read the bill and the email body, and list anything that needs a person: a question, a note, a changed amount, a past-due notice, or a property you can't match. 2) Save the bill as a PDF (convert photos or JPGs to PDF first) and email it as a new message, with the PDF attached, to our AppFolio bill-entry address: [your address]. Don't forward the original email. 3) Draft a reply to the vendor that says only "Received, thank you!" and leave it in drafts. 4) Label the email "invoice" and archive it. Don't approve, pay, or edit anything in AppFolio, and don't delete any email. When you finish, give me one list: each bill sent (vendor, property, amount, link to the email), each item that needs me, and anything you skipped and why. If no invoices came in, say so in one line.

Twiggs's Bot sends the vendor thank-you itself. Our prompt leaves it as a draft, in line with Cursor's advice to "keep sending, purchasing, deleting, publishing, and production changes behind approval" (docs). Switch to sending once a week of drafts looks right.

Gotchas#

• Check that the mail arrives. On Oct 9 he warned that "Grok Bot emails get flagged as spam by Gmail" after his lead Bot sent him a test (post). Confirm AppFolio actually entered the first few bills, and ask a vendor whether your thank-you arrived.
• It copies your mistakes. On the October transfer, he says the only mistake he has seen was "copying a mistake we had made and duplicating it. Even then it flagged it and questioned it, then we fixed it" (post). Ask for a list of anything that looks duplicated instead of a silent copy.
• Keep bank access read-only. Both of his money Bots say "READ ONLY BANK ACCESS", and he "Will be expanding on this as my comfort level with bot and financials improves". Grok Bot's Finance integration is read-only by design: "Access is read-only, Grok Bot never sees your logins, and you can unlink anytime", per @bot.
• API access may depend on your AppFolio plan. Another AppFolio user, Curt Bagne, wrote that "appfolio locks down the API unless you pay for the higher tiers". Twiggs replied that his company is on a higher tier but "I just dont trust the bot enough yet". The browser route works on any plan you can sign in to.
• Sign-ins drop. His biggest problem across Bots is "getting signed out and failing to sign back in. Google and Facebook are the biggest ones that cause problems. Using 1password as helped" (post). If you add 1Password, read our note on the current reconnect bug first.
• Every Bot shares the same logins. "Every Bot on your account uses the same computer: browser sessions, files, and command-line credentials are shared", per Cursor's docs. A bank or AppFolio session one Bot opens is open to all of them.
• Tabs and usage pile up. He has seen his Bots with "literally 50+ tabs open", so "Every morning he tells the bots to shut down unused tabs" (post). He pays for "the $100 per month Grok plan" and went over only "because of a big project bot did for me" (post); on Oct 13 he said he is "probably going to switch to the $200 per month plan" (post). "Each run spends usage", per the routines help page, so a once-a-day sweep is cheaper than a constant inbox watch.

What to watch#

• Fewer, bigger Bots in November. "My CEO bot is going to cull the herd in November after some projects are done", combining Bots with overlapping duties (post). Watch whether the bills and bank Bots merge.
• Compliance next. Two more Bots, "Compliance - Leases, Owners, Vendors" and "Insurance, Licenses, Records", are "Upcoming, still building this one out" (thread).
• Real numbers. He hasn't posted hours saved or error counts for the bills work. We'll recheck his posts and update this playbook if he does.
• Official templates. Grok Bot's use cases page lists an Invoice Coordinator that "Forwards invoices, matches what it can, tracks campus or vendor actuals, and nudges the right owner when something needs a human". It is a general starting point, not built for AppFolio.

Related#

• Grok Bot for operations: trackers, office logistics, and vendor spend
• Grok Bot for finance: a bookkeeping Bot that prepares and an accountant who approves
• Finance integration links bank and card accounts
• Sign your Grok Bot in to sites without handing over passwords
• Make Grok Bot routines stay quiet when nothing changed

Sources#

• @ChrisTwiggsPM on X, Oct 13: the daily invoice email sweep
• @ChrisTwiggsPM on X, Oct 13: mailed city bills by photo and the JPG to PDF step
• @ChrisTwiggsPM on X, Oct 13: owner records for the platform switch and moving October's accounting
• @ChrisTwiggsPM on X, Oct 13: browser login, no API
• @ChrisTwiggsPM on X, Oct 8: How I use Grok Bot as a Property Manager & Sales Broker (thread)
• Blair Allen: team page
• AppFolio Engineering: Understanding invoices with Document AI
• @bot on X: Accounts connect securely through Plaid
• Cursor Docs: Work with Grok Bot
• Cursor Help Center: Routines
• Grok Bot: Use cases