Set an email trigger on a Grok Automation

Point a Grok Automation at your inbox so a matching email starts a full run with that message as context, instead of waiting for a clock. Official Automations in Grok describes email triggers that watch sender, recipient, or subject filters, then fire with the incoming email as context so Grok responds to the actual message.

Email triggers need SuperGrok. Scheduled automations (daily, weekdays, and the other clock options) are available more broadly without that trigger type. Automations live on grok.com/automations and in the Grok apps; they are separate from Grok Bot routines.

Before you start

• SuperGrok on the same account you use for Automations
• A clear filter: which sender, recipient, or subject should fire the job
• Instructions that tell Grok what to do with the matching email (summarize, draft a reply for you to send, flag risk, file a note)

Keep the filter narrow. Broad matches burn usage and produce noisy runs.

Create or convert the Automation

1. Open grok.com/automations while signed in, or open Automations in the Grok mobile app.
2. Create a new Automation, or open an existing one you want to switch from a schedule to an email trigger.
3. Write instructions that assume the triggering email is the main context. Say what to extract, what to ignore, the output format, and whether Grok should only prepare a draft for you.
4. Attach standing files only if every run needs the same policy or checklist. Type @ to mention connectors the job should use on every fire when tools beyond the email matter.
5. Choose the email trigger and set filters for sender, recipient, or subject so only the messages you care about fire it.
6. Set how it reports back: email, app notification, both, or neither if you will open run history yourself.
7. Save. Send yourself a safe test message that matches the filter, or use Run now if the UI offers a manual path, then open the run conversation and confirm the brief behaved.

When an email matches, Grok opens a real conversation, does the work, and stores the result in run history. You can reopen any run and continue from that thread.

Filters that stay useful

Prefer exact sender addresses or distinctive subject prefixes over catch-alls like every message to your inbox. Mention @ connectors only when the run must pull related records; otherwise keep the job on the email body and headers. If you also want a morning digest on a clock, create a separate scheduled Automation rather than overloading one trigger — Create a scheduled Grok Automation.

To pause noisy filters, reshape the brief, or delete the job, use Pause, edit, or delete a Grok Automation. Chat-created Automations still need the same filter check on the Automations page — Start a Grok Automation from chat.

Pitfalls

• Enabling an email trigger without SuperGrok — scheduled runs may still work; the inbox trigger will not.
• Filters that match half your inbox — tighten sender or subject before you leave the Automation on.
• Instructions that assume yesterday's chat context — every fire is a fresh request with the saved brief plus the new email.
• Asking the Automation to send external mail without a human review step — keep outbound sends behind your own approval when the stakes are high.