Notify
Sign in

Recipe: Send email from OpenAI dots

Have your ChatGPT dot send transactional email via Notify — cloud computer curl or a custom MCP plugin.

Use an OpenAI dot when an always-on ChatGPT agent should compose and send transactional email from your verified domain. Still not newsletters.

Connecting personal Gmail/Outlook to a dot is for that mailbox. Notify is your product send pipe: custom from, logs, and webhooks. Dots have their own cloud computer and can call HTTPS; Business / Enterprise workspaces can also add custom MCP plugins.

Dots need a supported plan (Pro / Business Premium / Enterprise beta where rolled out).

Prerequisites

  • API key (prefer a domain-locked sending_access key)
  • Verified domain for production custom from
  • A dot with access to its cloud computer (and optionally Plugins / custom MCP on Business or Enterprise)

Path A — curl from the dot’s computer (works everywhere)

  1. Tell the dot to store NOTIFY_API_KEY as a secret / credential — not in the chat transcript.
  2. Ask it to send with curl (or equivalent) and never print the key:
Send a transactional email with Notify from your cloud computer.

POST https://notify.cx/api/email/send
Header x-api-key: $NOTIFY_API_KEY
Content-Type: application/json

{
  "to": "user@example.com",
  "from": "noreply@your-verified-domain.com",
  "subject": "Status update",
  "html": "<p>Here is the update you asked for.</p>"
}

Show HTTP status and JSON response. Do not echo the API key.

Curl shape:

curl -sS -X POST https://notify.cx/api/email/send \
  -H "Content-Type: application/json" \
  -H "x-api-key: $NOTIFY_API_KEY" \
  -d '{
    "to": "user@example.com",
    "from": "noreply@your-verified-domain.com",
    "subject": "Status update",
    "html": "<p>Here is the update you asked for.</p>"
  }'

html is preferred; message and text also work.

Path B — custom MCP plugin (Business / Enterprise)

If your workspace can Add custom MCP server under Plugins:

  1. Prefer a hosted Streamable HTTP MCP that wraps Notify (Notify’s official notifycx-mcp is local stdio via npx — fine for IDE agents, not for ChatGPT’s cloud unless you host a remote bridge yourself).
  2. Create the plugin, review discovered tools, install/enable it for the account.
  3. Ask the dot: “Use the Notify plugin to send …”

Until you host a remote MCP, Path A is the reliable default. For IDE coding agents (Cursor / Claude Code / Codex), use the official MCP instead of a dot.

Custom rules

In the dot’s Custom rules, set sending email / calling Notify to Ask before taking action (or hand off). Asking for a draft is not the same as authorizing a send.

Sandbox vs production

Until the domain is verified, production custom from stays locked. Use sandbox vs production or POST /api/email/send/test for API rehearsal.

After you send

Check Email Logs or the logs API. Delivery events can go to a webhook on Pro+.

Where to next?