Learn to configure Grok bots that auto-label your inbox and get their own email address using Agent Mail webhooks for automated routines.
What does it mean to give a Grok bot its own inbox? #
A Grok bot with its own inbox is an AI agent connected to a dedicated email address that it can send from and receive into, triggered by a webhook instead of a fixed schedule. Rather than checking email every 30 minutes on a timer, the bot sits idle until an incoming message fires a webhook, at which point it wakes up, reads the email, and takes action, like replying, forwarding, or executing a task such as placing a trade. This setup uses two components: Grok’s bot builder for the logic and routines, and Agent Mail, a separate service that provisions real inboxes and pushes webhook notifications when mail arrives.
TL;DR #
- Grok bots can run on two trigger types : a timed schedule (say, twice a day) or a webhook that fires the instant a new email lands, which is what lets a bot react in near real time instead of polling.
- The simplest setup is an inbox-cleaning bot that connects to your existing Gmail or Outlook account, sorts incoming mail into labels like primary, notifications, outreach, and urgent, and can be built in roughly 5 to 10 minutes.
- A more advanced setup gives the bot its own email address through Agent Mail, a service that provisions inboxes (on a shared domain or a custom one) and issues webhooks when messages arrive.
- Connecting the two systems requires copying a webhook URL and an authorization key from Grok into Agent Mail’s endpoint settings, formatted as an
Authorization: Bearer <key>header. - Each bot should be scoped to one inbox , since a webhook subscribed to “messages” will fire for any connected inbox by default, and without filtering, two bots can end up processing the same emails.
- The webhook URL and API key function like a password , and anyone with both can trigger the bot’s routine, so they need to be treated with the same care as any other credential.
- The bot builder interface is still evolving , and some steps (like viewing the webhook address) required an app update to work correctly during setup.
How do you set up a basic Grok bot to organize your inbox? #
The entry-level version of this workflow doesn’t require Agent Mail at all. It only needs a Grok bot connected directly to an existing email account.
The process starts by creating a new bot and giving it a plain-language job description: what labels to use, and what kind of email belongs in each one. A working example from the demonstrated setup used four categories:
- Primary : active conversations with people, marked as high priority
- Urgent : bills, invoices, or time-sensitive items, also marked as high priority
- Notifications : automated messages from banks or subscribed services
- Outreach : sponsorship pitches, collaboration requests, and similar cold contact
During setup, the bot can suggest refinements. In the demo, the bot proposed adding a “newsletters” category after noticing a high volume of newsletter traffic, which the operator accepted.
Once the categories are locked in, the next step is connecting the actual email account through the marketplace (Gmail and Outlook are both supported as native connectors), giving it a label so multiple inboxes can be managed separately if needed. From there, a routine is created to run on a schedule, twice daily was used in the example, at set times, with the bot sending a notification (in this case, a direct message to a messaging platform) summarizing what it found and flagging anything urgent. The bot doesn’t draft replies at this stage. It only classifies and flags.
How do you give a Grok bot its own email address? #
This is where Agent Mail comes in. Agent Mail is a separate service that provisions inboxes independent of your personal Gmail or Outlook account. It offers a free tier for getting started, with a dashboard showing deliverability stats like emails sent and received per inbox.
To create an inbox, you pick a username and a domain (a default agentmail.to domain is available, or a custom domain can be connected). Once created, that inbox behaves like a real mailbox: it can receive messages, and you can view and respond to them directly inside the Agent Mail interface.
From there, the connection to Grok happens through Agent Mail’s native connector in the Grok marketplace. Adding an account authorizes Grok to access the Agent Mail inbox, similar to how OAuth works for Gmail. After authorization, a new bot is created and given a role (in the demonstrated example, an assistant bot named Stephanie), and a routine is set up with a webhook trigger rather than a time-based schedule.
How does the webhook connection actually work? #
A webhook is a way for one application to notify another automatically when something happens, instead of the second application having to repeatedly check for updates. In this context, Agent Mail notifies Grok the moment a new email arrives at the bot’s dedicated address, and that notification is what wakes the bot’s routine.
Setting this up involves passing two pieces of information between the two platforms:
- The webhook URL , generated inside the Grok routine, which tells Agent Mail where to send its notification.
- An authorization key , also generated inside Grok, which proves the notification is legitimate.
Built like a system. Not vibe-coded.
Remy manages the project — every layer architected, not stitched together at the last second.
Inside Agent Mail’s webhook settings, you add a new endpoint, paste in the Grok-generated URL, and subscribe it to the relevant event (in this workflow, new messages). Then, under advanced or custom header settings, you add an Authorization header with a value formatted as Bearer <your key>. Once saved, that endpoint is live, meaning any new email to that inbox pushes a notification to the connected Grok bot, which then runs its routine.
Is this setup reliable, and what are the rough edges? #
The two-part transcript makes clear this is a relatively new integration, and the interface had some friction during setup. At one point, the webhook address and key weren’t visible in the routine view until a desktop app update was installed. The Agent Mail interface also required careful manual entry of the authorization header rather than offering an easy dropdown.
There’s also a scoping issue worth planning for upfront: if you run multiple inboxes and multiple bots (for example, one bot handling trading-related email and another handling general assistant replies), a webhook subscribed broadly to “messages” can notify every connected bot, not just the one meant to handle that specific inbox. Without explicit filtering instructions telling a bot to ignore emails not addressed to its own inbox, you risk cross-talk between bots that should be operating independently. Grok can be told directly, as a routine instruction, to only act on emails from a specific inbox, which works as a practical filter even if it’s not a clean built-in setting.
Frequently Asked Questions #
What is Agent Mail used for in this setup?
Agent Mail provisions dedicated email inboxes that aren’t tied to a personal Gmail or Outlook account, and it generates webhooks that notify connected tools like Grok the moment a new email arrives, which lets a bot react instantly instead of checking on a timer.
Do I need Agent Mail just to sort my personal inbox?
No. Basic inbox organization (labeling, flagging urgent items, sending twice-daily summaries) can be built using Grok’s native Gmail or Outlook connectors alone. Agent Mail is only needed if you want a bot to have its own separate, dedicated email address.
What triggers a Grok bot when it has its own inbox?
A webhook. Instead of running on a fixed schedule, the bot’s routine is configured to fire whenever Agent Mail sends a notification that a new message has arrived at its connected inbox.
Is it safe to share the webhook URL and API key?
No. Both should be treated like a password. Anyone who has the webhook URL and its authorization key can trigger the bot’s routine, potentially making it perform unwanted actions, so they should never be shared or posted publicly.
Can one Grok bot manage multiple inboxes?
You can connect multiple email accounts and label them separately, but if you want distinct bots to act only on their own inbox’s messages, you generally need to add explicit instructions in the routine telling the bot to ignore messages that aren’t addressed to its assigned inbox.