Gergely Orosz hooked Grok Bot to his customer-support inbox — and connected Stripe for routine refunds
On 19 Aug 2026 Gergely Orosz (@GergelyOrosz) wrote that he hooked Grok Bot to his customer-support emails. The Bot can connect to Stripe via API for agentic operations — routine refunds as the example. The attached screenshot is Stripe’s agent auth screen: “Agent is now authorised to continue.”
Based on a public example shared by @GergelyOrosz on X.
Support mail in, Stripe API out. He is impressed Stripe already built the agentic flow. We keep Gergely’s permalink. We did not re-run his inbox or issue a refund.
Why it's useful
Support plus refunds is the job people actually run a shop for. This is a named person showing the Bot in the live inbox and the payment API, not a generic “try agents” thread.
Who should try it
Founders doing their own support
Ops who already refund in Stripe
Anyone whose support queue is also the billing queue
From the original post
“Hooked up Grok Bot to my customer support emails... and it can connect to Stripe, via API, for agentic operations, e.g. routine refunds.”
On 19 Aug 2026 Elon quote-tweeted Mike P (@mikepat711): Grok Bot was walking two Gmail accounts — about 90,000 emails — and deleting junk Mike had never dared to touch. Elon’s line was the product tip: “Clear your email with @Grok @Bot.”
Nate Herk published “A Week of Grok Bot Lessons in 10 Mins” on X: nine hacks for turning a default Bot into a team. Elon quote-tweeted it the same morning and asked people what Bots they run.
Blake accepted a public challenge, skipped OpenClaw, and in two nights: linked email, had a Bot build a 12-page household budget PowerPoint, stood up a team for his wife’s business, and started daily Tesla news recaps.