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 Loops if your developers write each email themselves and you want A/B experiments inside your workflows.
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 Loops, your team builds each email in the editor or in code.
 Brew | Loops | |
|---|---|---|
| Key differences | ||
| Fully agentic | Brew: Yes. Your agent designs, sends and runs automations end to end | Loops: Partly. Partly: Agents can run it, but write each email in LMX code |
| Designs finished, on-brand emails | Brew: Yes. Layout, copy and images from your brand, ready to send | Loops: No. You build in the editor, or an agent writes LMX |
| Remembers your brand for every email | Brew: Yes. Brand files your agent reads every time | Loops: Partly. Partly: Themes built from the style panel or the API |
| Unlimited contacts | Brew: Yes. On every plan; you pay for sends | Loops: No. Priced by subscribed contacts |
| Builds an automation from a description | Brew: Yes. Emails, waits and branches together | Loops: Partly. Partly: Coding agents can create workflows over the API |
| Brew | Loops | |
|---|---|---|
| Creating emails | ||
| Visual editor | Brew: Yes. Infinite canvas, edit by hand or in chat | Loops: Yes. Editor with themes, components and Markdown |
| Bring the emails you already have | Brew: Yes. HTML, MJML, React Email, Figma or a forwarded email | Loops: Partly. Partly: MJML uploaded as a ZIP |
| Automation and data | ||
| Event-triggered automations | Brew: Yes. Stripe, Shopify, Clerk, Supabase or your own events | Loops: Yes. Events, contact changes and list signups |
| A/B tests in automations | Brew: No. Not built in | Loops: Yes. Experiment nodes split workflow traffic |
| Channels | ||
| Email from your own domain | Brew: Yes. Marketing and transactional | Loops: Yes. Marketing and transactional |
| Signup forms | Brew: No. No forms builder | Loops: Yes. Generated HTML or JSX forms and an endpoint |
| Agents and developers | ||
| Your agent takes it live | Brew: Yes. Sends, schedules and runs automations; OAuth and org-scoped MCP require confirmation, brand API keys do not | Loops: Yes. Agents can schedule and send campaigns over the API |
| MCP server for AI agents | Brew: Yes. Every Brew tool, in Claude, ChatGPT, Cursor and Grok | Loops: Yes. In Claude, ChatGPT, Codex and other clients |
| API and CLI | Brew: Yes. REST API, typed SDK and CLI | Loops: Yes. REST API, SDKs, CLI and agent skills |
| Pricing | ||
| Billed on | Brew: Emails sent and AI credits | Loops: Subscribed contacts; unsubscribed ones are free |
| Getting started | Brew: Free trial with 500 AI credits and 1,000 sends | Loops: Free: 1,000 subscribed contacts, 4,000 sends per 30 days |
| First paid plan | Brew: Growth, $99/month: 10,000 AI credits and 50,000 sends | Loops: $49/month for 5,000 subscribed contacts, unlimited sends |
| Next plan | Brew: Pro, $249/month: 25,000 AI credits and 200,000 sends | Loops: $99/month for 10,000 subscribed contacts |
| Enterprise | Brew: Custom volume and a dedicated account manager | Loops: Contact sales above 1.5 million contacts |
| Security and compliance | ||
| SOC 2 | Brew: No. Not yet; security review and DPA on request | Loops: Yes. SOC 2 audit complete |
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 Loops sending until Brew passes your tests. We’ll do the move with you on a call if you like.
Download your audience from Loops as a CSV from the menu on its filter box. It has a column for every contact property, default and custom. LiveFlow brought its Loops contacts across this way. 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 import the MJML files you uploaded to Loops or forward a sent email to hello@email.brew.new; imports are free.
Connect Stripe, Clerk or Supabase, or send the events you already send Loops to Brew’s 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 you want an agent to make and run your email instead of building each one yourself. Brew designs finished, on-brand emails from your brand, sends them and runs your automations from your AI agent, with unlimited contacts on every plan. At LiveFlow, one sequence took Josh about three hours across Figma, ChatGPT and Loops; in Brew, his emails take minutes.
Yes. LiveFlow kept its authentication emails in Loops and sends everything a customer reads from Brew. Brew has no Loops export, so each tool sends its own emails.
Loops gives coding agents an MCP server, CLI and skills: an agent writes the email in LMX, Loops’ markup, creates and sends campaigns and workflows, and sends transactional email. In Brew, your agent designs the finished email from brand files it reads every time, builds audiences, runs automations and 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.
No. Loops has no AI that designs emails: you build each one in its editor, or a coding agent writes it in LMX, Loops’ markup. That is the work Brew’s agent takes over. 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 often you email it. Loops bills on subscribed contacts with no send cap on paid plans: $49/month up to 5,000 contacts and $99/month up to 10,000. Brew bills on sends and AI credits with unlimited contacts. Teams with a large list they email a few times a month usually pay less on Brew. Start with the free trial and compare at your own numbers.
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 workflows you run: contacts import from Loops’ CSV download, most teams have Brew redesign their emails rather than import them, and each flow is rebuilt by describing it. Keep Loops 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 Loops? 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