Grok BotTips

· Intermediate · Routines

Reported, not yet confirmed.

Use an email trigger when mobile hides webhook credentials

The phone app still doesn't show a webhook URL or key. BrexitBot's workaround is a mail.grokbot.com email trigger, or a forward into that inbox.

On Android and iOS, a webhook routine still doesn't show its URL, key, or Authorization header. Colin on Cursor's forum staff said on Oct 9 that those fields "only show in the Grok Bot desktop app," and that in-chat grokbot:// links to them do nothing on mobile yet. On Sunday evening, BrexitBot posted a workaround he is using without a PC: he fires the routine with the email trigger on mail.grokbot.com, or by forwarding other mail into that inbox.

How to use it#

  1. Claim the Bot's mail.grokbot.com inbox.
  2. From desktop (or by asking the Bot), attach an email trigger to that inbox.
  3. Fire it by sending or forwarding a message to that address from your phone.
  4. If saving the email trigger fails, use a short schedule that checks the inbox instead.
Prompt
Create a routine that runs when mail arrives at my mail.grokbot.com inbox. When it fires, summarize the new message in this chat. If the email trigger won't save, say so and set a 15-minute schedule that checks the inbox instead.

Good to know#

  • We did not reproduce the email trigger from a phone. Treat BrexitBot's report as one working path until you test yours.
  • Staff have not endorsed the workaround. Colin's post only confirms the webhook fields are missing on mobile.
  • Email triggers can fail to save. See the known issue.

Steps

  1. Claim a mail.grokbot.com inbox for the Bot if you haven't.
  2. On desktop, create a routine with an email trigger on that inbox (or ask the Bot to).
  3. From your phone or another service, send or forward mail to that address to fire the routine.
  4. If the email trigger won't save, fall back to a schedule that checks the inbox.

Source: BrexitBot on the Cursor forum: email trigger instead of webhook

Sources

  1. forum.cursor.com
  2. forum.cursor.com
  3. cursor.com

Something wrong? Tell the bot