A meeting transcript becomes five assignments. A customer-support agent prepares a refund request but leaves the final decision to a person. Another bot watches for an online booking slot and asks before reserving it. In this episode, Andrew Warner and Andrew Kordampalos review 11 such Grok Bot examples from eight other creators. The interesting question is not whether an agent can click through a task. It is whether the trigger is timely, the permission is narrow, and the person can see and approve what matters.
The strongest pattern is event arrives → agent prepares → human reviews → approved action runs → result is logged. Webhooks can avoid wasteful polling; sub-agents can keep long jobs off the main conversation; and approvals can protect customers and accounts. The episode's clips show possible workflows, not independent evidence of savings, sales, or error rates. Begin with one low-risk job and measure it.
Watch the Discussion
Credit: The Next New Thing episode, published 3 October 2026, and the supplied transcript are the basis for the commentary. Each original creator is credited beside their video below. The episode is presented by Zapier; its Zapier segment is a sponsor integration, not a neutral product benchmark.
Eleven Examples, Four Kinds of Work
| Work | Examples in the episode | First control to add |
|---|---|---|
| Trigger and delegate | Meeting actions, sub-agents, form webhooks | Event filter and explicit task owner |
| Read and prepare | Local files, AI recommendations, subscriptions | Read-only access and source links |
| Customer-facing | Support refunds, Marketplace listings, email | Review before money, publishing, or replies |
| Repeat and improve | Useful posts turned into skills, appointment booking | Test run, permission scope, and confirmation |
The source collection is also available as an 11-clip visual index. It links each original creator and includes alternate timestamps. The embedded gallery below shows each of the eight distinct creator videos once; where a video supplies two examples, both moments are linked.
1. Trigger Work, Then Delegate It
Brock Mesarich's meeting example takes a Granola note and splits follow-up across specialized agents. Andrew's criticism is that a three-hour polling routine can make a supposedly proactive system both late and expensive. A cleaner design is to trigger when the note is ready, extract proposed actions, let the meeting owner select the real commitments, and only then assign work. A transcript is evidence of what was said, not permission to contact a customer.
Sharbel A.'s sub-agent example lets a long research or preparation task run without monopolizing the main bot. That helps with parallel work, but it also creates more branches to review, more context to share, and potentially more usage. Give each agent one bounded deliverable and a completion test. At 17:06, Nate Herk shows a form submission waking a bot through a webhook. The advantage is immediate work on a real event, not repeated inbox sweeps. Validate the webhook source, filter duplicate events, and do not expose its endpoint as a public instruction to arbitrary callers.
Grok Bot's official routines documentation covers scheduled and event-driven automation. Zapier is one possible bridge to connected apps; the Zapier MCP page describes its integration, while the episode's discussion points to using deterministic automation for routine triggers and an agent only when interpretation is needed.
2. Read Files and Find the Decision
Nate Herk's local-file demo asks Grok Bot to identify and rename a desktop file. This is useful for low-risk housekeeping, but local access is a different permission from reading a web page. The official access guide says local computer access defaults to asking each time. Keep a recoverable copy and preview the proposed move or rename before applying it to important folders.
AI LABS checks whether assistants recommend a business for relevant queries. That is a useful qualitative audit: record the exact prompt, model, date, response, cited sources, and competitors. It is not a stable “rank” across all users or proof of revenue. The agent should identify missing evidence and inaccurate descriptions, then propose content or outreach for a human to verify.
How I AI's subscription audit searches receipts for recurring spend. Email receipts can miss charges, credits, renewals, and subscriptions paid from another account. The source collection itself notes that connected financial data may be more complete, but that means a much higher permission burden. Start with a user-provided export, show the evidence behind every candidate, and ask before canceling or negotiating anything.
3. Keep a Person at the Customer Boundary
How I AI's support bot handles routine issues and requests approval for a Stripe refund. Andrew likes the visible action card and weekly feedback into support documentation, but questions the hourly sweep: a new ticket should trigger timely triage. Kordampalos points out that several approval cards in one chat can become hard to track. For a real support desk, keep a ticket ID, customer context, refund amount, policy basis, approver, and final result together. The human should verify the transaction before approval.
Peter Yang's Marketplace clip shows a multi-step brief: inspect a product photo, compare local prices, learn a preferred listing style, draft and post the item, then lower the price on a schedule. A business should split those into permissions. Research and drafts are low-risk; publishing, buyer messages, price changes, and accepting terms are external actions. Set a minimum price, disclosure rules, and a review point before the first listing or any automatic change.
Sharbel A.'s inbox triage prompt sorts messages into safe-to-archive, read-only summaries, and replies drafted in the user's voice. Its most important line is that replies wait for approval. Scope the run to a time range, label uncertain classifications, and keep sensitive email out of shared bot contexts. The episode also touches on calendar updates; conversational access helps with finding actions, but it does not replace a visual calendar for checking conflicts.
4. Turn One-Off Work Into a Checked Routine
Leveling Up with Eric gives his bot a useful post from X and asks whether it suggests an upgrade to an existing workflow or a new bot. That is an idea intake process, not a mandate to copy the post or change production. Save the source, specify the proposed behavior, run a small test, and have an owner accept or reject the change. This also makes creator credit and provenance easy to preserve.
Paul J Lipsky's booking agent checks his calendar, finds an online appointment window, and asks before reserving it. At 38:42, Kordampalos highlights “Teach a Task” for turning a difficult browser flow into a reusable skill. The Grok Bot docs describe taught skills and caution that test runs can perform real actions. Test with a harmless example first. Avoid giving a bot an entire password vault when one scoped session or credential is enough.
The final team-work teaser matters because shared bots change the security model: another person can now see work or ask the bot to act. Official team documentation and the privacy guide are worth checking before connecting a team workspace. Multiple bots can share a cloud computer; separate names do not by themselves create separate security boundaries.
Original Creator Videos: All 11 Examples
These are the original demonstrations Andrew and Andrew react to. The embeds begin at the cited example where possible. Each caption links the exact moment; repeated creators are embedded once.
A Safer First Pilot
- Pick one trigger. A submitted form or finished meeting note is easier to observe and measure than “check everything every hour.”
- Keep preparation separate from action. Let the agent classify, summarize, and draft. Use rules or code for deterministic routing.
- Review the risky step. Require a person before external messages, refunds, price changes, purchases, bookings, account connections, or important file edits.
- Log the outcome. Record the source event, draft, approver, action, time, and correction. Compare delays, errors, and real customer outcomes against the old process.
Turn a Workflow Into a Business Idea
This prompt works in a general AI assistant. It uses the episode's event-driven and review-gated ideas to find a buyer, then forces a small validation test before a recurring-service claim.
Find one valuable trigger
Three service ideas, one approval-gated pilot.
Episode Chapters
00:18 Meeting notes · 02:42 Better triggers · 04:12 Local files · 06:00 AI recommendations · 08:51 Zapier · 11:24 Subscriptions · 14:06 Sub-agents · 17:06 Webhooks · 21:18 Refund approvals · 25:30 Marketplace · 28:03 Email and calendar · 30:18 Inbox triage · 33:27 Bot upgrades · 35:33 Bookings · 38:42 Teach a task · 40:03 Team bots.
Source Map and Further Reading
- Episode and creator index: The Next New Thing discussion; the 11-clip collection. The eight original videos and exact example timestamps are embedded above.
- Official product: Grok Bot announcement, overview, skills and routines, approvals and privacy, and teams.
- Integration: Zapier MCP is relevant to event-triggered app connections and sponsors the episode. It is not required for every workflow.