# Integrations

> Connect MailBlastr to the tools you already use — AI builders, no-code automation, notification platforms, CMSs, and developer tools — over its clean REST API.

MailBlastr speaks a **clean REST API**, so any tool that lets you configure an email provider over HTTP can talk to it. Anywhere a tool lets you set the API base URL, point it at `https://api.mailblastr.com` and supply your MailBlastr `mb_` key; where a tool only asks for an API key, use a MailBlastr key and (if available) its custom-host setting.

The categories below mirror the kinds of integrations developers reach for most. Each works through the same endpoints documented in these docs — there is no MailBlastr-specific protocol to learn.

## AI app builders

AI and agent platforms can send email through MailBlastr the moment you give them an API key — useful for letting an assistant or a generated app fire off transactional mail.

- **AI app builders** (Lovable, Base44, Leap.new, Rocket, Anything) — add email to apps they generate by configuring MailBlastr as the email provider.
- **Agent toolkits** (Wildcard, mcp.run, Pica, camelAI) — let an agent send natural-language emails or wire MailBlastr into a tool-use / MCP workflow.
- **Intent & enrichment** (Parsley) — push buyer-intent signals into your audiences and segments to drive targeted campaigns.

## No-code & automation

Workflow and automation platforms can call the MailBlastr API as a step, so non-developers can trigger emails from forms, spreadsheets, CRMs, and events.

- **Workflow builders** (n8n, Zapier, Make.com, Pipedream, Activepieces, Lindy, BuildShip, viaSocket, Monkedo, Email Element) — add a "send email" step backed by MailBlastr via an HTTP / API-key connection.
- **Data sync & routing** (Stacksync, ApiX-Drive) — keep contacts and audiences in sync, or use MailBlastr as a destination, between your other systems.
- **Billing & quoting** (Bunny) — quote and bill customers and send the resulting email through MailBlastr.
- **WordPress** (Post SMTP) — route WordPress mail through MailBlastr's SMTP relay or API.

## Notification platforms

Multi-channel notification engines can use MailBlastr as their email delivery provider, so MailBlastr handles the email channel while they orchestrate routing, templating, and preferences.

- Courier, Novu, Knock, Engagespot, Dittofeed, and Suprsend — configure MailBlastr (or its SMTP relay) as the email provider for their email channel.

## Content management systems

CMS platforms that send transactional mail (account, comment, and form notifications) can be configured to deliver through MailBlastr.

- Payload CMS and Strapi CMS — set MailBlastr as the email adapter / provider in their email configuration.

## Developer tools

A wide range of developer infrastructure can lean on MailBlastr for email — background-job runners, observability and billing tools, e-commerce backends, auth providers, and status pages.

- **Background jobs & events** (Inngest, Trigger.dev, Upstash, Convex, Fastgen) — send drip campaigns and event-driven email from durable workflows.
- **Backends & platforms** (Encore, Medusa, Coolify, Courrier) — send transactional and e-commerce email from your app or self-hosted stack.
- **Auth & identity** (Auth0, Kinde, Infisical) — deliver auth, billing, and verification emails through MailBlastr's SMTP relay or API.
- **Billing, analytics & ops** (OpenMeter, Invopop, Tinybird, Pulsetic, brin) — send usage/invoice email, analyze email data, or scan inbound mail.
- **Desktop & tooling** (Raycast) — manage emails, domains, and more from a launcher extension pointed at MailBlastr.

> **Note:** Integrations that exercise capabilities MailBlastr has not yet shipped will surface an error from the API. See the [roadmap](https://www.mailblastr.com/docs/resources/sdks) for what is currently supported.

## Build your own integration

Adding MailBlastr to your own product is just calling the API:

1. **Read the send reference** — Start with [Send an email](https://www.mailblastr.com/docs/api/emails-send) and the [Examples](https://www.mailblastr.com/docs/resources/examples) recipes to learn the request shape.
2. **Authenticate** — Use a scoped MailBlastr API key — sending-only is enough if you only send mail. See [API keys](https://www.mailblastr.com/docs/api-keys/overview).
3. **Wire it into your product** — Call the endpoints over HTTPS from your backend, and subscribe to [webhooks](https://www.mailblastr.com/docs/webhooks/overview) to react to delivery events.

You can build with the official `mailblastr` Node SDK or drive the API straight from the terminal — see [SDKs](https://www.mailblastr.com/docs/resources/sdks) and the [CLI](https://www.mailblastr.com/docs/resources/cli) guide.