Create on-brand emails in Brew, export them to Klaviyo as CODE templates, and send from your existing campaigns and flows. Steps, checks and limits.
The campaign brief goes out on Monday, and by Wednesday the draft in Klaviyo still looks like the default template with your logo on top. Someone adjusts the button color, swaps in the closest font on offer, and sends it anyway because the segment is ready.
Your profiles, flows and revenue reporting are in Klaviyo. Moving all of that to change how emails get designed is rarely worth it. The simpler setup is to design in Brew, export to Klaviyo, and keep sending where you already send.
This guide covers that path end to end. Brew creates the email and exports it as a template, and Klaviyo sends it. Brew sends nothing in this setup.
You need:
You do not need a verified sending domain in Brew, because Klaviyo sends.
Add your brand with your website domain. Brew's extraction agent reads the site and writes an email-design.md, a brand document covering colors, email-safe fonts, layout habits, signature moves and voice. Upload anything that describes your brand better than the website does: a PDF brand guide, logos, product shots, past emails. When your uploads and the site disagree, Brew follows your uploads.
Open the generated document and read it. If the voice is off, change the sentence. Brew uses the edited document for every email after that.
Describe the email in chat the way you would brief a designer. For example:
Audience: customers who bought in the last 90 days, not subscribed to the loyalty program.
Job: get them to join the loyalty program this week.
Offer: points on every order, double points in the first 30 days.
Proof: only use the terms on example.com/loyalty. No statistics, no customer quotes.
Constraints: under 150 words, one CTA to example.com/loyalty, promotional footer.Brew generates the email on the canvas. Ask for two or three directions if you are unsure of the angle. How to brief an email agent explains why the proof line matters.
Select the email you want and refine it. Edit with a prompt ("shorten the intro to two sentences"), or click into text, links, buttons and images to change them by hand. Preview at mobile and desktop widths.
Before export, check that every link points to a real URL, that images have alt text, and that the footer has your physical address. Review the preview here. After export, send a test from Klaviyo to the clients your audience uses, including Outlook and mobile inboxes (step 6).
In Brew, open Integrations and connect Klaviyo. The connection uses one-click OAuth, according to the Klaviyo export docs. You sign in to Klaviyo and approve access. You only do this once per brand.
Open the email and choose Send, then Export template. Select Klaviyo, name the template and export. Klaviyo templates carry no subject, so set the subject on the Klaviyo campaign.
Brew then does four things:
If you work through an agent or code, the same export is available as export_email over MCP or as POST /v1/emails/{emailId}/export with "provider": "klaviyo" in the API. Add "dryRun": true to check the connection without creating a template.
In Klaviyo, open your template library and find the template by name. Use it in a campaign or as a message in a flow. Set the final subject line, choose the list or segment, and send or schedule as you normally do. Klaviyo handles delivery, and opens, clicks and revenue reporting stay in Klaviyo.
Send a test to yourself first. Check the unsubscribe link, and check any personalization you added in Klaviyo against a real profile.
An export is a copy. If you change the email in Brew, export it again and switch your campaign or flow to the new template.
For recurring work, such as a weekly product update or a seasonal campaign, set your best email as the reference design in Brew. New generations then follow its structure.
If you later want triggered emails sent from Brew itself, Brew has its own automations and integrations. That is a separate setup with a verified sending domain.
You can. Klaviyo's Composer drafts campaigns from your account's brand settings and history. Add Brew if you want designs built from a detailed brand document, a canvas for comparing directions, or one design system across several ESPs or brands.
Yes, as a CODE template, which means editing the HTML. For layout changes, it is usually faster to edit in Brew and export again.
No. Export is free. Generating and editing emails in Brew uses AI credits from your plan.
Yes. The CODE template works in both campaigns and flows.
To try it with one campaign, connect Klaviyo in Brew, export your next email, and send yourself a test from Klaviyo before scheduling it.
