Integrations
Flowmails integrations — frameworks, runtimes and auth
The same SDK and the same REST surface, shown in the runtime you actually deploy to. Each page is install command, auth, one working send, and the sharp edges that belong to that runtime — not a rewritten API reference.
Cloudflare Workers
The home-runtime for Flowmails — the receive Worker, the dashboard, and the outbound send all run on Workers. The SDK works the same shape it does anywhere else.
Cloudflare Pages
Pages Functions sit on top of Workers — same runtime, same SDK. Use this when your site is on Pages and you want a contact / sign-up / notification endpoint without standing up a separate Worker project.
Next.js
The SDK works in both the App Router server components and the Pages Router API routes. Edge Runtime is fully supported; use it for low-latency transactional sends.
React Router 7
The framework Flowmails itself ships on. Call Flowmails from any server loader or action — the SDK is just a thin wrapper over the REST API.
Hono
Hono's middleware composition pairs nicely with the SDK — wrap a `/send` route, plug the SDK in, ship. Works on every runtime Hono supports.
Bun
Bun ships its own fetch implementation, and the SDK uses the runtime-native fetch (no Node polyfill). Server-side rendering and standalone HTTP servers both work.
Deno
Deno works without a package.json — import the SDK via npm: specifier. The runtime's fetch is used directly.
SvelteKit
SvelteKit's server endpoints are the natural place to call the SDK. Form actions work too — see the snippet below.
Astro
Astro's API routes work like any other HTTP server endpoint. The SDK runs in the Node / Workers runtime Astro deploys to.
Node.js
Plain Node.js, Express, Fastify, NestJS, Koa — anything built on Node 18+ runs the SDK out of the box. The SDK uses the runtime-native `fetch`, no polyfill.
Better Auth
Wire Better Auth's email verification and password-reset flows to Flowmails in four callbacks. Verification mail and reset mail go out through your own domain, so deliverability lives with your brand rather than a shared sending IP.
FastAPI
Send transactional mail from a FastAPI route by calling the Flowmails REST API with httpx — and receive inbound mail as a signed webhook with the exact verification code a FastAPI handler needs.
If your runtime speaks HTTPS, it is supported: the REST endpoint has no SDK requirement.
Keep going
- MCP server — not a framework: a hosted protocol endpoint any MCP client can drive.
- Install the SDK — the five-minute path if your runtime is not on this list.
- Raw HTTP — curl, no SDK, no runtime assumptions.