Email for Your Zapier or Make Agent (No Code)

This guide covers both platforms in three steps.

Step 1 - Provision a mailbox and a scoped key

Create the mailbox in the dashboard and issue a per-mailbox key - read_write to send and read, read for codes/confirmations only. Keep the sm_live_… secret in the platform's credential store:

# Keys are issued from the dashboard, not over REST - the issuance surface is
# deliberately not agent-callable, so a leaked key can never mint or revoke
# another. To get one: Dashboard → API keys → pick the mailbox + a role
# (read / read_write / management) + an optional expiry → copy the sm_live_…
# secret (it is shown ONCE). Then set it for your agent and pass it as the
# Bearer token on every REST + MCP call:
export SAIRAPH_MAIL_KEY="sm_live_…"

Step 2 - Connect over MCP (native, no code)

Both platforms can call a remote MCP server directly:

• Zapier: use the MCP Client to connect a remote MCP server, set the URL to https://mail.sairaph.com/mcp/v1/mcp, and add the Authorization: Bearer sm_live_… header. The mailbox's actions become steps you can use in a Zap or hand to a Zapier Agent.
• Make: add the MCP Client app, create a connection to https://mail.sairaph.com/mcp/v1/mcp with the same Bearer header, and the mailbox's tools appear in your scenario with their required and optional fields listed.

Step 3 - Or call REST from a generic HTTP step

If you'd rather not use MCP, every mailbox is a plain REST endpoint:

• Zapier: Webhooks by Zapier → Custom Request, method POST, URL https://mail.sairaph.com/api/v1/mailboxes/{mailbox_id}/outbound, headers Authorization: Bearer sm_live_… and a unique Idempotency-Key, with the JSON body below.
• Make: the HTTP → Make a request module with the same method, URL, headers, and body.

Send body and the read leg are the canonical REST snippets - send first:

curl https://mail.sairaph.com/api/v1/mailboxes/$MAILBOX_ID/outbound \
  -H "Authorization: Bearer $SAIRAPH_MAIL_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["agent@acme.dev"],
    "subject": "Your verification code",
    "body_text": "Reply with APPROVE to continue."
  }'

Then read inbound (poll on a schedule, or live=true for an on-demand fetch when waiting on a code):

# Read inbound from cache, or live=true for an on-demand fetch.
curl "https://mail.sairaph.com/api/v1/mailboxes/$MAILBOX_ID/messages?direction=inbound&live=true" \
  -H "Authorization: Bearer $SAIRAPH_MAIL_KEY"

How Sairaph Mail fits Zapier and Make

Generic automation tools assume you already have a mailbox - Zapier gives you a limited parsing inbox, Make makes you connect your own IMAP/SMTP account. Sairaph Mail removes that: it *is* the mailbox, provisioned and two-way, EU-hosted by default, reachable as a native MCP step or a plain HTTP step, with a dashboard to see what your scenario sent and received. See the MCP docs or the REST API docs.

Next step: get started and provision a mailbox. Sending confirmations from a scenario? See transactional notifications.