Grok Bot can't log into Shopify

Symptom

The Bot opens the Shopify admin login in its browser, reports something like "waiting for verification", and loops. Retrying does nothing. A user reported exactly this on the Cursor forum in late August 2026.

Why it happens

The Bot's cloud computer is a datacenter machine running a headless-style browser. Bot-detection on the Shopify login page sees the network and browser fingerprint and issues a challenge. That is the system working as designed. There is no setting inside Grok Bot that changes what the machine looks like.

What not to do

• Don't paste your owner-session cookies into the Bot's browser. Every Bot on the shared computer can then use them, and so can anything that prompt-injects one of them.
• Don't try to "teach" the Bot to pass the challenge. That is the wrong side of a line we don't cross, and it will break again next week anyway.

The fix: scoped API access

1. In Shopify admin, create a staff account for the Bot (its own email, see give a Bot its own account). Give it the minimum permissions.
2. Under Apps → Develop apps, create a custom app owned by that staff account. Grant only the Admin API scopes the routine needs: read_orders for order reporting, write_customers for tagging, read_inventory for reorder alerts. Nothing else.
3. Store the token in the Bot's knowledge file or connector settings, not in a chat message.
4. Rewrite the routine to call the Admin API (GraphQL or REST) instead of clicking through the admin UI. Ask the Bot to draft the request; review the scopes it uses.
5. Test on a read-only routine first. Then add write scopes one routine at a time.

What you lose

Screens with no API (some app-embedded settings, some report exports). For those, a once-a-week human step is cheaper than a Bot that half-works.

Related integrations

Grok Bot + Shopify · Grok Bot + WooCommerce · Give a Bot its own account