Forward-to-bot inbox triggers

Why it works

The bottleneck is opening another app. Email-forward triggers meet work where it already lives, so intake becomes a single gesture.

Workflow steps

1. Locate your bot’s email address / inbox.
2. Define 2–3 email-triggered routines (e.g. receipt filing, invoice parse, meeting-notes cleanup).
3. Teach the bot how to detect which routine fits (subject keywords, sender, or a tag you add when forwarding).
4. Forward a sample of each type and verify the routine output.
5. Standardize a forward habit: add a short prefix like [receipt] / [invoice] / [notes] when helpful.

Prompt / routine template

You have an email inbox that triggers routines.

Routines:
1) [receipt] — extract merchant, date, amount, category; return a one-line ledger entry.
2) [invoice] — extract vendor, due date, amount, pay status; list open questions.
3) [notes] — turn messy meeting notes into decisions, owners, and next actions.

On each inbound email: detect routine (from tag/subject/body), run it, reply with structured output. If unsure which routine, ask one clarifying question.

Connectors & routines

Bot inbox + on-email routines are the core. Optional Gmail filters that auto-forward labeled mail. Keep payment or send-external actions behind confirmation.

Source post

Grok Bot tip: your bot has its own email inbox, and an email to it can trigger a routine. Forward a receipt, an invoice or messy meeting notes, and the right workflow runs on it. No app to open, just hit Forward. #GrokBot #AI