145 Grok Bot Tips and Tricks From Real Users (Sourced)
Every practical tip on this site in one list, grouped by what you are trying to do. Each one opens a full write-up with steps, a prompt to copy and the mistakes to avoid, and credits the person who shared it. Official update notes live in what's new. Want just the prompts? See prompts by job.
Start here
- Have your Bot call a US business to lower a bill. Give a Bot your account details, current price and a competitor's offer, and it phones the company, gets through the menu, negotiates and checks with you before agreeing.
- Two habits that make usage last: batch requests, send words not screenshots. Every message makes a Bot reread the chat, so send related requests together, skip 'thanks' replies, and paste text or cropped images instead of full screenshots and PDFs.
- Build a three-Bot starter team: Scout, Shopper and Desk. One Bot researches and checks sources, one shops and stops before checkout, one learns a weekly task by watching you once.
- Borrow skills from public Bots before building your own. Point your Bot at a directory of public Bots, give it your goals, and have it list which skills you need and where they come from before adding anything.
- Let your Bot cancel free trials and unused subscriptions. Three built-in templates from 0.78: start a trial and cancel it before it bills, cancel plans you don't use, and watch renewal prices.
- Have a Bot watch for cancellations at a fully booked spot. Ask a Bot to check a booking page every hour and ping you the moment a slot opens, so you can grab a cancellation before anyone else.
- Package your whole Bot setup into one zip you can rebuild from. One prompt makes your Bot bundle your preferences, memory, skills, routines and instructions into a zip with a README, without any passwords or keys.
- Find the tasks you repeat every week, ranked by time saved. One prompt makes your Bot read two weeks of your email, meetings, Slack and docs, list what you do over and over, and pick the top three to automate.
- Compare tools from their official pricing pages, into a shareable sheet. Ask a Bot to compare a few products for your team size using only the official pricing pages, with no signing in, and return a table plus a spreadsheet in your library.
- A people Bot that remembers everyone you meet. Tell one Bot about people as you meet them, with exact spellings, and ask it later who someone was in one line.
- Build a weekly research briefing Bot from scratch, then test run it. Create a research Bot with a clear role, check it understood, connect Gmail, save a report skill, and schedule it for Monday 9:00 a.m. Then press Test run instead of waiting a week.
- Ask your Bot which dashboards you should build. A reverse prompt: your chief of staff checks with your other Bots and suggests five Pages worth having.
- Out of usage? Run these five checks before you buy credits. Grok Bot says you're out of usage but you still have credit? Check the weekly pool, the monthly cap, the meter, the account, then what's eating it.
- tibot: one sorted digest of everything said about you on X. A marketplace Bot that finds posts about you or your keywords, tagged or not, and sends one short sorted digest a day. It never posts for you.
- Have your Bot set phone alarms for today's meetings. Connect Calendar and Alarms on your phone, then a daily routine sets an alarm for each meeting.
- Give your support Bot your SOPs, then schedule it for business hours. Attach your support docs so drafts follow your rules, then one sentence sets an hourly check during work hours with every reply waiting for you.
- Make a write-like-me skill from your sent email. One sentence has a Bot read your sent email, find how you write, and save it as a skill every Bot uses when drafting for you.
- Get a prep doc a few minutes before each meeting. A morning routine reads your calendar, pulls context from email and connected apps, and sends a prep doc just before each meeting starts.
- Ask which of your past prompts should be routines. One prompt makes a Bot look back over what you keep asking and say what should be a routine, a trigger, or its own Bot.
- Vault: logins, cards and contact info. Your Bot never sees saved passwords or card numbers. One catch with saved cards.
- Three questions before you create another Bot. Only make a new Bot if the job needs its own memory, different permissions or its own schedule. Otherwise give it to your chief of staff.
- Use your 1Password with Grok Bot. Connect 1Password, approve each login in the 1Password app, and it fills the sign-in without the Bot seeing the password.
- Grok Bot can use your phone's apps. Calendar, Reminders, Contacts and more, on iOS and Android.
- Tag @bot on X: say "send it to my bot". Just tagging @bot won't reach your chat. Ask it to send it to your Bot.
- Turn YouTube videos into Notion notes. Give it a link; it saves quotes, ideas, trends and questions to Notion.
- Call your Bot back within 30 minutes and it remembers. Voice calls now carry over: hang up, call again soon, and the Bot has the previous call's transcript.
- "Hey Siri, ask Grok Bot". Set up a Siri shortcut that starts a voice chat with your Bot in under a minute.
- Set up Auto-review rules: ask first for anything you can't undo. Turn on Auto-review, then add Ask first rules for money, publishing and sending. When rules clash, Ask first wins.
- Set Grok Bot as your iPhone Action Button. Press it and you're talking to your Bot. No app to open, nothing to type.
- A safety baseline before sharing logins. All your Bots share one computer, so every Bot can use each login.
- Teach a task by doing it once. Do the workflow while it watches; it records the steps.
- Before you unify your Cursor, Grok and X subscriptions. A walkthrough of the unify screen: connect the right accounts, compare plans, watch third-party model pricing, and know it can't be undone.
- Connectors before the browser. One task got about 45x cheaper by switching to a connector.
- Route your Bot's web traffic through your computer. Turn on one setting so websites see your connection instead of a cloud machine, which gets blocked less often.
- A Bot that keeps your to-do list up to date. Tim Fairley's first-Bot pick: a routine that reads email and messages to update a cloud to-do list, plus quick adds from your phone.
- A price watch Bot that only pings you for a real, verified drop. Give a Bot one exact product and two shops. It checks every morning, treats anything it can't read as unknown, and stays quiet unless it confirms a lower price.
- Clean up a messy folder safely: plan first, move after you approve. A cleaner Bot finds exact duplicates and proposes where every file goes. Nothing moves until you approve, and it checks every file is still there afterwards.
- Make an executive assistant your first Bot. Charlie Chang's beginner setup: one general helper Bot first, told plainly what it owns, before any specialists.
- Add a ready-made Bot from the Marketplace. Browse Bot templates at x.ai/bot/marketplace, read what each one includes, then add your own copy.
- Triage and reply to email from the chat. Ask for a brief of emails that need replies, then answer them in one line each.
- Make your first task boring. Start with something checkable, then add one thing at a time.
Routines that don't break
- A read-only usage audit across your whole Bot team. One prompt has your chief of staff check every Bot's routines, schedules and triggers, then report what to pause, slow, narrow or merge, and change nothing until you approve.
- A routine that triages your backlog with RICE and blast radius. Your Bot collects requests into a backlog, then a routine scores each item for reach, impact, confidence, effort and blast radius so the best small jobs rise to the top.
- A content scout routine that files X news onto your idea board. Twice a day, a Bot reads public posts on X, picks three topics worth covering, and adds the useful links to matching cards on your Notion idea board.
- A Sunday leadership brief from meeting transcripts and Slack. Once a week, a Bot reads your team's meeting transcripts and Slack and tells you what each team discussed, what was decided, and where it drifts from your priorities.
- Build a monthly usage audit page that labels every routine. Hand your Bot screenshots of your usage and billing pages, get a page that marks each routine Keep, Slow down, Change check or Retire.
- Route every meeting transcript to the right Bot with a webhook. When your note taker finishes a call, a webhook wakes your Chief of Staff Bot, which reads the transcript and hands it to the Bot that owns that work.
- A Monday money check routine. Renewals, higher bills and price drops in one short list. Nothing bought without your yes.
- Keep routines one line long. The schedule says when. The skill says how.
- Analyse your own usage CSV. Export usage from the Usage page and ask your Chief of Staff Bot how to cut it.
- Put quiet hours inside the routine itself. Have the routine re-check the clock right before it acts, and skip itself if it's too late.
- Write the outcome, not the recipe. Describe what you want; pasted tool calls break by week two.
- Make routines cheaper: events, slow schedules, change checks. A 5-minute routine wakes 8,640 times a month. Use an event trigger, the slowest schedule that works, and a cheap change check.
- Create a routine by asking, then ask what else to schedule. Describe a schedule in one sentence to make a routine, then ask the Bot which routines it thinks you need.
- Run nightly code audits that leave PRs for the morning. Engineer Bots clean up the codebase overnight; you review a fresh set of pull requests with breakfast.
Skills and prompting
- Turn a repeated job into a script the skill runs. Do a weekly job once with your Bot, check it, then have it rewrite the job as a plain script and save a skill that runs the script and reports in two lines.
- Keep lasting rules in the description, not memory. Duplicate a Bot and the description comes along; memory starts empty.
- Keep a restore skill for when your Bot's computer is updated. Files and logins survive a computer update; installed tools don't. A restore skill puts them back in one message.
- A /clean-start skill for long chats. Save the goal, decisions, files and next action to a handoff file, then pick up in a fresh chat.
- How to trust your Bot's work more. Put most of your effort at the top: code structure, then lint/tests/CI, then prose rules, then human review.
- Keep skills in a GitHub repo and sync them to your Bots nightly. One-line routines call skills; the skills live in a repo you edit elsewhere, and a nightly routine pulls them onto the Bots' computer.
- Give deep research a finish line. "Research this deeply" gives no finish line and no reason to stop browsing.
- Do it by hand, save a skill, then schedule. Most automations break because they're scheduled before they've worked once.
- Teach a task the smart way: describe it first, record only the gap. Most of a browser job can be explained in chat. Record a 20 to 60 second clip of only the part the Bot can't work out, then add anti-jobs before you schedule it.
Connectors and apps
- A read-only X Bot that finds conversations worth joining. A Bot checks X every 30 minutes for fresh posts you can add something to, ranks them Act now, Maybe or Skip, and never posts.
- Three email-triggered Bots from the Grok Bot team's demo. Give Bots its email: one reviews your Google Docs from its own Google account, one fact-checks deal newsletters, one logs receipts sent to a plus alias.
- Find what your audience keeps asking for in 28 days of comments. Connect YouTube through Zapier's MCP server, then have your Bot read recent comments and rank the most requested topics with real quotes and like counts.
- Make your Bots read websites with a script, not screenshots. One test: 213K tokens by clicking around, 51K with a browser script, almost none with a plain script. Give your Bots the rule.
- Build a Tesla Bot with Tesla's Fleet API. A Bot that checks your Tesla, runs climate and charging, and asks before it unlocks anything, set up through Tesla's free developer Fleet API.
- Route Bird customer messages to a webhook routine. Bird's official plugin plus a Grok Bot webhook routine lets incoming Apple Messages or emails wake a Bot that drafts the reply for you to check.
- The fan-out method: three models, one brief. Launch Cursor cloud agents on three models at once and keep the best parts.
- Connect Clay and build sales workflows from one sentence. With the Clay plugin, your Bot searches, enriches and researches companies and contacts in Clay, then finishes the steps Clay can't do alone.
- Ask for plus-addressed aliases on your Bot's email. Your Bot can send from tagged addresses like name+shop@, and a routine on that tag runs only for its mail.
- Forward new leads to your Bot's inbox. A Gmail filter forwards leads to a tagged Bot address; a routine on that tag researches each one before you reply.
- A daily X digest in Slack. Watch what people do with Grok Bot on X and Slack you a 9am digest.
- Give your Bot its own email address. Ask your Bot to claim an address so you can forward or CC it, and so it can sign up for accounts itself.
- Connect your apps from chat, or through one MCP hub. Ask a Bot to connect Gmail and other accounts in chat, or use one Composio or Zapier account if you have many tools.
- Let your Bot ask for the access it needs. Describe the job first. The Bot tells you which tool to connect and walks you through it.
Several Bots working together
- Five no-small-talk rules for Bots that talk to each other. Paste five rules into each Bot so group chats and handoffs stop filling up with 'got it' and thumbs-up replies.
- One governed Team Bot as the source of truth for sensitive data. Put a sensitive workflow, like checking exposure or compliance wording, in one admin-managed Team Bot that every personal Bot asks, instead of everyone building their own.
- Lauren Tan's guide to a small, high-quality Bot team. A few well-onboarded Bots beat a big team. Design them with Dr. Eggbot, have them write their own skills, give them real access, and brain dump by voice.
- Make your Bot the manager, not the coder: one rule and locked doors. Let your Bot plan and check the work while coding agents write the code. Start with one rule, and remember every Bot shares one computer and its logins.
- Promote a Bot to director and let it build and run its own team. When one Bot has collected a lot of context, promote it: ask it to create three Bots that report to it, keep them away from you, and send you one Monday summary.
- Share a finished Bot as a template without sharing your accounts. Share as template packages a Bot's rules, skills and routines. A privacy filter strips chat history, email addresses, account IDs, tokens and keys before you publish a link.
- Use Dr. Eggbot to health-check the Bots you already have. Dr. Eggbot isn't only a Bot builder. Its built-in routines scan your Bots' recent chats for friction and your routines for wasted usage, then propose fixes.
- Move an old AI agent folder into Grok Bot. Tom moved 59 local agents into about two dozen Bots by going through them one role at a time: keep, merge, instructions or shared skill.
- Run a daily standup with your Bots in a group chat. Put your main Bots in one group chat and have your primary Bot ask each morning what everyone is doing today, so nothing slips.
- Turn a Bot into a team Bot your colleagues can use. Share a working Bot with your team as an internal tool, with owners who edit and users who just use it.
- Let a team Bot answer requests in Slack. Install a team Bot in Slack so colleagues tag it directly, and give it a routine to catch missed tags.
- Run a weekly Bot audit to merge or retire extras. Once a week a Bot reviews your whole team and proposes which Bots overlap, which are idle and which do too much. You make the changes.
- A daily loop: a metrics Bot decides, other Bots change the site. In the official 201 workshop, an orchestrator Bot runs a daily skill: read the analytics, drop the bottom three, design three new, deploy.
- Dad Bot: get your parents started. A patient helper that walks older folks through it one step at a time.
- Back up your whole Bot setup. Have each Bot document its job, rules, skills and routines into a recovery doc, kept current monthly.
- One job per Bot. Give each Bot one job and a list of things it never does.
- Two Bots that research leads and draft first emails while you sleep. One Bot finds the right person at each target company, a second writes a personal first email as a draft, and you review the pile each morning.
- Pick a main Bot so it can see and delegate across your team. A main Bot gets wider visibility into your other Bots, messages you first, and hands work out.
- Use a group thread to watch Bots work together. Put several Bots in one chat so you can see every handoff instead of hidden Bot-to-Bot messages.
- A manager Bot that never does the work itself. Give a lead Bot one job: break work down, hand it to worker Bots, and check results against the goal. Big projects then run as a chain you only talk to at the top.
- An ops Bot that runs postmortems and daily 1:1s with your Bots. When a Bot makes a mistake, an ops Bot finds the cause, updates the shared playbook and tells the others.
- Run each project as a channel with a roster and a Notion board. A projects manager Bot opens one group chat per project, staffs it from your existing Bots, and tracks tasks on a Notion board with a Blocked column.
- Start with a chief of staff Bot. Talk to one coordinator Bot and let it hand work to your specialist Bots.
Pages and dashboards
- An events scout that signs up with its own email and keeps a calendar Page. A Bot finds events on sites like Luma and Meetup using its own email address for sign-ups, then keeps a calendar Page of confirmed and unconfirmed events up to date.
- Build a crew dashboard of what every Bot is doing. A Page that shows which Bots need you, which are busy and which are idle, rebuilt every morning.
- How Pages stay up to date (and what they cannot do). Pages are not live: a routine rewrites them. Know the limits before you build many.
- Build a recurring charges page from your email receipts. One prompt turns receipt emails into a subscriptions page with totals, duplicates and a privacy toggle.
- Turn a messy CSV into a report that says what to fix first. Hand your Bot a messy export and ask for a cleaned, scored report with a do now / do later list.
- Share a Page by link, and know who can see and edit it. Anyone-with-the-link pages open without sign-in, viewers cannot edit, and team sharing needs a Teams plan.
- Build a weekly before-and-after scoreboard from a Google Sheet. Point a Page at a sheet, compare baseline weeks with recent weeks, and refresh it every Monday.
- A personal finance dashboard with Pages. Connect bank accounts and X Money; the Bot builds one dashboard across them.
- Pages: reports and dashboards that stay up to date. Ask for a report, memo or dashboard and get an editable page.
Everyday workflows
- From support form to fix: a webhook, a Bot and a Cursor cloud agent. A support form posts to a webhook, a Bot picks up the ticket, and for bugs it starts a Cursor cloud agent that reproduces the issue, adds a failing test and opens a pull request for an engineer to review.
- An incident routine that investigates before you wake up. A Sentry, PagerDuty or GitHub event triggers a Bot that builds the timeline and proposes a fix, but changes nothing in production without you.
- Benchmark your assistants on your own top tasks. Ask each assistant for the tasks it does most for you, pick the overlap, give them the same tools and short prompts, then score the results side by side.
- Inbox manager in review mode that learns from your edits. A separate inbox Bot sorts mail and Slack, drafts replies in your voice, and every Friday compares its drafts with what you actually sent.
- Have a Bot click through your landing pages as a real buyer. Give a Bot your ad landing pages. It clicks, scrolls and reads like a buyer, scores each page out of 10, finds broken steps and gives you the top fixes.
- Plan every Bot job with four blocks. Corey Ganim runs 6 Bots and 14 weekly routines across 11 apps. Each job is built from the same four blocks: Bot, routine, skill and connector.
- Expense Bot: inbox receipts into a Notion table. Sonny Sangha's expense Bot scans two inboxes for receipts, logs them in Notion, and learns to fetch portal invoices with Teach a task.
- A news-to-website pipeline with two approval gates. Four Bots gather news from X, draft an edition, and ship articles through a pull request, but nothing moves without an "approve" and a "publish" from you.
- A household shopping manager that builds your weekly cart. A year of orders became a Notion catalog. Every Sunday the cart is built and the human checks out.
- Register for Do Not Call. The Bot registered his number and clicked the confirmation email itself.
- An event RSVP Bot that answers 'is X coming?' in Slack. A Bot reads your event registrations, posts who's attending by account each day, tags the owners, and answers questions in the channel for you.
- How the team uses its own Bot on support. It spots incidents and answers related tickets; a human approves the batch.
- Get links to every comment you haven't answered. Kris wakes up to hundreds of comments. The Bot sends links to each unanswered one and Kris replies personally.
- Have Bots email you numbered approvals you can answer from your phone. Design what Bots send back as much as what you send them: a few email types, clear subject lines, and numbered items you reply to in one line each.
- Keep an attention list instead of a priority list. An hourly routine reads your email, Slack, meetings and calendar and keeps a short list of what you are actually working on. Other Bots use it as a filter.
- Fact-check before you publish. It checked 11 claims against 9 sources and quoted the line behind each.
- Turn your YouTube Watch Later pile into a learning site. A Bot reads the transcript of every video in your Watch Later list and builds a site with summaries, timestamps, a quiz and a watch or skim verdict for each.
- Have a Bot update your CRM after every call. Your Bot reads call notes, email and Slack for an account and proposes the CRM updates; you approve them instead of typing them.
- Keep long jobs sharp: helpers, files and the cheapest tool first. How the Grok Bot harness avoids running out of context, and how to ask for work in the same shape.
- Run Claude Code or Codex on your Bot's computer with your own plan. Your Bot's computer has a terminal, so it can install a coding CLI, you sign in once, and your Bots can use that subscription from anywhere.
- Start each day with an approvals prompt, end it with a night prompt. Two short daily questions that get your Bot to find work you forgot about.
- Watch coding work live and get recordings back. With Cursor connected, your Bot links you to the cloud agent live and sends screenshots and screen recordings.
- A printed daily brief from your home printer. A Daily Brief Bot pulls your calendar, bookmarks and workouts from your other Bots, lays them out on one page and prints it at 6:45 AM through a computer on your home network.
- Check usage and update your Bot's computer in Settings. Where to see how much of your weekly usage is left, and when to update or reset the Bot's cloud computer.
- Open your Bot's screen to watch or help. Each Bot works on a real desktop you can open, watch, sign in on, and take over.
- Chain a whole errand into one prompt. Hand over every step of a job in one message, including the follow-up rule, and let the Bot ask your other Bots for what it needs.
Logins, Vault and safety
- Roll out Grok Bot to a team with admin guardrails. From the official admin video: set team rules, auto-review, plugin and network allow lists, then start with a pilot group before inviting everyone.
- What actually stops a coding Bot (and what is only advice). Of 15 operations tested, only a merge to main hit a hard stop. Skill-file rules are only advice.
- Test your Bot against instructions hidden in email. Send your Bot's inbox two booby-trapped emails, check it ignores them, then add a house rule and a sender filter.
- Research to purchase, with your approval. It researched pet insurance, compared quotes and paid with Link only after the user said buy.
On your phone
- Ask Grok Bot about whatever is on your iPhone screen. A free, open-source Action Button shortcut that sends your screen to your Bot and returns a silent answer as a notification.
Browse tips by topic
- Grok Bot routines (20 tips)
- Grok Bot skills (12 tips)
- Grok Bot connectors (17 tips)
- Grok Bot multi-bot setups (27 tips)
- Grok Bot phone & apps (7 tips)
- Grok Bot security & vault (9 tips)
- Grok Bot pages & dashboards (10 tips)
- Grok Bot workflows (39 tips)
- Grok Bot updates: what's new (4 tips)
New to Grok Bot? Start with how to use Grok Bot, or see real use cases and the full tips feed.