Grok Bot + WooCommerce
How to connect Grok Bot to WooCommerce with a Bot-owned account, the routines that work, the one thing to put behind approval, and our verdict.
How a Bot connects
WooCommerce REST API keys generated for the Bot's WordPress user, read or read/write per routine. WordPress admin is usually reachable by browser, but use the API anyway.
The Bot's identity
A WordPress user with the Shop Manager role (or a trimmed custom role); API keys created under it. Don't reuse a human's login. If you did, see shared computer cleanup.
Routines we've run
- Daily — processing orders older than 48h: list and draft status updates
- Daily — stock below threshold; supplier PO drafts
- Weekly — abandoned-cart follow-up drafts (if you collect consent), for approval
Each routine follows the four-part shape: when it runs, what it reads (bounded), what it produces, when it stops. See routines best practices.
The thing to gate
Plugin updates and theme edits. The Bot should never touch WordPress admin settings; ops only.
Verdict
Works well; simpler auth than Shopify. Watch for plugin-specific data that isn't in the REST API.
Setup notes
- Test every routine supervised until it's produced the right output three times.
- Add the routine's completion line to your heartbeat log so silent failures show up.
- Put the WooCommerce token in the Bot's connector settings or knowledge file, never in a chat message.
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.