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 beehiiv if you publish a newsletter and want a website, an ad network and paid subscriptions to earn from it, all in the same account.
Brew is fully agentic: your agent designs on-brand emails, sends them and runs your automations. In beehiiv, AI writes inside your template and you switch on each automation.
| beehiiv | ||
|---|---|---|
| Key differences | ||
| Fully agentic | Brew: Yes. Your agent designs, sends and runs automations end to end | beehiiv: Partly. Partly: Drafts and builds; you switch on automations in the app |
| Designs finished, on-brand emails | Brew: Yes. Layout, copy and images from your brand, ready to send | beehiiv: Partly. Partly: AI writes copy and images inside your template |
| Your agent takes it live | Brew: Yes. Sends, schedules and runs automations; OAuth and org-scoped MCP require confirmation, brand API keys do not | beehiiv: Partly. Partly: Agent sends posts on Pro; the MCP cannot send |
| Remembers your brand for every email | Brew: Yes. Brand files your agent reads every time | beehiiv: Partly. Partly: Template styles, logo and colors you set up by hand |
| Unlimited contacts | Brew: Yes. On every plan; you pay for sends | beehiiv: No. Priced by subscribers |
| Unlimited team seats | Brew: Yes. No seat limits on any plan | beehiiv: Partly. Partly: 1 on Free, 2 on Lite, 10 on Pro |
| beehiiv | ||
|---|---|---|
| Creating emails | ||
| Visual editor | Brew: Yes. Infinite canvas, edit by hand or in chat | beehiiv: Yes. Post editor with templates and custom CSS |
| AI translation | Brew: No. Not built in | beehiiv: Yes. AI Translator in the editor |
| A/B testing | Brew: No. Not built in | beehiiv: Yes. A/B tests from Lite |
| Automation and data | ||
| Event-triggered automations | Brew: Yes. Stripe, Shopify, Clerk, Supabase or your own events | beehiiv: Yes. Signups, purchases and custom events; clicks on Pro |
| Automations on every plan | Brew: Yes. No step or flow limits on any plan | beehiiv: Partly. Partly: From Lite; Free sends a welcome email only |
| Builds an automation from a description | Brew: Yes. Emails, waits and branches together | beehiiv: Partly. Partly: MCP builds workflows; you activate them in the app |
| Publishing and earning | ||
| Email from your own domain | Brew: Yes. Marketing and transactional | beehiiv: Yes. Newsletters and automations, custom domains |
| Website builder | Brew: No. Email only | beehiiv: Yes. On every plan |
| Ad network | Brew: No. Not built in | beehiiv: Yes. beehiiv Ad Network from Lite |
| Paid subscriptions | Brew: No. Not built in | beehiiv: Yes. From Lite, with a 0% take rate |
| Podcasts and community | Brew: No. Email only | beehiiv: Yes. On every plan |
| Agents and developers | ||
| MCP server for AI agents | Brew: Yes. Every Brew tool, in Claude, ChatGPT, Cursor and Grok | beehiiv: Partly. Partly: Read-only on Free; drafts and builds on paid plans |
| API | Brew: Yes. REST API, typed SDK and CLI | beehiiv: Yes. API and webhooks; Send API on Pro |
| Pricing | ||
| Billed on | Brew: Emails sent and AI credits | beehiiv: Subscribers; unlimited sends on every plan |
| Getting started | Brew: Free trial with 500 AI credits and 1,000 sends | beehiiv: Free plan up to 2,500 subscribers, no automations |
| First paid plan | Brew: Growth, $99/month: 10,000 AI credits and 50,000 sends | beehiiv: Lite, $59/month for 1,000 subscribers; $49 billed yearly |
| Next plan | Brew: Pro, $249/month: 25,000 AI credits and 200,000 sends | beehiiv: Pro, $109/month for 1,000 subscribers; $95 billed yearly |
| Top plan | Brew: Enterprise: custom volume and a dedicated account manager | beehiiv: Enterprise, custom pricing |
| Security and compliance | ||
| SOC 2 | Brew: No. Not yet; security review and DPA on request | beehiiv: Yes. SOC 2 Type 2 since January 2026 |
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 beehiiv sending until Brew passes your tests. We’ll do the move with you on a call if you like.
In beehiiv, go to Settings, then Export Data, and choose Export All Subscribers. beehiiv emails you a link when the CSV is ready, with each subscriber’s status, tier and custom fields; the link lasts 24 hours. 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 forward a sent beehiiv post 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 automation. 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 your email is lifecycle and marketing email 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, with unlimited contacts and seats on every plan. Brew is email only, with no website, ad network or paid subscriptions, so a newsletter business that earns from those keeps them in another tool.
Yes. Keep your newsletter, website and paid subscriptions in beehiiv, and send your lifecycle and transactional email from Brew on your own domain. Brew does not export to beehiiv directly.
In Brew, your agent designs the finished email from your brand, builds audiences, runs automations and sends. The beehiiv MCP lets Claude, Cursor and other clients draft posts and build automation workflows on paid plans, but it cannot send, and you activate each automation in the beehiiv app. beehiiv Agent, inside the app, also schedules and sends posts on Pro and Enterprise. On Free, both are read-only.
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.
Not as finished designs. beehiiv’s AI writes copy and makes images inside your existing template, which carries the fonts, colors and logo you set up, and you lay out each post. 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. beehiiv bills on subscribers, counted as unique email addresses, with unlimited sends on every plan; automations start on Lite. Brew bills on sends and AI credits with unlimited contacts and seats. Start with the free trial and compare at your own numbers.
No. Brew is email only: marketing and transactional email from your own domain. Publishers who earn from ads, paid subscriptions or a website keep those in beehiiv or another tool.
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 automations you run: contacts and their status import from beehiiv’s CSV export, most teams have Brew redesign their emails rather than import them, and each automation is rebuilt by describing it. Keep beehiiv 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 beehiiv? 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