How to Import Figma, HTML, and Inbox Emails in Brew
With Thomas, CTO · 3:35
Bring the emails you already have into Brew from Figma, from HTML or by forwarding them from your inbox.
Watch on YouTube (opens in a new tab)
Choose Brew if you want a fully agentic setup, where your AI agent drives lifecycle marketing to engage and retain customers. Brew designs every email from your brand and runs your automations agentically.
Choose Customer.io if your journeys need SMS, push or WhatsApp next to email or run on warehouse objects, and your team has time to design each email by hand.
Emails used to take me hours. Now they’re done in minutes.
THE BROWSERCOMPANY
Brew is fully agentic: your agent designs on-brand emails, sends them and runs your automations. In Customer.io, your team still builds each email by hand.
 Brew | Customer.io | |
|---|---|---|
| Key differences | ||
| Fully agentic | Brew: Yes. Your agent designs, sends and runs automations end to end | Customer.io: Partly. Partly: Assists by default; your team does the work in the app |
| Designs finished, on-brand emails | Brew: Yes. Layout, copy and images from your brand, ready to send | Customer.io: No. Suggests copy and brand colors; you design each email |
| Your agent takes it live | Brew: Yes. Sends, schedules and runs automations; OAuth and org-scoped MCP require confirmation, brand API keys do not | Customer.io: Partly. Partly: Drafts by default; sending needs an admin to allow live access |
| Remembers your brand for every email | Brew: Yes. Brand files your agent reads every time | Customer.io: Partly. Partly: Brand colors and type from your domain |
| Unlimited contacts | Brew: Yes. On every plan; you pay for sends | Customer.io: No. Priced per profile stored |
| Prices listed publicly | Brew: Yes. Growth $99/month, Pro $249/month | Customer.io: No. On request |
| Brew | Customer.io | |
|---|---|---|
| Creating emails | ||
| Visual editor | Brew: Yes. Infinite canvas, edit by hand or in chat | Customer.io: Yes. Design Studio, drag-and-drop and code editors |
| Bring the emails you already have | Brew: Yes. HTML, MJML, React Email, Figma or a forwarded email | Customer.io: Yes. HTML in the code editor |
| Automation and data | ||
| Event-triggered automations | Brew: Yes. Stripe, Shopify, Clerk, Supabase or your own events | Customer.io: Yes. Events or segment membership |
| Builds an automation from a description | Brew: Yes. Emails, waits and branches together | Customer.io: Yes. AI Agent configures the automation |
| Accounts and other objects | Brew: No. Contacts with custom fields | Customer.io: Yes. People and objects with relationships |
| Data pipelines and warehouse sync | Brew: No. API, SDK and integrations | Customer.io: Yes. Data pipelines built in |
| Best send time per contact | Brew: Yes. Intelligent Send | Customer.io: Yes. Send-time optimization |
| Channels | ||
| Email from your own domain | Brew: Yes. Marketing and transactional | Customer.io: Yes. Marketing and transactional |
| SMS, push and in-app | Brew: No. Email only | Customer.io: Yes. SMS from Standard; push and in-app included |
| WhatsApp and LINE | Brew: No. Email only | Customer.io: Yes. On Premium |
| Agents and developers | ||
| MCP server for AI agents | Brew: Yes. Every Brew tool, in Claude, ChatGPT, Cursor and Grok | Customer.io: Yes. Full API access; read-only by default |
| API and CLI | Brew: Yes. REST API, typed SDK and CLI | Customer.io: Yes. API, CLI and webhooks |
| Pricing | ||
| Billed on | Brew: Emails sent and AI credits | Customer.io: Profiles: people and objects |
| Getting started | Brew: Free trial with 500 AI credits and 1,000 sends | Customer.io: A year free for startups that raised under $10M |
| First paid plan | Brew: Growth, $99/month: 10,000 AI credits and 50,000 sends | Customer.io: Essentials, price on request: 1 million emails a month |
| Next plan | Brew: Pro, $249/month: 25,000 AI credits and 200,000 sends | Customer.io: Standard and Premium, price on request: adds SMS, WhatsApp and LINE |
| Enterprise | Brew: Custom volume and a dedicated account manager | Customer.io: Custom volume, dedicated infrastructure and HIPAA |
| Security and compliance | ||
| SOC 2 Type II and ISO 27001 | Brew: No. Not yet; security review and DPA on request | Customer.io: Yes. Certified |
| HIPAA | Brew: No. Not supported | Customer.io: Yes. Compliant |
Connect Claude, ChatGPT, Cursor or Grok over MCP and your agent gets every Brew tool. It designs emails from your brand, builds audiences, runs automations and schedules sends. OAuth and organization-scoped MCP connections ask you to confirm live sends and launches. Brand-scoped API keys can execute permitted calls without the MCP confirmation step.
Paste your website and Brew writes your brand into two files your agent reads for every email. Describe the email and it appears on the canvas, ready to edit by hand or in chat.
They had me at Lovable for email. 10/10 experience.
MiloRiff.aiHaving an AI assistant built into the platform has made creating emails so much faster, easier, and, honestly, a really enjoyable experience.
Alice MullinsMarketing Manager, RedSeedA great rethinking of everything about email. Love it so far.
Shan ZhongGrowth, NeticVery impressed with what y’all have built and can’t wait to use Brew.
Addie LevinskyOps & Strategy, The Browser CompanyI didn’t need to cold start it with context. I gave it a link and it gathered everything it needed to get me started. I liked its taste in design.
Nischal NaikCo-founder, ConstructKeep Customer.io sending until Brew passes your tests. We’ll do the move with you on a call if you like.
Export your contacts from Customer.io as a CSV, including their subscription status. Before importing, prepare a Subscribed column: true for opted-in contacts, false for unsubscribed, cleaned or suppressed contacts. Invert any Unsubscribed true/false flag first. Map the column to Subscribed and review the opt-out preview; new contacts default to subscribed if this value is missing.
Most teams have Brew redesign their emails from their brand, which is faster and looks better. You can also paste the HTML from Customer.io’s code editor or forward a sent email to hello@email.brew.new; imports are free.
Connect Stripe, Shopify, Clerk or Supabase, or send your own events over the API, then describe each flow. Brew builds the emails, waits and branches, usually simpler than the original.
Connect and verify your sending domain, then review its health and inbox placement. For a new domain, select Gradual send to ramp the campaign in configurable batches before a large send. Gradual send is off by default; connecting a domain does not automatically warm it up.
With Thomas, CTO · 3:35
Bring the emails you already have into Brew from Figma, from HTML or by forwarding them from your inbox.
Watch on YouTube (opens in a new tab)We're here to help! Feel free to schedule a call.
Can't find what you're looking for? Contact us at +1-(332)-203-2145 or support@brew.new.
Yes, if email is your main channel and you want an agent to run it. Brew designs finished, on-brand emails from your brand, sends them and runs your automations from your AI agent, and bills on sends instead of stored profiles. Brew is email only, so SMS and push stay in another tool.
Yes. You can design in Brew and keep Customer.io for SMS, push and in-app. Export the finished email as HTML and paste it into Customer.io’s code editor. A direct Customer.io integration is coming soon.
In Brew, your agent designs the finished email from your brand, builds audiences, runs automations and sends. Customer.io’s MCP is read-only by default and writes drafts; your team designs the email in Design Studio, and sending needs an admin to allow live access.
OAuth and organization-scoped MCP connections ask you to confirm live sends and launches. Brand-scoped API keys can execute permitted calls without the MCP confirmation step.
Customer.io’s AI does not design the email. It suggests copy and brand colors, and your team designs each email in Design Studio. Teams that move to Brew tell us these drafts rarely look like their brand, so someone still redesigns them. Brew designs the whole email, layout, copy and images, from brand files your agent reads every time, so it goes out on-brand.
It depends on your list and how much you send. Customer.io bills on stored profiles; Brew bills on sends and AI credits with unlimited contacts. Teams with a large user base they email in part usually pay less on Brew. Start with the free trial and compare at your own numbers.
No. Brew is email only: marketing and transactional email from your own domain. Teams that need SMS or push keep a separate tool for those, or keep Customer.io for them and design the emails in Brew.
Not yet. We complete security reviews and sign a DPA on request, and our privacy policy, DPA, GDPR page and subprocessor list are public at docs.brew.new/legal.
Your first on-brand email is ready the day you start the trial. The rest depends on how many flows you run: contacts and unsubscribes import from a CSV, most teams have Brew redesign their emails rather than import them, and each flow is rebuilt by describing it. Keep Customer.io sending until Brew passes your tests.
Before importing, prepare a Subscribed column: true for opted-in contacts, false for unsubscribed, cleaned or suppressed contacts. Invert any Unsubscribed true/false flag first. Map the column to Subscribed and review the opt-out preview; new contacts default to subscribed if this value is missing.
Yes. We get on a call to import your contacts and unsubscribe list, bring over or redesign your emails, rebuild your flows and connect your sending domain.
Brew publishes this comparison. Brew Team reviewed the linked first-party documentation. This is a documentation review, not a claim of hands-on testing of every product. Pricing and plan limits can change.
Work at Customer.io? If anything on this page is wrong or out of date, email support@brew.new and we will correct it. We want to compete on the product, not on a mistaken comparison.
Updated October 2026