Check official pricing and availability. Model versions must be checked in each case.
Sales, Marketing & SupportInput: Post-meeting voice memos or dictated messages → Process: Transcribe, denoise, match record, map fields with source quotes → Output: Field proposals with verbatim citations, written to CRM only after confirmation
Read the case’s method and prerequisites
Prerequisites: a grok-bot thread that can receive voice messages, plus query access to Salesforce records. Slack is an optional notification channel. Input format is voice memos or raw dictated text. Cost conditions unknown. Boundary constraints: no inference for unmentioned field values; no rounding numbers; ambiguous records must be asked, not guessed; a single ambiguous field does not block the rest; human confirmation required before write.
salesforce · slack
Associated by case tags. Verify costs, permissions and actual results in the case.
Life Admin & HomeInput: specify mailbox and time range → Process: search by sender groups and flag sensitive mail → Output: line-by-line approval cleanup proposal with samples
Read the case’s method and prerequisites
Start a new dedicated chat with grok-bot and paste the BOT.md role protocol as system prompt or first message. Requires web access to the target Gmail account; without an API connector, manually type search strings into the Gmail web client and feed result counts back to the model. Default scope is everything older than 12 months; one account per run. The model never auto-deletes, empties trash, unsubscribes, or asks for passwords/2FA codes.
gmail
Associated by case tags. Verify costs, permissions and actual results in the case.
Money, Bills & BenefitsInput written expense policy and week's transactions → pull receipts from Gmail and Drive → output match report, policy exceptions, and human-reviewed chase drafts
Read the case’s method and prerequisites
Prerequisites: grok-bot access; read permissions for Gmail, Google Drive, and Google Sheets; written expense policy with limits and categories (not a summary). This template is a role protocol—configure the BOT.md content as a system prompt or conversation starter. Tool integrations are labeled suggestions; actual connector setup (OAuth/API) is not provided and must be done separately. Output goes to a document draft requiring human review before sending.
gmail · google-drive · google-sheets
Associated by case tags. Verify costs, permissions and actual results in the case.
Content & CreativeInput: confirmed outline + target reader + purpose → Process: strict outline adherence, no invention, no padding → Output: flagged first-draft document with issue list
Read the case’s method and prerequisites
Prerequisites: a confirmed outline (with section order), a stated reader, and a stated purpose. All three are required; the assistant will ask and stop if any are missing. Runtime: grok-bot (specific version not stated in source). Optional integrations: Google Drive, Notion (frontmatter labels only, connector status unverified). Hard boundary: never publishes, never sends, never invents facts to fill gaps; thin sections are flagged, not padded. Cost: unknown.
google-drive · notion
Associated by case tags. Verify costs, permissions and actual results in the case.
Life Admin & HomeInput: Flight confirmation emails in Gmail → Process: Extract bookings, de-duplicate, compute check-in open time, build prep checklist → Output: Per-flight structured prep pack with three-stage reminders
Read the case’s method and prerequisites
Prerequisites: a grok-bot runtime environment with authorized access to Gmail (to read flight confirmation emails) and Google Calendar (to write reminders). Input is flight confirmation, itinerary, e-ticket, or schedule-change emails in your inbox, which must contain a six-character record locator (PNR). The bot runs twice daily, morning and evening. Cost conditions are unknown and depend on grok-bot runtime and mail/calendar API billing. Known limitations: the bot only organizes information and sends reminders; it does not perform any booking changes. If it cannot confirm check-in open time from airline rules, it states so rather than assuming 24 hours. It does not guess passport, visa, seat, or baggage details.
gmail · google-calendar
Associated by case tags. Verify costs, permissions and actual results in the case.
Sales, Marketing & SupportRead open deals for this quarter and next → match against calls, emails, and internal messages → flag slipping/silent/blind patterns and draft owner-reviewed notes
Read the case’s method and prerequisites
Prerequisites: Salesforce read access (opportunity fields, close-date history), Gong/Granola call and meeting-note access, Gmail read access (filtered by account domain), and Slack internal channel read permissions. Runtime is grok-bot. Recommended schedule: weekday evenings and two hours before weekly pipeline review. Source does not specify API versions or connector configuration; verify OAuth scopes for each system before production use.
salesforce · granola · gong · slack · gmail
Associated by case tags. Verify costs, permissions and actual results in the case.
Life Admin & HomeInput staples list, 4-week order history, and next-week calendar → predict restock needs with price checks → output a priced basket (stops before checkout, hands to you)
Read the case’s method and prerequisites
Prerequisites: access to grok-bot; prepare four weeks of order history (item name, size, quantity, unit price, date), standing staples list, and next 7 days of Google Calendar. Frequency: run once per week on your agreed shopping day, in a fresh chat. Boundary: the assistant never places orders, never pays, never enters checkout. If the retailer supports cart-filling without a payment step, it will populate the cart; otherwise it outputs a paste-ready list. Use a dedicated shopping account for each retailer instead of your household primary account.
amazon · costco · google-calendar
Associated by case tags. Verify costs, permissions and actual results in the case.
Money, Bills & BenefitsInput read-only balances, transactions, holdings & calendar outflows → run protocol for cash runway, anomaly scan, portfolio drift & fee tally → output one-screen daily report with source attribution
Read the case’s method and prerequisites
Prerequisites: environment supporting grok-bot. Read-only access to Plaid (accounts), Yahoo Finance (holdings), and Google Calendar (scheduled outflows) is suggested but not configured in the source. Prepare account last-four digits, transaction IDs, tickers for source attribution. Cost: unspecified by source.
plaid · yahoo-finance · google-calendar
Associated by case tags. Verify costs, permissions and actual results in the case.
Sales, Marketing & SupportInput Gmail inbox → filter by budget tier and brand fit → output ranked shortlist and log to Google Sheets
Read the case’s method and prerequisites
Prerequisites: accessible Gmail inbox and Google Sheets edit permissions; grok-bot runtime environment configured by the operator (specific version not stated in source). Source integrations tag [gmail, sheets] is a suggested tool list, not a pre-configured connector. Cost conditions unknown. Schedule: every weekday at 08:00, scanning the previous 24 hours.
gmail · google-sheets
Associated by case tags. Verify costs, permissions and actual results in the case.
Sales, Marketing & SupportInput Gmail negotiation thread + Google Sheets historical deals → agent rebuilds deal state, extracts sponsor intelligence, prices from your own records, builds concession ladder → outputs one-page strategy brief for human send-off
Read the case’s method and prerequisites
Prerequisites: access to grok-bot runtime; a complete Gmail email thread with one sponsor; a Google Sheets deal history (including charged amount, deliverables, and post-campaign reports). This template is a role protocol—paste it into the agent's system/role field. Boundary constraint: the agent never replies directly to sponsors and never commits to any rate; all output is for operator review before human send-off.
gmail · google-sheets
Associated by case tags. Verify costs, permissions and actual results in the case.
Work & OperationsRead the sibling-bot registry → detect stalls against SLA → nag once in shared chat → page you only for human-required issues
Read the case’s method and prerequisites
Prerequisites: multiple bots running on the same computer or shared session, and you can maintain a bot registry or sibling list. Input form: feed BOT.md into grok-bot as its system/role prompt. Required materials: sibling bot names, per-task SLA timeouts, Slack group/channel names. Cost: unknown. Boundary constraints: never restart, edit, or delete another bot; stay completely silent when the fleet is healthy.
slack
Associated by case tags. Verify costs, permissions and actual results in the case.
Work & OperationsControl a pre-registered fleet of bots from a single private Telegram thread, with allowlist boundaries and mandatory confirmation for sensitive actions.
Read the case’s method and prerequisites
Prerequisites: one confirmed private Telegram chat or private group; permission to edit the identity file and roster file; grok-bot runtime configured. Boundary constraints: only contact allowlisted numbers or groups; never join public groups as the operator; no blasting; send/post/pay/delete actions require explicit yes from the allowlisted user. Not tested by this site.
telegram
Associated by case tags. Verify costs, permissions and actual results in the case.
Work & OperationsInput: shared /workspace with ops boundaries → Process: weekday cadence inventory, archive, backup, collision flagging → Output: live registry + weekly org review
Read the case’s method and prerequisites
Prerequisites: xAI Grok Bot account (one persistent cloud computer per account), GitHub private repo access. Input form: paste BOT.md role protocol as system prompt. Required materials: read/write access to /workspace, operator-named registry file, allowlisted backup directories, custom retention days (default 14). Cost: unknown. Boundaries: never delete another bot's working tree without operator-approved named archive step; never commit secrets including .env, *.pem, cookies, private keys; screens are not a security boundary.
github
Associated by case tags. Verify costs, permissions and actual results in the case.
Shopping & ErrandsInput your kitchen inventory with rough expiry dates → rank by what expires soonest → get 3 dinner options with cook times and missing items
Read the case’s method and prerequisites
Prerequisite: maintain a running kitchen inventory in Notion or Google Drive with items and rough expiry dates. Paste the BOT.md role protocol as the grok-bot system prompt, then send your current inventory each evening. Hard boundary: the assistant never orders groceries, never adds to cart, never opens delivery apps; it only suggests takeout when every option would require shopping. If inventory is stale (>5 days), outputs are marked as guesses.
notion · google-drive
Associated by case tags. Verify costs, permissions and actual results in the case.
Sales, Marketing & SupportInput Gong call records and sales data → read evidence by priority, rebuild timeline, extract buyer quotes → output one-page Notion memo
Read the case’s method and prerequisites
Prerequisites: read-only access to Gong (call transcripts, emails, messages) and CRM (stage dates, pricing sends, attendees); configure a value floor and weekly scheduling trigger (e.g., cron or workflow tool). Runtime: grok-bot. Boundary: never contact the buyer, never edit CRM records or close reasons; memo writes to internal workspace only. Note: template lists integration tags without specific connector configuration.
gong · notion
Associated by case tags. Verify costs, permissions and actual results in the case.
