Notify
Sign in

Recipe: Send email from Zapier

Call Notify from Zapier — API by Zapier or Webhooks Custom Request with x-api-key.

Use Zapier when a Zap should fire a transactional email after another app event — form submit, CRM update, payment. Still transactional, not newsletters.

No Notify Zapier app is required. Call the HTTPS send endpoint with your API key.

Prerequisites

  • API key (prefer a domain-locked sending_access key)
  • Verified domain for production custom from
  • A Zap with a trigger that already has the recipient address

Preferred: API by Zapier

API by Zapier keeps the key in an app connection instead of a plaintext step field.

  1. Add an action → search API by Zapier → API Request.
  2. Create a connection that sends a static header:
    • Header name: x-api-key
    • Header value: your Notify API key
  3. Method: POST
  4. URL: https://notify.cx/api/email/send
  5. Also set Content-Type → application/json
  6. Body (JSON), mapping fields from earlier steps:
{
  "to": "user@example.com",
  "from": "noreply@your-verified-domain.com",
  "subject": "Your order confirmation",
  "html": "<p>Thanks — we got your order.</p>"
}

Replace literals with Zapier field tokens from the trigger (email, name, etc.).

Alternative: Webhooks by Zapier

  1. Action → Webhooks by Zapier → Custom Request (or POST with Payload Type JSON).
  2. Method: POST
  3. URL: https://notify.cx/api/email/send
  4. Headers:
    • Content-Type → application/json
    • x-api-key → your API key
  5. Data: the same JSON body as above.

Anyone with edit access to the Zap can see step-level secrets. Prefer API by Zapier when you can.

html is preferred; message and text also work.

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?