Your app decides who gets which email. We make it look like your brand.
Welcome, onboarding, weekly digest, win-back — your product picks the person and the moment with one call. Content Agents renders the email in your brand style, in their language, and delivers it.
Three calls. No email stack to build.
Add a person, enroll them in a sequence, stop the enrollment. Every email is an ordinary newsletter saved in your brand's Content Agents account — designed once, sent whenever your product says so.
- Connect with your brand API key — Your backend talks to the Content Agents MCP endpoint with the brand's API key. No separate email service, SMTP setup, or template engine to run.
- Emails designed in your brand style — Each email is a saved newsletter in your brand's account, built in the same composer and look as everything else you send. Edit the copy without shipping code.
- Merge fields from your own data — {{first_name}} and any attribute you send — nested ones too, like {{counts.photos}}. Values are HTML-escaped, and link fields render only when they are https.
- Every person in their language — Set a language per person. Hebrew and Arabic render right-to-left, and the footer is localized in English, Hebrew, and French.
- Retry-safe by design — Enrolling the same person in the same sequence twice never sends twice. A network blip or a retried job cannot double-send.
- Events pushed to your webhook — Delivered, opened, clicked, bounced, unsubscribed — sent to your own endpoint, signed with HMAC-SHA256, ready to record and forward to your analytics.
What it looks at
- Add — Create or update a person with first name, language, and any merge fields. Attributes merge, so send only what changed.
- Enroll — Enrolling in a sequence is the send. A one-step sequence is a "template"; multi-step drips with delays and open/click branches work too.
- Stop — Stop an enrollment the moment the goal is met — the user finished onboarding, so the reminders stop.
- Listen — Signed webhook events tell your app what happened to every email, keyed by the newsletter it came from.
Your product owns the timing. We own the inbox side.
Your app decides
- Who gets an email
- Which email, and when
- What personal details go into it
- When to stop the follow-ups
Content Agents handles
- Rendering it in your brand style and the person’s language
- Delivery, with one-click unsubscribe in Gmail and Yahoo
- One unsubscribe that covers every newsletter and sequence of the brand
- Automatic suppression of hard bounces and spam complaints
How it works
- Design the emails — Write each lifecycle email as a newsletter in your brand's account, with merge fields where the personal details go.
- Add your users — Your app adds or updates each person with their name, language, and the attributes your emails use.
- Enroll to send — When your product logic says "now", it enrolls the person in a sequence. Content Agents renders and delivers.
- Record the events — Delivery, open, click, bounce, and unsubscribe events arrive at your webhook, signed.
Ship lifecycle email without an email stack.
Design the emails once in your brand style. Let your product decide who gets them and when.
Frequently asked questions
How is this different from a transactional email service?
A transactional service gives you a pipe and leaves the design, templates, language handling, and unsubscribe rules to you. Here each email is a newsletter designed in your brand style inside Content Agents, with localized footers, right-to-left rendering, a brand-wide unsubscribe, and bounce and complaint suppression already handled. Your app only decides who and when.
How much work is the integration?
Three calls over the Content Agents MCP endpoint with your brand API key: add or update a person, enroll them in a sequence, and stop an enrollment. Optionally, point a webhook URL at your app to receive events.
What if my job retries and enrolls someone twice?
Nothing extra is sent. A person can only be enrolled once in a given sequence, so a retry returns the existing enrollment instead of a second email. That makes network errors safe to retry.
How do I measure whether the emails work?
Every delivered, open, click, bounce, and unsubscribe event is pushed to your webhook, signed with HMAC-SHA256, and tagged with the newsletter it belongs to. Record them in your database and send them on to your analytics tool alongside your product events.
Can I send in more than one language?
Yes. Each person carries a language. Hebrew and Arabic render right-to-left, and the footer is localized in English, Hebrew, and French. A family-memories app already sends its onboarding emails in English, Hebrew, and French this way.