Connect Grok Bot to UserAlertX (email trigger)

The fastest way to hook up Grok Bot — or any agent that can already send an email, which is basically all of them: no connector to add, no plugin settings, no API key header to configure anywhere. Your Bot just sends a plain email to your own dedicated UserAlertX address, and that triggers the alert. Want a real MCP tool instead (e.g. because your Bot already manages other tools/connectors)? See the MCP connector instead.

1. Get your UserAlertX API key (one-time)

  1. Go to useralertx.com/getstarted.html and enter your email.
  2. Click the confirmation link that arrives by email.
  3. The confirmation page shows your api_key exactly once — copy it now.

2. Your dedicated trigger address

Your address is:

in+YOUR_API_KEY@useralertx.com

Replace YOUR_API_KEY with the key from step 1 (no dashes/spaces added — paste it in as-is). That's the whole address — no separate signup for it, no dashboard to visit. Save it wherever you'd tell your Bot to send an email (its memory, a note, its own settings — however you normally give it an address to use).

3. Use it

Tell your Bot something like: "When this job finishes, send an email to in+YOUR_API_KEY@useralertx.com with what happened." Whatever it puts in the subject and body becomes the alert text (both together if you use both, e.g. subject "Build finished" + body "all checks green" arrives as "Build finished: all checks green").

First use may come back with nothing visibly happening yet — that just means your phone hasn't confirmed opt-in on this number yet. You'll get a one-time text asking you to reply Y; after that, every future alert goes straight through. (This step doesn't apply if your account's delivery method is set to email instead of text.)

What this can and can't do

Address is the credentialThe +YOUR_API_KEY part of the address is your authorization — same security model as the API key itself. Don't paste your real address into a shared/public Bot template; keep it the same way you'd keep the key private.
DestinationAlways the one phone/email you verified on your own UserAlertX account. The email's content can't redirect it anywhere else — there's no recipient field to abuse.
Subject + bodyPlain text and simple HTML/multipart emails both work. Content is capped at the same limits as every other UserAlertX send path (1500 characters for the body).
ErrorsUnlike the API/MCP paths, a rejected send (bad key, rate limit, unverified account) fails silently today — no bounce back, no reply. If an alert doesn't show up, double-check the address first.