Let the bot email customers from your own domain

The poster set up a custom-domain mailbox as an MCP connector for Grok Bot, plus a webhook so new mail triggers an automation.

What They Did

The poster found Grok Bot’s built-in mail too limited for customer-facing use, so they created a mailbox on their own domain and connected it to Grok as a custom MCP connector. Because incoming mail does not wake the bot automatically, they also added a webhook that starts a Grok automation on each new message; they note the webhook had to use Grok’s signed whsec_ secret format, not a bearer token.

How It Went

It gave them a customer-facing address on their own domain and an inbox they could open themselves, while still letting the bot react to mail as it arrived. They say Grok’s native mail works for signups and verification codes, but shares one address across bots and has no inbox view or automatic trigger.

Worth Knowing

Their main gotcha was that Grok automation webhooks rejected bearer-token requests with 400s; only signed requests using the provided whsec_ secret worked.