Shopify_Demons Grok · Shopify

🧰 Module 2 · Grok Bot

Agents need a load path — not a chat paste

The durable home history settled on: shopify.env outside the project repo. Agents load Admin credentials from disk and report outcomes — never the token.

Get access See the outline

Public teaser. Env templates, load helpers, and agent wiring unlock after you subscribe.

Module: Grok Bot and shopify.env

✨ Public teaser

What free visitors need to know

Module 2 teaches where Shopify Admin secrets live, how Grok Bot / ops agents load them, and why the durable path is a local env file — not MCP env blocks and never paste-into-chat.

  • Load path > transcript

    Agents do not need secrets in chat — they need a file on the machine.

  • Durable home

    Pattern: C:\Users\<you>\.grok\shopify.env (outside any git repo).

  • Names only

    SHOPIFY_STORE_DOMAIN=YOUR_SHOP.myshopify.com and SHOPIFY_ACCESS_TOKEN=shpat_….

  • Direct Admin preferred

    Real ops path: remove Shopify MCP and call Admin with X-Shopify-Access-Token from that file.

  • Shared credential file

    Store Operator, catalog, and theme/SEO bots share one shop file — not a pasted token each.

  • Flowchart

    Chat paste BAD → shopify.env GOOD · MCP env optional/legacy · session logs can retain old pastes.

📁 Copyable teaser

shopify.env shape (placeholders)

Put this outside git. Never paste live secrets into chat.

shopify.env env
SHOPIFY_STORE_DOMAIN=YOUR_SHOP.myshopify.com
SHOPIFY_ACCESS_TOKEN=shpat_••••••••
# Optional: SHOPIFY_API_VERSION=2024-10

🗺️ Outline

The flow (titles public, steps locked)

  1. ★

    Public

    Prereq: Connect Grok first

    Live Admin auth proven (shop identity without 401) before bots load credentials.

  2. Locked · Subscribers

    Decide the credential architecture (MCP vs env file)

    Why history settled on one env file as the subscriber default.

  3. Locked · Subscribers

    Create shopify.env in the Grok home (not the repo)

    Path pattern, key names only — you fill values locally.

  4. Locked · Subscribers

    Load pattern agents must use

    Read file → headers → Admin REST/GraphQL — never echo the token.

  5. Locked · Subscribers

    Remove Shopify MCP when it fights the env-file path

    Plus wire ops agents, never-paste rules, prove load path, refresh lifecycle, session hygiene.

Unlock Module 2

🔒 Behind the paywall

Env + agent playbooks stay closed

Subscribers get the full Grok Bot path: env placement, load helpers, MCP remove vs keep, and never-paste operating rules. Guests get this teaser only.

  • shopify.env outside git
  • Agent load helpers (outcomes only in chat)
  • MCP remove / dual-home drift fixes
  • ~24h refresh without re-pasting
Subscribe to unlock Connect Grok first

➡️ Next

Ready to put bots on the store?

Unlock Module 2, or skim Scopes (Shopify API) for the 401 vs 403 map next.

See plans Scopes / Shopify API