Introduction
Notifyzr is an open-source, API-first platform for the messaging a product needs to send: transactional email, marketing broadcasts, lead capture, and the automations that tie them together.
It is built as a small set of services behind one reverse proxy. The dashboard is not privileged — it is a client of the same API you use.
What is in it
| Area | What it does |
|---|---|
| Contacts | A CRM-shaped store of people, with custom properties and tags. Bulk import from CSV. |
| Segments | Saved filters over contacts. Membership is computed on read, never materialised. |
| Templates | Reusable email content with {{ placeholder }} variables and a draft/published state. |
| Sending | POST /v1/send for one message; broadcasts for one message to an entire segment. |
| Forms | Hosted lead-capture endpoints that emit an event on submission. |
| Automations | Event-triggered graphs of conditions and actions. |
| Webhooks | Signed HTTP callbacks for every domain event. |
| Unsubscribes | A hosted opt-out page and a suppression list enforced across every send path. |
How the pieces fit
Everything is organization-scoped. An API key belongs to exactly one organization, and every record it can reach belongs to that organization. There is no cross-organization call.
State changes emit domain events (contact.created, form.submitted, email.delivered, …). Those events are what webhooks deliver and what automations trigger on — so an integration you build and an automation a user configures are reacting to exactly the same thing.
Next
- Quickstart — from a fresh account to a delivered email.
- Authentication — how API keys work.
- MCP server — connect an AI assistant to your Notifyzr data.