Integrations

Email from Remix actions and resource routes.

Remix runs actions and loaders on the server, which is where a send belongs. Put the Notix client in a .server module so the bundler refuses to ship it to the browser, call it from the action that handles your form, and verify delivery events in a resource route.

The send

Send an email from Remix.

app/routes/checkout.tsx with app/notix.server.ts

// app/notix.server.ts
import { Notix } from "notix-js";
export const notix = new Notix(process.env.NOTIX_API_KEY!);

// app/routes/checkout.tsx
import type { ActionFunctionArgs } from "@remix-run/node";
import { notix } from "~/notix.server";

export async function action({ request }: ActionFunctionArgs) {
  const form = await request.formData();
  const to = String(form.get("email"));
  const { data, error } = await notix.emails.send({
    from: "Acme <receipts@acme.com>",
    to,
    subject: "Your receipt",
    html: "<p>Thanks for your order.</p>",
  });
  if (error) return Response.json({ error: error.message }, { status: 502 });
  return Response.json({ id: data?.emailId });
}

The from address must be on a domain you have verified in Notix. Step by step: the Node.js quickstart and the longer guide to sending email from Remix.

Environment

One API key, kept on the server.

Create an API key on the API keys page of the Notix console and store it as NOTIX_API_KEY in the server environment. Read it only in code that runs on the server, never in anything shipped to a browser.

A Send only key is enough for code that only sends: if it leaks, it cannot read your contacts or delete a domain.

.env

NOTIX_API_KEY=notix_xxxxxxxxxxxx
NOTIX_WEBHOOK_SECRET=whsec_xxxxxxxxxxxx

Webhooks

Verify delivery events over the raw body.

Notix signs every webhook call with the webhook's signing secret: an HMAC-SHA256 of the X-Notix-Timestamp header, a dot and the raw body, sent in X-Notix-Signature. The SDKs check the signature and refuse a call more than 5 minutes old.

Read the body as text before parsing it: the signature covers the exact bytes, and JSON that is parsed and turned back into text can change them.

app/routes/webhooks.notix.ts: call it from the route's action

import { Notix } from "notix-js";

const notix = new Notix(process.env.NOTIX_API_KEY!);
const webhooks = notix.webhooks(process.env.NOTIX_WEBHOOK_SECRET!);

export async function handleNotixWebhook(request: Request): Promise<Response> {
  const rawBody = await request.text();
  try {
    const event = webhooks.constructEvent(rawBody, { headers: request.headers });
    if (event.type === "email.bounced") {
      // Mark the address in your own records.
    }
    return new Response("ok");
  } catch {
    return new Response("invalid signature", { status: 400 });
  }
}

FAQ

Questions, answered.

Why put the client in a .server file?

Remix keeps any module whose name ends in .server out of the browser bundle, so the client and the key it reads cannot leak into client code by an accidental import.

What if the same request runs twice?

Send an Idempotency-Key header (idempotencyKey in notix-js) with a value that names the thing being sent, such as order-4471-receipt. A repeat with the same key and body returns the first result and sends nothing new; the same key with a different body is refused with 409.

Why is my send refused with a from-address error?

The from address must be on a domain you have verified in Notix. Add the domain in the console, publish the DNS records it shows, and wait for verification; until then, sends from that domain are refused.

The free plan does not ask for a card.

Guides

Send email from Remix

A Remix action that sends with notix-js, a resource route for webhooks with the raw body, and the same idempotency and error handling as the Node guide.

Docs