barua is a headless email service your AI agent can run end to end through the API. It supports automated customer journeys and campaigns to saved segments. barua writes emails in your brand's voice, from your domain. You choose the agent's permissions and what needs your approval.
A play is a rule with one or more emails attached. The rule describes the situation that calls for a message, including when the message should stop being useful.
What does barua do?
barua handles email tied to what happens in your product. That includes a welcome after registration, a reminder about an unfinished setup step, a return invitation after inactivity and supported order updates.
For a newsletter or announcement, your agent can select a saved segment and give barua a campaign brief. Barua prepares the email and fixes its audience for review. Sending requires the exact prepared version and the approval policy you chose. Read the campaign workflow for the details.
Consider a website builder. A user creates a site but leaves before connecting a domain. The server records the site being created. A play can wait for the activation step and send a reminder if the user still hasn't completed it.
The useful email names the unfinished task and links to the place where the user can finish. The product needs to report completion too, so the rule can recognize that the reminder is no longer relevant. The automated email examples show this kind of play.
Where does AI fit?
barua uses AI to write the messages for a play in your brand's voice. Those words are prepared for review. Once a play is approved, code applies its rules to determine who qualifies and when sending is allowed.
The email can include supported facts from the event, such as the title of a project or details of an order. That is different from asking a model to invent a new message for every recipient. Each send records the event and rule revision behind it.
If the words or rule change, the revised play needs approval. You can keep that decision yourself or delegate it through an agent connection with the appropriate permissions.
What does the coding agent handle?
Your agent reads the project and finds where the server records the facts barua needs. It proposes an event plan and adds the integration, then checks the events through the product's own code. With the right access, it can also confirm the brand, approve plays, verify the sending domain and enable sending.
You decide which steps it may carry out and which need your review. Accepting the terms stays with the owner. The permission to email people must come from facts you supply or a statement you authorize.
To evaluate fit first, read the features and pricing. When you are ready to set it up, the starting prompt is:
Fetch and follow the instructions at https://barua.ai/setup.md to set up barua for this project.
The installation guide covers Claude Code and Codex, along with other agents that can read the setup skill.
The onboarding setup walkthrough shows the sequence and the checks to run.
Do you need the pixel?
You can run barua's plays without the pixel. Plays use events your server sends after a fact becomes true, such as a completed purchase.
The pixel adds website activity to customer profiles and can provide a visitor's time zone. With pixel Plays enabled, supported website observations can also trigger approved marketing journeys for identified people who meet the marketing permission rules.
Browser properties help decide who qualifies and when. They do not supply facts to quote in an email or establish consent. Confirmed purchases and consent changes still come from your server. The customer data guide explains how the sources fit together.
For the supported events and their required data, use the maintained event contract.
What controls sending?
An approved play still has to meet its sending conditions. Marketing email checks the recorded permission state, and an explicit refusal takes precedence. Sending windows and frequency limits also apply.
New workspaces start with sending off. Approving a message does not turn sending on. The setup process handles those as separate steps and verifies the result with a fresh event after launch.
Supported receipts and order updates have different handling from marketing messages. Their documented timing is within hours, so keep urgent authentication email, such as password resets, on a service designed for that job.
When is barua a good fit?
Consider barua when you want product events to lead to useful email and you want your coding agent to handle the setup. You still choose what the product's important moments mean, and you control the permissions and approvals.
If you want a visual newsletter editor or a sales CRM, compare tools built around that work. Barua's campaign workflow is operated through your agent and the API. The marketing automation guide explains the different jobs.
barua is in early access. You can request access on the homepage and read the product guides before deciding whether it fits.