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.
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.
Same issue here, still happening on a different account.
- Main account: the inbox was turned on and ListEmailInboxes returns it.
- UpdateRoutine create with the minimal trigger {“type”:“email”,“inbox”:“”} is rejected with “Invalid input / Not a valid trigger”.
- On the same day, a bot on our second (sub) account created an email-trigger routine successfully, so the docs’ trigger shape itself works.
- This matches the staff answer above (the bot drops the inbox field when saving). No fix has been announced yet in this thread; any update? We are on a cron/webhook workaround for now.