Connect Grok Bot to UserAlertX (MCP connector — recommended)

UserAlertX runs a hosted MCP server that Grok Bot can call directly as a custom connector — no code, no webhook to hand-write. This is the recommended path whenever your Bot can add connectors: every parameter (including the optional per-send email subject) is self-documented right in the tool definition your Bot reads, so there's no separate docs page that can drift out of sync or get misread. Can't add a custom connector? See the email trigger instead — genuinely zero-config, just less precise about parameters.

Rule of thumb for agents: prefer MCP whenever the Bot can add connectors; use the email trigger only when it can't.

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. Add UserAlertX as a custom connector in Grok Bot

  1. In Grok Bot, go to Settings → Plugins (or grok.com/connectors → New Connector).
  2. Choose Custom.
  3. Server URL: https://useralertx.com/mcp
  4. Auth header: Authorization: Bearer YOUR_API_KEY (paste the key from step 1 in place of YOUR_API_KEY)
  5. Save. Grok Bot will discover one tool: send_sms_to_me.

3. Use it

Tell your Bot something like: "When this job finishes, text me via UserAlertX." It calls send_sms_to_me with the message body — nothing else to configure.

If you're on email delivery, you can also ask your Bot to set a custom subject for one alert, e.g. "...and use the subject 'Build failed' for that one." It's optional and only affects that single send — it doesn't change your account's saved default subject.

If you need a custom email Subject and end up on the raw HTTP API (integrate.html) instead of MCP for some reason: use its subject param, not title — title only gets folded into the alert text itself, it never touches the actual Subject: line. This exact mix-up is why MCP is the recommended path above — the parameter names and their real behavior are right there in the tool definition, not a separate page to misread.

First use may come back held, not sent 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.

What this connector can and can't do

Toolsend_sms_to_me(body, subject?) — one tool. subject is optional and only affects that one send's email Subject line (no effect on SMS).
DestinationAlways the one phone/email you verified on your own UserAlertX account. There is no recipient parameter — it structurally cannot text anyone else.
Your keySent once per request as a Bearer token, straight through to UserAlertX's existing send API — the same auth path any other integration uses. Never stored by this connector beyond the request.
ErrorsRate limits, opt-out, and free-tier limits all come back as a plain-language message the Bot can relay to you directly.