Grok Bots Directory
Submit a Grok Bot

Ask business numbers with a Grok Bot: pick a public template when Data Bot is not importable

On 2026-11-02, @bot described an internal Team Bot called Data Bot: on-demand data scientist for product usage, campaign results, dashboards and KPIs. That bot is not in the public template gallery. This playbook tells directory operators and importers what to point people at instead, and how those listings should stay labeled on Grok Bots Directory.

Grok Bot @bot

Source: xAI Data Bot Team Bot post · · Checked on

The playbook

Official post vs what you can install. The 2026-11-02 @bot post shows a Team Bot used inside xAI. Team Bots and public Bot templates are different surfaces. As of 2026-11-03, neither the public template gallery nor Grok Bots Directory lists an importable bot titled Data Bot from that post. Do not invent a fake official listing, and do not rewrite a community template's title to "Data Bot".

Public path that matches the job. Prefer Numbers Desk when someone wants plain-English questions on business numbers, written metric definitions, "How I got this" on every answer, a live dashboard Page, anomaly alerts and a Monday brief. It is read-only by design. Setup connects marketplace plugins as needed: Stripe, Shopify Merchant, QuickBooks Online, Xero, PostHog, Google Sheets, HubSpot, Supabase (Postgres), or a CSV. Public pack: KonectEaze reply under the Data Bot thread, share x.ai/bot/alyvookofdqjtvd2kot1a.

When to use Querie instead. Point to Data Science (Querie) only when the team already lives in Hex + Databricks SQL and wants an analyst-style query owner inside a multi-bot pod. It is not the default SMB ask-the-data path. Share x.ai/bot/bu2seqqu0hejpbzn_07d3 (Emily's pod post).

Adjacent, not substitutes. Damwright is lakehouse architecture and modeling (engineering), not day-to-day KPI Q&A. Tally (share n3sep6iy6bhiipcws6hqo) is a narrow paid-media Slack reporting dispatcher. Keep them out of "install Data Bot" answers unless the ask is specifically lakehouse design or paid-media pulls.

Directory copy rules. When someone asks to "install Data Bot" or quotes the @bot thread: (1) say the official bot is an internal Team Bot and is not publicly importable; (2) offer Numbers Desk as the closest public template for ask-the-data / dashboards / KPI briefs; (3) offer Querie only if they name Hex or Databricks; (4) link GBD pages or add_url, never claim Numbers Desk is Data Bot.

Where this guide stops. We did not import Numbers Desk or Querie for this draft. Plugin menus and Team Bot packaging can change; re-check after 2026-12-01 or when xAI publishes a public Data Bot template. See also Import and customize a Grok Bot template and Add plugins to a Grok Bot.

List and answer for the Data Bot ask

  1. Keep the boundary in one sentence

    Write (or reuse): "@bot's Data Bot is an internal Team Bot; there is no official public import. For the same job in a public template, start with Numbers Desk." Do not use Data Bot as the listing title of any community pack.

  2. Confirm or refresh the Numbers Desk listing

    Canonical fields as of 2026-11-03: slug numbers-desk, share_url x.ai/bot/alyvookofdqjtvd2kot1a, add_url grokbot://app/v1/bot-template?id=alyvookofdqjtvd2kot1a, x_url https://x.com/KonectEaze/status/2117406199406838059, x_handle KonectEaze. Prefer labels Analytics and Data; keep Finance only if Stripe/QuickBooks/Xero setup is central. Avoid calling it Data Bot in title or body.

  3. Keep Querie as the analyst-stack alternate

    Slug data-science-querie, share_url x.ai/bot/bu2seqqu0hejpbzn_07d3, add_url grokbot://app/v1/bot-template?id=bu2seqqu0hejpbzn_07d3, x_url https://x.com/egavrilenko11/status/2093409119302791170. Labels Analytics / Data. Body should say Hex + Databricks, not "public Data Bot".

  4. File adjacent bots without promoting them as Data Bot

    Damwright: slug damwright, share u9yedcqf8xzy-wfq_bbc0 — lakehouse / modeling. Tally (paid media): slug tally, share n3sep6iy6bhiipcws6hqo — Slack + spend reporting. Link them from this playbook's inspired list only with a one-line caveat, not as the default answer.

  5. Answer "帮我安装 Data Bot" / "install Data Bot"

    Reply pattern: (1) official Data Bot is not importable; (2) here is Numbers Desk add link + GBD page; (3) first chat: run getting-started, connect only the sources they use, pause routines until timezone and metric dictionary are set; (4) if they say Hex/Databricks, send Querie instead; (5) remind read-only — Numbers Desk must not write refunds or move money.

  6. Optional: same_tweet or curated shelf later

    A same_tweet collection on the @bot status can hold community replies that pack public templates. A curated task hub for "ask business numbers" belongs in collections (editorial lead + member shelf), not inside this playbook. Publish this playbook only after Lee reviews; status stays draft until then.

Inspired templates4

Public templates near the Data Bot job. Numbers Desk is the default; Querie needs Hex/Databricks; the others are adjacent only.

Numbers Desk

Numbers Desk

by Pablo

A data person on call for small businesses: connect Stripe, Shopify, QuickBooks, PostHog or a Google Sheet, ask about your numbers in plain English, and get an…

  • Memories4
  • Skills6
  • Routines3
Damwright

Damwright

by GenXer

A lakehouse architect that takes data requests through conceptual, logical, and physical models fit to your layering approach (medallion, Data Vault, Kimball m…

  • Memories3
  • Skills25
  • Routines0
Tally

Tally

by Miguel Cruz

A paid-media reporting bot. It watches your Slack for performance and metrics questions, pulls the numbers from Supermetrics right away, and DMs you the answer…

  • Memories8
  • Skills2
  • Routines2

More playbooks

All playbooks