Send email from agents & automation

Map non-app callers — IDE MCP, n8n/Zapier/Make/Pipedream, Grok Bot, Muse, dots, agent tools, cron — to Notify’s one HTTPS send.

Most people send from an app with notifycx or fetch. Plenty of modern setups are not a website at all — workflows, personal agents, and coding agents. They all hit the same contract.

Canonical request: POST https://notify.cx/api/email/send
Auth: header x-api-key
Body: to, from, subject, and one of html / message / text

Prefer a sending_access (domain-locked) key in automation when you can. Use a full_access key only for IDE MCP setup that also manages domains and webhooks. Transactional only — not newsletters.

Built-in agent inboxes (Grok Bot mail.grokbot.com, Muse/Gmail, a dot’s connected personal mail) are not the same as Notify. Those are the agent’s mailbox. Notify is your product send pipe from a verified domain.

Pick a path

You’re in…UseStart here
App, API, or CI codenotifycx or fetchSDK · Sending
Cursor, Claude Code, Codex, WindsurfOfficial MCP/mcp · MCP guide
n8nHTTP Request noden8n recipe
ZapierAPI by Zapier / WebhooksZapier recipe
MakeHTTP moduleMake recipe
PipedreamHTTP or Node stepPipedream recipe
Grok BotSecret + curl / HTTPSGrok Bot recipe
Meta MuseCustom Connector + Secure CredentialsMuse recipe
OpenAI dotsCloud computer curl (or custom MCP plugin)dots recipe
LangChain, CrewAI, Vercel AI SDKfetch inside a toolAgent frameworks recipe
Custom GPT / Claude ActionsOpenAPI actionCustom GPT & Claude Actions
cron, GitHub Actions, Vercel Croncurl / HTTPSCron / GHA recipe
Retool, AppsmithREST resource / queryRetool / Appsmith recipe

MCP helps coding agents set up, test, and send during an IDE session. It does not replace putting send in your product codebase. Cloud agents (Grok Bot, Muse, dots) usually call the same HTTPS endpoint — Notify’s official notifycx-mcp is local stdio for IDEs, not a hosted remote MCP URL.

Shared payload

POST /api/email/send HTTP/1.1
Host: notify.cx
Content-Type: application/json
x-api-key: your_api_key

{
  "to": "user@example.com",
  "from": "noreply@your-verified-domain.com",
  "subject": "Hello",
  "html": "<p>It works.</p>"
}

Production custom from needs a verified domain. New accounts stay sandbox-only until then.

Pricing

Free: 1,000 emails/mo. Pro: $10 / 10,000. Scale: $50 / 100,000.

Where to next?