Prompt Library

Grok Bot email prompts that wait before they delete

21 copy-paste prompts

Field-tested shape: the Bot walks the inbox like a person, buckets mail, and drafts replies. Delete, unsubscribe, and send stay on your side of the line.

In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup · Founder, Techpresso

Last updated August 28, 2026·Hand-curated & tested by the AI Academy team

Triage and purge

4 prompts

Three-bucket triage

1/21

✨ What it does

The Bot sorts [INBOX] for [DATE RANGE] into delete, archive, and needs-me, with ten examples per bucket and a money-or-legal flag list. You approve a bucket, then the Bot acts on that bucket only.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Triage [INBOX] for [DATE RANGE] into delete, archive, needs-me. Sources: Signed-in [GMAIL / OUTLOOK] on the computer. Ignore anything that looks like credentials or legal hold. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not delete, archive, or unsubscribe yet. Deliverable: Counts, 10 examples per bucket, and a legal/money flag list. Review point: I approve a bucket. Then you act on that bucket only.

💡

Pro tip: Mike P-style 90k purge works when the buckets are approved, not when the Bot "just cleans".

Newsletter and promo sweep

2/21

✨ What it does

The Bot lists newsletters with [0] opens in [90] days and drafts an unsubscribe plan, skipping anyone on [KEEP LIST I PASTE]. You tick senders; the Bot clicks unsubscribe only for those.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List newsletters with [0] opens in [90] days. Draft an unsubscribe plan. Sources: Inbox labels, unsubscribe headers, [KEEP LIST I PASTE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not click unsubscribe until I approve a sender. Deliverable: Sender, last open if known, keep/unsub, unsub URL. Review point: I tick senders. You click only those.

💡

Pro tip: Some unsub pages are dark-patterned. Ask for a screenshot of the confirm page before it clicks.

Two-inbox cleanup

3/21

✨ What it does

The Bot triages [INBOX A] and [INBOX B] separately using [A IS WORK, B IS PERSONAL] and reports anything that landed in the wrong place. You approve per inbox; the Bot does not move mail between them or delete.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Triage [INBOX A] and [INBOX B] separately. Do not move mail between them. Sources: Both signed-in inboxes. Rules: [A IS WORK, B IS PERSONAL]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not forward mail between inboxes. Do not delete. Deliverable: Two bucket reports, plus anything that landed in the wrong inbox. Review point: I approve per inbox.

💡

Pro tip: Say which inbox is which. Shared computer means both sessions may be logged in.

VIP and legal hold list

4/21

✨ What it does

The Bot builds a never-touch sender and label list from [CRM + CONTACTS + MY NOTES] so later triage leaves those alone. You edit the list, then the Bot may use it; it does not change filters yet.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a never-touch sender and label list from [CRM + CONTACTS + MY NOTES]. Sources: [CRM], [CONTACTS], names I paste. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change inbox filters yet. Deliverable: Never-touch list I can paste into the email Bot description. Review point: I edit, then you may use it.

💡

Pro tip: Put investors, counsel, and "from my mother" on this list. Write it once.

Prompts get you started. Tutorials level you up.

A growing library of 300+ hands-on AI tutorials. New tutorials added every week.

Start 7-Day Free Trial

Drafts and replies

4 prompts

Draft replies in my voice

5/21

✨ What it does

The Bot drafts a reply to [THREAD] in your voice for [GOAL OF THE REPLY], using two sample emails from you, and leaves it in Drafts. You hit send; the Bot does not cc anyone you did not name.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a reply to [THREAD] in my voice. Leave it in Drafts. Sources: The thread, two sample emails from me, [GOAL OF THE REPLY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send. Do not cc anyone I did not name. Deliverable: Draft body, suggested cc, and what you assumed. Review point: I hit send.

💡

Pro tip: Gmail connector may list attachments but not download bytes. Use Drive or the browser for files.

Waiting-on-them chase list

6/21

✨ What it does

The Bot finds threads from the last [21] days where you asked for something and got silence, quoting the original ask and drafting a nudge. You send the nudges you still want.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find threads from the last [21] days where I asked for something and they have not replied. Sources: Sent mail, inbox. Skip newsletters. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send nudges. Deliverable: Person, quoted ask, days waiting, draft nudge. Review point: I send nudges I still want.

💡

Pro tip: Ask for the original ask quoted. "You should nudge Jane" is not a chase list.

Meeting-request drafts

7/21

✨ What it does

The Bot proposes 3 slots of [N] minutes in [TZ] from your calendar for [THREAD], notes conflicts it avoided, and drafts the reply. You send the times; the Bot does not create events.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: For [THREAD], propose 3 slots of [N] minutes in [TZ] from my calendar. Sources: [CALENDAR], the thread, [WORKING HOURS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create events or send the times. Deliverable: Three slots, conflicts you avoided, draft reply. Review point: I send.

💡

Pro tip: Do not let it create holds on other people's calendars.

Attachment that the connector cannot fetch

8/21

✨ What it does

The Bot opens [MESSAGE] in the browser or Drive and saves the attachment to [FOLDER] on the computer. You open the file; the Bot does not email it onward.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Get the attachment on [MESSAGE] onto the computer via the browser or Drive, not the Gmail connector. Sources: The message in the cloud browser. Destination: [FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email the attachment onward. Deliverable: File path, size, and a one-line contents note. Review point: I open the file.

💡

Pro tip: Staff: Gmail connector lists attachment metadata only. No download tool. Use the browser.

Money mail

4 prompts

Receipts to a weekly expense pack

9/21

✨ What it does

The Bot builds this week's expense summary from [EXPENSE SYSTEM], [FINANCE INBOX], and [POLICY], matches receipts, and drafts one follow-up per owner. You send the follow-ups; the Bot does not change reimbursements.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build this week's expense summary. Match receipts. Flag missing categories or policy exceptions. Sources: [EXPENSE SYSTEM], [FINANCE INBOX], [POLICY], [SHEET]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send follow-ups or change reimbursements. Deliverable: Summary, exceptions with policy cites, one draft follow-up per owner, totals that reconcile. Review point: I send follow-ups.

💡

Pro tip: Ask for policy citations on every exception, and totals that reconcile to the source.

Refund and return hunter

10/21

✨ What it does

The Bot finds unrefunded returns in the last [60] days and drafts one merchant note each, with order, amount, and evidence. You send; the Bot does not start chargebacks.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find unrefunded returns in the last [60] days and draft one merchant note each. Sources: [INBOX], [ORDERS], [RETURN POLICY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send. Do not start chargebacks. Deliverable: Merchant, order, amount, evidence, draft, confidence. Review point: I send.

💡

Pro tip: Earn-back stories are real. Sending as the Bot without you is how you look like a scammer.

Invoice due-date list

11/21

✨ What it does

The Bot lists invoices due in the next [14] days from [INBOX + SHEET], with vendor, amount, due date, and a link to the mail. You pay; the Bot does not store card numbers.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List invoices due in the next [14] days from [INBOX + SHEET]. Sources: [INBOX], [BILLING SHEET], [BANK ALERTS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not pay. Do not store card numbers. If you see a full PAN, stop. Deliverable: Vendor, amount, due, status, link to the mail. Review point: I pay.

💡

Pro tip: Never store full card numbers. If a mail has one, stop and tell you.

Stripe or billing alert triage

12/21

✨ What it does

The Bot triages billing mail from [STRIPE / PADDLE / BANK] for [7] days, putting failed charges first and separating disputes from noise. You act in the dashboard; the Bot does not refund, retry, or email customers.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Triage billing mail from [STRIPE / PADDLE / BANK] for [7] days. Failed charges first. Sources: [INBOX], [BILLING DASHBOARD] if signed in. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not refund, retry, or email customers. Deliverable: Failed / disputed / noise, with links and a draft internal note. Review point: I act in the dashboard.

💡

Pro tip: Failed charges are time-sensitive. Ask it to put those first, not "newsletter from Stripe".

Like these prompts? There are full tutorials behind them.

Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.

Try AI Academy Free

Filters and hygiene

3 prompts

Propose filters, do not apply them

13/21

✨ What it does

The Bot proposes Gmail filters from the last [14] days of mail, honoring your never-touch list [PASTE], with false-positive risk and example threads. You create the safe ones.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Propose Gmail filters from the last [14] days of mail. Sources: Inbox. Never-touch list: [PASTE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create filters. Deliverable: Filter, rationale, false-positive risk, example threads. Review point: I create the safe ones.

💡

Pro tip: Bad filters hide legal mail forever. Review every "skip inbox" rule.

Phish and fake-invoice watch

14/21

✨ What it does

The Bot scans [INBOX] for lookalike domains and unexpected payment-detail changes against [KNOWN VENDOR DOMAINS], and recommends ignore, report, or call the vendor. You report or you call; the Bot does not click links or reply.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Scan [INBOX] for lookalike domains and unexpected payment-detail changes. Sources: Inbox, [KNOWN VENDOR DOMAINS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not click links. Do not open macros. Do not reply. Deliverable: Message, why it looks wrong, recommended action (ignore / report / call vendor). Review point: I report or I call.

💡

Pro tip: If it looks like a vendor invoice with a new bank account, stop. You call the vendor.

Label scheme that matches how I work

15/21

✨ What it does

The Bot proposes at most [12] labels for how you actually work ([LIST JOBS]), with keep / merge / add rules from the last two weeks of mail. You rename things; the Bot does not delete labels.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Propose at most [12] labels for how I actually work: [LIST JOBS]. Sources: Current labels, last 2 weeks of mail. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not rename or delete labels. Deliverable: Keep / merge / add, with a rule of thumb for each. Review point: I rename things.

💡

Pro tip: If you already have labels, ask for a merge plan, not a new universe.

Make it a Bot

6 prompts

Email Bot description

16/21

✨ What it does

The Bot writes an email Bot description named [NAME], including the never-touch list, [INBOXES], your review window, and a daily output format. You create the Bot.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write an email Bot description named [NAME]. Sources: Never-touch list, [INBOXES], my review window. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Never send, never delete without an approved bucket. Deliverable: Description plus a daily output format. Review point: I create the Bot.

💡

Pro tip: Mention the Gmail connector limit on attachments so it uses the browser without being asked.

Nightly triage routine

17/21

✨ What it does

The Bot prepares a weekday run at [07:30] [TZ] that sorts new mail in [INBOX] into buckets and posts the report, plus a test plan on yesterday's mail. You enable it after the test looks right; the Bot does not delete or send during the run.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Every weekday at [07:30] [TZ], triage new mail into buckets and post the report here. Sources: [INBOX], never-touch list. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not delete or send during the routine. Deliverable: Routine card and a test-run plan on yesterday's mail. Review point: I enable after the test looks right.

💡

Pro tip: Test run does real reading. It should not do real deleting.

Handoff to the expense Bot

18/21

✨ What it does

The Bot packages this week's receipt mail and hands it to [FINANCE BOT] with the expense skill and [POLICY]. You review the finance Bot's summary; neither Bot messages employees or changes reimbursements.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Package this week's receipt mail and hand it to [FINANCE BOT] with the expense skill. Sources: [FINANCE INBOX], [POLICY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not message employees. Do not change reimbursements. Deliverable: The pack path and the handoff note you sent the other Bot. Review point: I review the finance Bot's summary.

💡

Pro tip: Agent-to-agent is the point. You still approve reimbursements.

Two-inbox junk walk

19/21

✨ What it does

The Bot walks [INBOX A] and [INBOX B] for [LABEL OR QUERY], proposes delete with counts and 15 examples, and flags anything that looks like money or legal. You approve a bucket before anything is deleted.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Walk [INBOX A] and [INBOX B] for [LABEL OR QUERY]. Propose delete. Do not delete. Sources: Those inboxes on the computer. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not delete, unsubscribe, or mark spam until I approve a bucket. Deliverable: Counts, 15 examples, anything that looks like money or legal. Review point: I approve a bucket.

💡

Pro tip: Work one label at a time. A 90k purge in one job is how you delete a tax notice.

Receipt vs newsletter split

20/21

✨ What it does

The Bot splits the last [N] days of [INBOX] into receipts, newsletters, and needs-me, and proposes three labels without applying them. You apply the labels; the Bot does not delete receipts.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Split the last [N] days of [INBOX] into receipts, newsletters, and needs-me. Do not auto-file. Sources: [INBOX], [EXPENSE POLICY] if I have one. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not delete receipts. Do not forward them yet. Deliverable: Three folders or labels proposed, not applied. Review point: I apply the labels.

💡

Pro tip: Ask for a third bucket: receipts. Do not let receipts ride with newsletters.

Unsubscribe list you still click

21/21

✨ What it does

The Bot lists senders you should leave, with the real one-click URL if it can open it, from [INBOX] over the last [N] days. You unsubscribe; the Bot does not click unsubscribe or type your email on a third-party page.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List senders I should unsubscribe from, with the real one-click URL if you can open it. Do not click unsubscribe. Sources: [INBOX], last [N] days. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not click unsubscribe. Do not enter an email on a third-party page. Deliverable: Sender, why, URL or "do this in Gmail". Review point: I unsubscribe.

💡

Pro tip: Phish loves fake unsubscribe. You click the real ones.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free →

Frequently Asked Questions

Grok Bot is an always-on AI teammate from xAI / SpaceXAI that runs on a persistent cloud computer (browser, files, terminal). You message it like a coworker and it finishes work inside the apps you already use. Grok on grok.com or in the X app is a chat assistant with live search and Grok Imagine. These pages are only for the teammate product. For chat and Imagine prompts, use the Grok prompts library.

Yes. Official docs are explicit: isolation is per user, not per Bot. Files, browser logins, and plugins on the computer are visible to every Bot on your account. Do not treat a second Bot as a security boundary. Put irreversible actions (send, pay, delete, production changes) behind approval.

Access has expanded since the August 2026 launch. It is included with SuperGrok plans and with Cursor Pro and Cursor Teams, plus a limited free trial for everyone else at times. Plans and weekly usage change. Check the official Grok Bot plans page before you buy a seat for this product.

It can operate Gmail like a person. These prompts still require you to approve a bucket before anything is deleted. Field cases (large inbox purges) work because the owner confirmed the junk. A Bot that deletes as it goes will eat a legal hold or a customer thread.

Cursor staff have said the Gmail connector can list attachment metadata but not download bytes. Use the cloud browser to open the message, or park the file in Drive. Do not paste the file into chat if it contains secrets.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

Start 7-Day Free Trial AI tools for business

7-day free trial. Cancel anytime.

Browse All Prompt Collections

Popular prompt collections

AI Photo Editing Prompts ChatGPT Jailbreak Prompt Best ChatGPT Prompts Funny Hinge Prompts ChatGPT Caricature Prompts