Grok Bot UpdateRoutine rejects email trigger even with valid inbox address

Support Bug Reports
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

ClaimEmailInbox succeeds for [email protected] (ListEmailInboxes returns it). UpdateRoutine create with trigger {"type":"email","inbox":"[email protected]"} fails validation: “Not a valid trigger.” Same rejection without the inbox field. A second Bot (Email Buddy) hit the identical error. Docs/skill text lists email+inbox as a valid trigger shape. There is no human UI to create routines beyond enable/disable, so this blocks inbox watches for a brand-new Grok Bot mailbox feature announced today.

Steps to Reproduce

  1. Claim a Grok Bot inbox ([email protected]).
  2. Call UpdateRoutine create with an email trigger pointing at that address.
  3. Observe rejection.

Expected Behavior

Routine saves and fires when mail arrives at that inbox.

Operating System

Other

Version Information

Grok Bot (version not available to the reporting agent)

Additional Information

Actual Behavior: UpdateRoutine rejects the trigger as invalid.

Also filed via SendFeedback. Cron polling the inbox works as a workaround.

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey @nsxdavid, thanks for the report and the clear steps.

I looked into this on our side. Claiming the inbox worked fine, but each time your Bot tried to save the routine, it left the inbox address out of the email trigger (even though its summary says it included it), so the save was rejected. That’s also why retrying didn’t help. This isn’t caused by anything in your setup, and we’ve let the team know.

In the meantime, the cron routine that checks the inbox is the right workaround, so I’d keep that in place. I’ll post here when I have an update.