Notify
Sign in

Recipe: Send email from Meta Muse

Connect Muse to Notify with a Custom Connector — OpenAPI, Secure Credentials Store, then transactional send.

Use Meta Muse when your personal agent should send transactional email from your verified domain — confirmations, receipts, ops notices you approve. Still not newsletters.

Built-in Muse email connectors (for example Gmail) are for your connected inbox. Notify is the product send API: custom from, logs, and webhooks. Muse builds a Custom Connector from public API docs — Meta does not need Notify on its curated connector list.

Prerequisites

  • API key (prefer a domain-locked sending_access key)
  • Verified domain for production custom from
  • Muse access (app, muse.ai, or WhatsApp where available)

Ask Muse for a Custom Connector

Paste one message (edit the from / job to match yours):

Build a custom connector for Notify so you can send transactional email.

OpenAPI: https://notify.cx/openapi.yaml
Send docs: https://notify.cx/docs/how-to-send-email-from-rest-api

Canonical send:
POST https://notify.cx/api/email/send
Header: x-api-key (not Bearer)
Content-Type: application/json
Body: to, from, subject, and one of html / message / text

I will give you the API key through the Secure Credentials Store — never ask me to paste it in chat.
Store it as NOTIFY_API_KEY and send it as the x-api-key header on every request.

Test with a send to my address, show me the response, then save the integration as a reusable skill.
Keep approval on for any send.

Hand over the key securely

When Muse prompts for credentials:

  1. Use the Secure Credentials Store flow (masked field) — not the chat thread.
  2. Name the secret NOTIFY_API_KEY.
  3. Approve egress to notify.cx when Sentinel / Muse asks.

Pasting a key into chat defeats Muse’s design and leaves it in history.

Approval policy

Under Muse Settings, keep send (write) actions on ask before acting until you trust the connector. Read-only is wrong for this job — you need send — but unattended “always allow” on email is rarely what you want.

What a successful send looks like

Muse should POST JSON like:

{
  "to": "user@example.com",
  "from": "noreply@your-verified-domain.com",
  "subject": "Your order confirmation",
  "html": "<p>Thanks — we got your order.</p>"
}

html is preferred; message and text also work.

Sandbox vs production

Until the domain is verified, production custom from stays locked. Point Muse at sandbox vs production and, for API rehearsal, POST https://notify.cx/api/email/send/test with the same body shape.

After you send

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

Where to next?