← Back to all posts

Send Transactional Email from Zapier or Make — No Code Required

Most Indonesian startups think "transactional email API" means hiring a backend developer first. It doesn't. If you run on Zapier, Make.com, or n8n, you can send real transactional email — order confirmations, payment receipts, booking tickets — with zero backend code, using nothing but the Webhooks module and an HTTP request.

This is the same trick the big Indonesian platforms use, minus the engineering team. A travel booking site needs e-tickets in the inbox within seconds of payment. A food delivery app needs invoices per order. A fintech needs OTP verification codes that don't land in spam. All three are just "when X happens, POST to an email API."

The pattern: Webhooks module → POST /v1/send

Every automation platform has an HTTP module. In Zapier it's "Webhooks by Zapier" (Custom Request); in Make.com it's "HTTP — Make a request." Configure one:

• URL: https://api.mailanvil.com/v1/send
• Method: POST
• Headers:
• Authorization: Bearer <your API key>
• Content-Type: application/json
• Idempotency-Key: {{order_id}} (prevents duplicate emails when a Zap retriggers)
• Body:

{
  "from": "[email protected]",
  "to": ["{{customer_email}}"],
  "subject": "Pesanan #{{order_id}} dikonfirmasi",
  "html": "<h2>Terima kasih!</h2><p>Pesanan {{order_id}} sudah kami terima. Total: Rp {{total}}.</p>"
}

That's it. One HTTP module, one JSON body, done. The API returns 202 immediately with a queued id, then delivers via Amazon SES infrastructure.

Why this beats SMTP in Zapier

Zapier and Make both have built-in SMTP/Email actions. The differences that matter:

1. Deliverability. Platform SMTP sends come from shared infrastructure with no SPF/DKIM alignment for your domain. MailAnvil requires a verified domain with DKIM — your email arrives as yourdomain.com, not via-something.com. For OTP codes, this is the difference between the primary inbox and the spam folder.
2. Delivery tracking. SMTP integrations fire and forget. MailAnvil gives you per-recipient status (delivered, bounced, suppressed) via GET /v1/emails/:id and signed webhooks — which you can also route back into Zapier to pause customers with dead addresses.
3. Rate discipline. Bounces and complaints are tracked per customer with a kill switch (rolling complaint >0.3% pauses sending). You can't accidentally burn your domain reputation with a misconfigured loop.

Three Indonesian use cases

Travel booking (e-ticket delivery). Trigger: payment webhook confirms booking. Action: POST /v1/send with the ticket HTML and booking code. Gateways like Midtrans or Xendit fire a payment notification the moment QRIS settles — email goes out in the same second, not on a cron sweep.

Food delivery invoices. Every completed order generates an invoice email with the itemized total. With the free tier (3,000 emails/month, Rp 0), a small operation runs entirely free; above that, Pro is Rp 249rb/month for 50,000 sends — roughly Rp 5 per email, paid via QRIS or GoPay, no credit card needed.

Fintech OTP verification. Use Idempotency-Key: {{user_id}}-{{otp_request_id}} so double-taps on "Resend OTP" never double-send. Templates CRUD means your OTP layout lives server-side, and changed once, updates everywhere.

What Zapier can't replace

No-code tools handle the trigger side well, but three things still need 10 minutes in your dashboard:

• Domain verification — add the DKIM records to Cloudflare (automatic if you use CF DNS), verify in the dashboard.
• Email address verification — the from address must be verified before sending.
• Warmup awareness — new accounts start at 10 emails/day and ramp over a week. Don't blast 2,000 order confirmations on day one; that's what protects you from the spam folder, not a limit to work around.

Getting started

1. Sign up at mailanvil.com — free tier, no credit card.
2. Verify your domain and from-address in the dashboard.
3. Copy your API key into a Zapier Webhooks / Make HTTP module with the body above.
4. Send a test order confirmation. Check GET /v1/emails/:id for the delivered status.

If you're an AI-agent-first team: MailAnvil is also MCP-native (mcp.mailanvil.com/mcp), so Claude, Cursor, or any MCP client can discover and send email directly — the same API, no wrapper code.

Try MailAnvil free at mailanvil.com.