The most useful Grok Bot update last month is also the least flashy: Your bot can now have its own email address.
If that sounds minor, it isn’t. Give your bot an address, hook it up to a few apps and you can build workflows that kick off without you lifting a finger.
For example, if a prospect emails your bot, it can research the company, check your CRM and draft a personalized reply. Or a receipt lands at a different alias, the bot can log the expense. A newsletter hits a third address, and its contents get filed for your weekly research briefing.
And that's just email.
Over the past month, Grok Bot has also added interactive dashboards, deeper X integration, better access to websites and mobile apps, stronger coding workflows and new ways to share specialized bots across a team.
Some of these are brand new, and others make existing workflows easier to build or more useful. The real payoff comes when you start combining them.
A bot that can read and filter your email is helpful. A bot that reads your email, cross-checks your calendar, spots a commitment you forgot and drafts the follow-up is a different animal.
I pulled together 50 use cases from recent product releases, demos and examples shared by Grok Bot users on X and YouTube. Instead of sorting them by industry, I've grouped them by feature, so you can see what changed and several ways to use each capability.
Every workflow comes with a prompt you can adapt. Some you can try today; others need extra integrations or more setup.
Throughout the guide you'll also find ⭐ Forward Future Team Picks. I asked Matt, Alex and Brian for their favorite bots and workflows, then added a few of my own. They range from managing email and researching leads to editing video and running a team of AI software engineers. One of them is Alex's actual bot, which you can try yourself.
You won't need all 50. But I'd be surprised if you didn't find a handful worth putting to work this week.
The 10 Feature Categories
Feature | Number of use cases |
Bot Email & Inbound Triggers | 5 |
Proactive Main Bot & Routines | 7 |
X Search & Research Integrations | 6 |
Pages & Interactive Dashboards | 6 |
Vault & 1Password | 2 |
Computer Use & Teach a Task | 5 |
Shared Bots & Multi-Agent Workflows | 10 |
Cursor Cloud Agents & Video | 3 |
Voice & Mobile Integrations | 3 |
Commerce Integrations & Templates | 3 |
Total | 50 |
A note before we start: Grok Bot is moving fast, and not every feature is available to everyone. Some need specific plans or integrations; others are still rolling out. I've flagged the important limitations instead of pretending everything works out of the box.
Where to Start: Five Workflows Worth Trying First
Fifty workflows is a lot. If you only have an afternoon, start here.
Don't start by building an elaborate team of AI agents. Pick one workflow you already spend real time on and see whether Grok Bot can handle it reliably. These are the five we recommend prioritizing first.
Workflow | Why it's worth trying |
#1: Give your bot its own inbox | Unlocks a whole category of event-triggered workflows with very little added complexity. |
#7: Build a proactive chief of staff | Catches the commitments and scheduling problems that never make it onto your task list. |
#22: Audit your subscriptions | A simple project with a clear result and a real shot at saving money. |
#31: Teach a task | The most practical way to automate repetitive browser work without building an integration from scratch. |
#32: Update your CRM after meetings | Shows what's possible when a bot connects multiple apps and carries the work all the way through. |
More technical? Go straight to #43, which hands development work to Cursor cloud agents and brings back results you can review.
Already running several bots? Then #8, the automation verifier, might be the single most valuable thing you add.
Bot Email & Inbound Triggers
What's new: In October, Grok Bot gave bots their own email addresses, then added tagged aliases that can trigger different routines.
Why it matters: Your bot gets a dedicated inbox, and work starts the moment information arrives, without routing everything through your personal email.
An email address sounds like a small addition. In practice, it turns a bunch of previously clunky workflows into easy ones.
1. Give Your Bot Its Own Inbox, with A Different Alias for Each Job
You can now claim an email address for your Grok Bot and create tagged aliases, such as yourbot+receipts@... and yourbot+leads@....
Each alias gets its own job: one for receipts, one for business inquiries, one for research newsletters. When a message lands, the matching routine fires. Your receipts bot pulls the merchant, amount and date, then logs the expense in a spreadsheet. Your research bot collects interesting stories all week and delivers a Friday summary.
The win is that you stop forwarding things by hand. Set up the routing once, and information goes where it needs to go.
Try this prompt:
Help me set up your email address with three tagged aliases.
+receipts: Extract the merchant, date, amount, and expense category from incoming receipts, then log them in [Google Sheet].
+leads: Research the sender and company, check [CRM] for existing relationships, and prepare a prospect brief and reply draft.
+research: Collect newsletters and reports throughout the week and deliver a concise summary every Friday.
Create a separate routine for each alias. Include source links, flag errors, and never send external messages without my approval.
Send a test email to each alias first. Confirm the right routine fires before you forward real business mail.
Two caveats: Aliases organize incoming work; they don't isolate access or permissions. And since you may not be able to change a claimed address later, pick your handle carefully.
2. Research Inbound Leads Before You Even Open Their Emails
Grok Bot enthusiast Melvin Vivas (@melvindvivas), shared a simple setup: a Gmail filter forwards incoming leads to his bot, which automatically researches the sender and their business.
If you work in sales, consulting, recruiting or business development, this one's for you. Instead of opening an inquiry and burning ten minutes researching the company, you open your inbox with the background already done.
The bot can pull together what the company does, recent news, potential fit and questions worth asking. Connect a CRM, and it can also check whether you've talked to anyone there before.
Try this prompt:
When a new inquiry arrives at my +leads address, research the sender and company.
Check [CRM] for previous interactions and look for relevant recent developments, company information, and possible reasons they reached out.
Give me a five-bullet briefing, two questions worth asking, and a short reply draft in my voice.
Include links supporting your research. Flag information you couldn't verify, and never send the reply automatically.
Keep Version One focused on research and drafting. Once you've seen how well it qualifies leads, decide whether to automate more.
⭐ Forward Future Team Pick — Matt Berman: Lead Bot
Matt picked a Lead Bot as one of his favorites. It's a natural fit for Grok Bot's email, research and CRM capabilities: a dedicated assistant that sizes up new opportunities before you spend time chasing them.
The key is feeding it your actual qualification criteria. Any bot can spit out a generic company summary, but one that knows what makes a prospect worth pursuing is worth a lot more.
3. Replace Constant Notifications with A Weekly Approvals Digest
Entrepreneur Brian Casel (@CasJam) shared an interesting approach to managing bots: Rather than having them constantly message him, they send structured emails when a decision is needed.
Each email has a consistent subject line and numbered items. He can quickly review recommendations and respond with which ones to approve, change or skip.
There’s a bigger lesson here about how agents should communicate. If you have five bots working on different projects, you probably don't want five notification streams. You want the work done, the results organized and a manageable number of decisions brought to your attention.
Try this prompt:
Every Monday at 8 AM, prepare one approvals digest covering my active projects.
Include no more than six numbered decisions. For each, explain what needs deciding, your recommendation, and the consequence of doing nothing.
Use the subject line [Weekly Decisions].
Keep the message concise and actionable. Leave all consequential actions pending until I approve them through Grok Bot's approval controls.
Casel's original workflow used a third-party agent-email service, but Grok Bot's new inbox provides many of the same building blocks.
One distinction matters: replying to an ordinary email isn't necessarily equivalent to approving an action through Grok Bot's authenticated approval system.
⭐ FORWARD FUTURE TEAM PICK — Matt Berman: Email Triage Bot
Matt also picked an Email Triage Bot. It's a related idea, but it works further upstream, managing the inbox before messages turn into tasks or decisions.
A useful setup sorts incoming mail by importance, flags messages that require a response and drafts messages for review. Combine it with the approvals digest, and you spend your time on what matters instead of refreshing your inbox.
Start with sorting and drafts. Hold off on letting it archive or change anything on its own.
4. Bring Customer Messages from Multiple Channels Into One Workflow
Customer requests don't always arrive by email. They might come through WhatsApp, SMS, Apple Messages and support platforms.
Bird recently launched an integration that routes incoming customer messages to Grok Bot. With the right connections in place, each message can trigger a routine that looks up the customer, checks relevant account information and drafts a response.
For a small support team, that means opening the queue with much of the initial research and first drafts already done.
Try this prompt:
Create a routine for incoming customer messages from [Bird].
Identify the customer, retrieve relevant account or order information from [CRM/Shopify], and check our support policies.
Draft a helpful response using verified account information.
Flag requests involving refunds, legal issues, security or anything outside our standard policies.
Send drafts to me for approval. Never respond directly to the customer.
You'll need the appropriate Bird integration and event triggers. Test the workflow with common, low-risk inquiries before routing anything sensitive.
5. Find Legitimate Sponsorship Offers Buried in Your Inbox
If you've ever managed a creator's sponsorship inbox, you'll know that most incoming offers aren't worth a reply.
CEO Alex Finn (@AlexFinn) explained how he used a dedicated bot to review sponsorship messages, surface genuine opportunities and respond to legitimate inquiries. He started because he thought the filtering aspect would be the most useful — he hates reading email. But just four hours after setting it up, Grok negotiated and closed a deal for $10,000.
But even if your bot never obtains revenue on its own, it’s still a massive efficiency gain in terms of determining if a company is legitimate, the product fits the audience and the request contains an actual budget or campaign brief. It can also spot what’s missing and draft a reply asking for more details.
Try this prompt:
Monitor sponsorship inquiries arriving at [inbox].
Filter out spam, generic outreach, and products that clearly don't fit our audience.
For credible opportunities, summarize the brand, product, proposed deliverables, budget, timeline, and any missing information.
Rank the opportunities by audience fit and commercial potential.
Draft replies requesting clarification where needed. Never send messages or agree to terms without my approval.
Alex Finn's original demonstration predates October, but the new email features make this workflow easier to build.
Proactive Main Bot & Routines
What's new: Grok Bot's primary bot can proactively suggest ways to help. Routines have also become more flexible, with additional event triggers and higher execution limits.
Why it matters: Your assistant can start handling some of the small tasks and potential problems you'd otherwise need to notice yourself.
This is the point when an assistant starts to feel less like one more app you manage and more like something working alongside you.
6. Never Miss an Important Comment Again
Kris Kashtanova (@icreatelife) described waking up to hundreds of comments across her content. Her bot checks which ones she hasn't answered and sends her direct links. It doesn't reply for her, but it makes sure nothing slips through the cracks.
That's an important distinction for creators who want to maintain personal relationships with their audience without spending hours sifting through comments. The same approach can work for customer requests, community discussions and social media engagement.
Try this prompt:
Every morning at 7:30, review comments from the last 24 hours on my connected [YouTube/Instagram/X] accounts.
Identify unanswered questions, important feedback and comments that deserve a personal response.
Group them by post and provide direct links, with a short summary of what each person asked.
Prioritize the most important ones. Never reply, like, or follow anyone automatically.
Depending on the platform, this may require a connector or browser automation.
⭐ FORWARD FUTURE TEAM PICK — Brian Knepprath: Cross-Platform Social Bot
Brian recommended a similar workflow that extends across all the social platforms you use.
The idea is to have a bot monitor your posts for replies, mentions and questions directed at you, then bring the relevant conversations into one place.
I like this because it's even harder to stay on top of valuable interactions when you're posting across several platforms. This is not about having AI impersonate you in the comments, but to make sure you see and interact with the people who are actually trying to engage with you.
A useful version would provide direct links and prioritize conversations that warrant a personal response.
7. Build a Chief of Staff that Catches Things You've Forgotten
Matt Palmer (@mattyp), who works in developer relations at SpaceXAI, shared an example of his Grok Bot noticing that a scheduled ride didn't line up with his flight's arrival time.
Another example involved a schedule-change email that hadn't been reflected in the calendar. Neither problem is particularly complicated. They're just easy to miss when you're busy.
I think there's an even more valuable version of this workflow: tracking commitments.
Throughout the day, we make promises in emails, Slack messages and meetings. We'll send someone a document, make an introduction, review a proposal and follow up on a conversation.
Not every commitment makes it onto the task list.
A bot with access to the right applications can identify those commitments, check whether they've been fulfilled and flag the ones at risk of slipping through the cracks.
It can also work in reverse, catching commitments other people have made to you.
Try this prompt:
Act as my proactive chief of staff. Every evening, review tomorrow's calendar, recent email, approved Slack conversations, and my open tasks.
Look for scheduling conflicts, missing travel arrangements, commitments I've made that appear incomplete, and commitments others have made to me that may require follow-up.
Notify me only when something warrants attention.
Include the original source and your recommended next action. Distinguish confirmed commitments from inferred ones, and never send messages or modify my calendar without approval.
The hardest part is getting the notification threshold right.
If the bot flags every possible task, it quickly becomes another inbox. I would explicitly tell it to stay silent unless something requires attention.
⭐ FORWARD FUTURE TEAM PICK — Nick Wentz: Commitment Breaker
One of my favorite applications is what I call the Commitment Breaker. It looks for commitments buried in email, Slack and other conversations that never made it to my to-do list.
I find the reverse direction especially interesting: catching promises other people have made to you. Ask the bot to identify overdue commitments and prepare a follow-up, rather than relying on your memory to keep track of everything.
I'd prioritize this over a generic daily briefing because it looks for something specific that might otherwise get missed.
8. Have One Bot Verify that Your Other Bots Actually Did Their Jobs
This might be one of the most overlooked use cases in the collection.
Keep Reading
Available to paid subscribers
Get the Frontier Pass to access Forward Future's private Slack community, member-only videos and content, insider interviews, and monthly AMAs with Matthew Berman.
Join The Frontier Today
