Connect Grok Bot to UserAlertX (email trigger — fallback)

Use this only if your Bot can't add a custom MCP connector. If it can, use the MCP connector instead — it's the recommended path, since every parameter is self-documented in the tool definition your Bot reads directly, rather than a separate page like this one that it has to interpret correctly on its own.

This path works with 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.

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

Go to useralertx.com/getstarted.html and enter your email.
Click the confirmation link that arrives by email.
Your api_key is on your account screen any time you sign in (it emails you a link or code - no password). Copy it from there; if it's ever exposed, press Regenerate there for a new one.

2. Your dedicated trigger address

Your address is:

in+YOUR_EMAIL_KEY@useralertx.com

Copy it from the Alert email address box on your account screen - it has its own key, not your API key. That's the whole address - no separate signup for it. 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_EMAIL_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 START; 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 credential	The `+YOUR_EMAIL_KEY` part of the address is your authorization - but only to text you, nothing else on your account. Keep it out of shared/public Bot templates. If it leaks, press New address on your account screen; you can also limit it to a list of senders (who must pass DKIM/SPF). The old `in+YOUR_API_KEY` address works until December 1, 2026.
Destination	Always 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 + body	Plain 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).
Errors	Unlike 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.