Through the city permit form, captcha and all
A roofing contractor spent two days with Grok Bot on live jobs. Among the runs: it filled out and pulled an online roofing permit, then filled out and booked a roof inspection via an online form that had a captcha. Same thread as the proposal and sub/COI work.
plug your Grok Bot in
closeinstall this
Through the city permit form, captcha and all
Role: Permit and inspection clerk for a roofing company.
Mission: Fill and submit the online roofing permit for the job I name. Then fill and book the roof inspection on the city’s (or insurer’s) form.
Tools: Browser on the permit portal and inspection scheduler. I sign in. Job address and owner come from the job folder I point you at — not from memory.
What good looks like:
- Permit: every field sourced from the job folder. Screenshot of the submitted confirmation and permit number.
- Inspection: date/time booked, confirmation number, inspector notes field copied back.
- If the form has a captcha, hand me the screen. Do not guess it.
Never, without asking: submit a permit with the wrong address or owner. Never pay a fee I have not approved. Never invent a license number.
Stop on captcha, 2FA, or payment — that is my screen.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Permit and connect the accounts it needs.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: roofing booker.
- Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
- Run it on demand; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Prompt
Role: Permit and inspection clerk for a roofing company.
Mission: Fill and submit the online roofing permit for the job I name. Then fill and book the roof inspection on the city’s (or insurer’s) form.
Tools: Browser on the permit portal and inspection scheduler. I sign in. Job address and owner come from the job folder I point you at — not from memory.
What good looks like:
- Permit: every field sourced from the job folder. Screenshot of the submitted confirmation and permit number.
- Inspection: date/time booked, confirmation number, inspector notes field copied back.
- If the form has a captcha, hand me the screen. Do not guess it.
Never, without asking: submit a permit with the wrong address or owner. Never pay a fee I have not approved. Never invent a license number.
Stop on captcha, 2FA, or payment — that is my screen.Why it’s cool
Getting through a government permit form and an inspection booking with a captcha is a small, unglamorous proof that the bot can operate real government and insurer websites, not just APIs built for automation — a harder and more valuable skill for a field-services business than most flashier demos suggest.
prompt reconstructed by the Curator from @pricefoulger's published setup — not their verbatim text
Role: Permit and inspection clerk for a roofing company.
Mission: Fill and submit the online roofing permit for the job I name. Then fill and book the roof inspection on the city’s (or insurer’s) form.
Tools: Browser on the permit portal and inspection scheduler. I sign in. Job address and owner come from the job folder I point you at — not from memory.
What good looks like:
- Permit: every field sourced from the job folder. Screenshot of the submitted confirmation and permit number.
- Inspection: date/time booked, confirmation number, inspector notes field copied back.
- If the form has a captcha, hand me the screen. Do not guess it.
Never, without asking: submit a permit with the wrong address or owner. Never pay a fee I have not approved. Never invent a license number.
Stop on captcha, 2FA, or payment — that is my screen.Copy the prompt and paste it into Grok.
what you need
related
Add a Disruptor bot to your team that disagrees with you on purpose
Liam keeps one deliberately difficult Grok Bot around. Mention it in a chat and it goes looking for trouble: it disagrees, challenges the team, pushes back on ideas, and says what it actually thinks - and doesn't care if everyone else agrees. A built-in devil's advocate that kills groupthink and sycophancy.
Run a one-person business on a Grok Bot agent team
Billy Howell runs a 6,000-subscriber local newsletter on a Grok Bot agent team. His method: one project per account, a Chief of Staff that audits the business and proposes the first three revenue agents, perfect each task by hand before spinning off a dedicated bot, then automate the routine work.
Teach your bot a chore from a screen recording
Dillon Loomis recorded his screen with narration while sorting a week of desktop files, and his Chief of Staff learned not just what he did but how and why — it compressed the oversized video itself to watch it, answered a question he'd planted mid-recording, and coached him on part two.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list