Grok Bot: X Research, Email, Routines and Shopify Store Management

What you give it, and what to expect

Give a Bot a bounded task, sources, permitted actions and an output format. Its cloud computer retains context and files; your laptop need not stay open for cloud work. The app is documented for desktop and mobile. Access is included with paid individual Cursor plans and Cursor Teams, or an eligible linked individual SuperGrok subscription. Weekly usage applies; verify your account’s current allowance rather than assuming unlimited work. Platforms and access.

Expect a sourced summary, prepared artifact or a report of attempted changes—not an automatic guarantee that every external action succeeded. A named Bot is useful for recurring context; a simple one-off question may be better served by ordinary Grok.

Read official Grok Bot setup

X research: public search versus your account

Public posts, account posts and mentions can be searched and read without connecting your X account. Your home timeline, DMs and bookmarks require the X plugin and sign-in. Public research is read-only access, not permission to act as you. Files, browser sessions and installed connections are shared across your own Bots; separate Bot names are not credential-isolation boundaries. X access and shared computer model.

An original research brief

Review public X posts about a fictional product category during the last seven completed days. Return source URLs, post timestamps and the reason each item matters. Separate original announcements from reposts and opinion. Mark inaccessible posts. Do not post, reply, follow or message anyone.

Validate a small sample by opening the links and checking dates. A zero-result search is not proof nobody discussed the topic. An unavailable source must not become a fabricated quote. Ask for the covered time window and search limits before treating the summary as representative.

A skill is a method; a routine supplies a trigger

Save a reliable one-time method as a skill; use a routine only for supported schedules or events. Confirm the owning Bot, source, time zone, approval boundary, failure policy and displayed next run. The docs specify a minimum five-minute interval, up to 50 routines per Bot and 20 recent run records. These are not a promise of continuous X monitoring. Routine controls and limits.

Notifications depend on both device permission and the Bot setting; focused-app notifications can be suppressed. Check the conversation and run history rather than interpreting silence as success. Time zone, usage and notifications.

Our recommendation: for a topic digest, define a fixed window and deduplicate source URLs. On an unavailable source, return a failure note. Do not silently reuse yesterday’s result. Review a trial run before scheduling external write actions.

Some docs still say Marketplace or describe slash menus. The October changelog renames the entry to Connect Apps and changes slash-menu behavior. Match instructions to your installed version; do not assume an older label means the connector is absent. Current UI changes.

Install Shopify in Grok Bot, not the Grok web connector

In Grok Bot → Connect apps, search for Shopify and use the official integration. Installing through Grok’s web connectors page does not install it in Grok Bot. Bot connector responses are text; do not expect the web Grok connector’s visual storefront, chart and table components. Shopify adds no extra connector fee; normal Shopify and provider subscription costs remain. Product-specific installation and output.

Authorization redirects to Shopify to select the store and approve access. Read/write scope and the staff member’s own permissions both constrain the tool; an AI connection cannot elevate a read-only staff role. Switching stores needs authorization, then a new conversation to avoid stale store context. Authorization and store switching.

Shopify task boundaries

Swipe wide tables horizontally on a phone.

Shopify-supported operations and exclusions.

A short capability label is not enough for a write request. For example, “set stock to 40” needs the exact variant and location, a reason, and confirmation that another process has not already changed the stock. Ask for a proposed change before executing; inspect the resulting record afterward.

Review one change before a batch

Our proposed workflow is read → compare → approve a bounded change → read back → reconcile. First name the store and target IDs. Ask for current values and proposed replacements in text. Keep approval attached to those exact targets, rather than granting an open-ended instruction to “fix the store.”

After a batch, request three lists: succeeded, failed and not attempted. Check those against Shopify admin. A stopped job can leave partial changes; do not blindly rerun all items, since that can duplicate work or overwrite newer values.

Original read-only inventory brief

For the explicitly named store and location, list the five named variants with their current available quantity and item IDs. Do not change stock. Flag missing variants and ambiguous location matches. Return the read time and a proposed review list.

This is a suggested brief, not a connection or test performed by AI Tool Finder. Do not substitute real customer data into a public example.

Customer data, revocation and failure handling

Authorized data leaves Shopify and falls under the AI provider’s terms. Uninstall the integration in Shopify admin to revoke access; reducing an approved scope requires uninstalling and reinstalling with less access. Data handling and revocation.

Minimize what enters a Bot conversation: prefer aggregate counts and product IDs over customer names, addresses, emails or order details unless needed and permitted. Review retention and access rules for the entire Bot account, not just one conversation. Do not put credentials into a prompt.

If you receive advice instead of an action result, inspect whether Shopify is connected and enabled. If a batch stops, reconcile the confirmed changes before continuing in admin. An acknowledgement, notification or successful sign-in is not proof that a write completed.

Grok Bot Email: Claim an Address, Handle Incoming Mail and Set Up Routines

One permanent mailbox per user, not one per Bot. Your address is username@mail.grokbot.com. Bots in your own chats and routines can use it within permissions; other people's chats and shared Slack contexts cannot. A Team Bot does not receive a shared team mailbox.

Claiming and team access

Ask the Bot for an address and approve its confirmation card, or use the desktop Email plugin. On mobile, open Settings → Plugins → Email → Create address. A Cursor Team administrator must first enable Dashboard → Grok Bot → Bot Capabilities → Agent Email; team access is off by default.

Choose carefully: the address cannot be renamed or deleted independently. Names use lowercase letters, digits, dots, hyphens or underscores, start and end with a letter or digit, and have at most 64 characters. Reserved names include support, admin, billing, security, help, info, team, cursor, grok and xai. Availability is checked when claiming.

Incoming mail and routines

There is no default inbox view or new-message notification. Ask the Bot to search mail; a newly received message can take about a minute to appear. Incoming mail does not automatically wake a chat. Create an explicitly configured email-triggered routine for that behavior. Filters can match any sender, a specific address or a domain; subject filtering is not promised. Authenticated-sender checks apply by default.

Incoming content is untrusted information, not permission to follow instructions or send a reply. A reply is a send action: without a request in the chat or routine, the Bot should show the complete draft and ask. Auto Review may still require confirmation for an otherwise requested send.

Sending limits and lifecycle

• At most 50 recipients across To, Cc and Bcc; at most 10 attachments, 10 MB each and 25 MB combined. Oversized incoming attachments can be skipped; executable attachments are blocked on sending.
• Newsletters and first contact are limited to one recipient per message and include one-click unsubscribe. Bounces, unsubscribes and spam complaints suppress future sends to that address. Limits on contacting new people apply; the documentation does not establish an unlimited allowance or a fixed daily number here.
• Spam or virus-rejected mail does not retain body/attachments or trigger a routine. Disabling team access stops email tools and email-triggered routines but retains the mailbox.
• Deleting the account deletes mail and attachments and permanently retires the address; it is not reassigned to another person.

Four email concepts to keep separate

1. Agent Email: the dedicated mailbox described above.
2. Connected Gmail or Outlook: a separate authorized account. Specify which account should send; the Bot should ask if the choice is ambiguous.
3. Gmail verified send-as: a Gmail setting with its own ownership verification and delivery requirements. Claiming Agent Email does not configure Gmail or prove SMTP compatibility. Google currently announces removal of third-party send-as support from January 2027; consult its current help before designing around it.
4. Website signups: a Bot may receive verification mail for a signup you authorized, but this grants neither unlimited registrations nor permission to bypass the site's terms.

Proposed first workflow: review the permanent name and administrator policy, then design a routine that summarizes mail from one approved sender and produces drafts only. Review its permission and filter settings before enabling it. We did not claim an address, connect a mailbox, create a routine, register an account or send mail.

Checked October 10, 2026: Official Agent Email guide · Gmail send-as requirements and announced change. Documentation review only.

Grok Bot purchases: approval is not a blanket safety guarantee

As checked October 11, 2026, xAI's August 28 changelog describes a purchase card with an amount and Allow/Deny, followed by Link payment. Its October 7 entry describes Secure Form for checkout fields. These are documented approval flows. A personal card-photo shopping demonstration is a different kind of evidence: it does not establish universal account access, reliable completion on every merchant site, or a detailed contract for safely handling full card data in ordinary chat.

By default, do not upload raw front-and-back credit-card photos in ordinary chat. Prefer the payment confirmation and Secure Form flow explicitly supported by the product you are using. Check the real merchant domain and order source; review the final total, tax, shipping, currency, item specifications and refund policy. Separately confirm the final amount and payment authority before submission.

A Bot's ability to attempt a purchase does not mean every website permits automated buying. One successful demonstration is not a reliability benchmark. Card-data retention, third-party processing and privacy conditions for a photo-based flow remain unverified in this review; do not infer them from a public demonstration. Keep consequential payment confirmation under your own control.

Sources: xAI Bot changelog · Approvals, security and privacy. We did not upload card data, connect a payment account or make a purchase. The reported October 10 personal demonstration was not independently authenticated here and is not used as a product-access or security claim.

Who should use this, and what to do next

Useful for: a researcher who needs a repeatable sourced digest, or an authorized merchant preparing narrow catalog and inventory work. Poor fit: guaranteed real-time social monitoring, unrestricted order processing, autonomous customer-data exports or a substitute for store administration.

For a broader platform comparison, start with our Agent tools guide. For remote control of a local coding task rather than persistent cloud work, see Cursor iOS Remote Control.

Next step: read the current access rules, choose one read-only task and define what evidence would make its result acceptable. We did not operate Grok Bot, connect X or Shopify, read orders or change a store.