When should you use it?
- A city event week posts dozens of sessions
- Good events fill within hours
- You register on an event platform
Not for: Auto-registering for events without you; Events requiring payment you have not approved
What do you need, and what do you get?
You need
- Event listing pages for the week
- Your event platform account
- Your calendar
You get
- A daily list of newly posted events
- An itinerary of accepted events
- Addresses and travel notes
How does it work, step by step?
- Create one bot per city or weekKeep each focused on a single set of listings.
- Check dailyHave it compare today's listings with yesterday's and report only new ones.
- Register yourselfUse the alert to sign up quickly; keep registration a manual step.
- Connect the event platformLet a second bot see which events accepted you.
- Plan the dayAsk for an itinerary with times, addresses and travel gaps.
The prompt
Our own prompt, inspired by Baskaran Manimohan and written to work in Grok Bot. Values in lime are placeholders.
Each morning, check [event listing pages] for [city] [week]. Compare with yesterday and list only new events, filtered to [topics], with time, venue and sign-up link. Do not register me. Separately, read my accepted events from [platform] and build a day-by-day itinerary with addresses and travel time between them.
Inspired by Baskaran Manimohan: Grok Bot: AI Agents That Work Together. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Listings change and get canceled; recheck the morning of.
- Group chats with too many bots get noisy; he suggests three or four at most.
Our take
Baskaran Manimohan of CloseFuture built several Grok Bot agents in an afternoon, including two for Tech Week: a San Francisco watcher that checks daily for newly posted events so he can register early, and a Bangalore planner connected to Luma that knows which events he was accepted to and lays them into a schedule, including addresses for early workshops. The split into watcher and planner keeps each bot simple. Add a filter for topics you care about so the daily list stays short. His habit of turning off send permissions on email bots is worth copying for every connector. Register yourself rather than letting a bot RSVP with your account until you trust it. Confirm addresses and travel time the night before; agents misread venues. Delete or pause the watcher when the week ends so it does not keep pinging. Prefer official event calendars over scraped aggregates when both exist.
Where the time goes back: Daily checking of busy event listings is automated, so you only act when something new appears.
FAQ
Can bots collaborate?
How did he handle email access?
Source and credit
Inspired by Baskaran Manimohan. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Grok Bot: AI Agents That Work Together
- Creator
- Baskaran Manimohan
- Published on
- closefuture.io
- Original date
- Oct 1, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Grok Bot
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.