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 Omnisend if you run an online store and want SMS, web push, popups and product recommendations in the same account as your email, and have someone to design each email.
THE BROWSERCOMPANY
Brew is fully agentic: your agent designs on-brand emails, sends them and runs your automations. In Omnisend, AI writes the copy and your team designs each email.
 Brew | Omnisend | |
|---|---|---|
| Key differences | ||
| Fully agentic | Brew: Yes. Your agent designs, sends and runs automations end to end | Omnisend: Partly. Partly: Its MCP sends and builds flows; in-app AI writes copy |
| Designs finished, on-brand emails | Brew: Yes. Layout, copy and images from your brand, ready to send | Omnisend: No. AI writes copy in text blocks; you design each email |
| Remembers your brand for every email | Brew: Yes. Brand files your agent reads every time | Omnisend: Partly. Partly: Logo, colors and fonts from your store, on templates |
| Unlimited contacts | Brew: Yes. On every plan; you pay for sends | Omnisend: No. Priced by contacts; unsubscribed ones not billed |
| Bring the emails you already have | Brew: Yes. HTML, MJML, React Email, Figma or a forwarded email | Omnisend: Partly. Partly: HTML only, with the head tags removed first |
| Brew | Omnisend | |
|---|---|---|
| Creating emails | ||
| Visual editor | Brew: Yes. Infinite canvas, edit by hand or in chat | Omnisend: Yes. Drag-and-drop builder with templates |
| A/B testing | Brew: No. Not built in | Omnisend: Yes. In campaigns and automation workflows |
| Product recommendations | Brew: No. Not built in | Omnisend: Yes. Product recommender blocks in emails |
| Automation and data | ||
| Event-triggered automations | Brew: Yes. Stripe, Shopify, Clerk, Supabase or your own events | Omnisend: Yes. Store events and custom events |
| Builds an automation from a description | Brew: Yes. Emails, waits and branches together | Omnisend: Yes. Through its MCP, from Claude or ChatGPT |
| Best send time per contact | Brew: Yes. Intelligent Send | Omnisend: Yes. Personalized sending time |
| Channels | ||
| Email from your own domain | Brew: Yes. Marketing and transactional | Omnisend: Yes. Campaigns plus order and shipping emails |
| SMS and web push | Brew: No. Email only | Omnisend: Yes. On every plan; SMS billed per message |
| Popups, forms and landing pages | Brew: No. Email only | Omnisend: Yes. Popups, signup forms and landing pages |
| 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 | Omnisend: Yes. Its MCP sends campaigns and enables workflows |
| MCP server for AI agents | Brew: Yes. Every Brew tool, in Claude, ChatGPT, Cursor and Grok | Omnisend: Yes. Remote server for Claude, ChatGPT and Cursor |
| API | Brew: Yes. REST API, typed SDK and CLI | Omnisend: Yes. REST API |
| Pricing | ||
| Billed on | Brew: Emails sent and AI credits | Omnisend: Subscribers, plus anyone sent an automated email |
| Getting started | Brew: Free trial with 500 AI credits and 1,000 sends | Omnisend: Free plan: 250 contacts, 500 emails a month |
| First paid plan | Brew: Growth, $99/month: 10,000 AI credits and 50,000 sends | Omnisend: Standard, $16/month for 500 contacts and 6,000 emails |
| Next plan | Brew: Pro, $249/month: 25,000 AI credits and 200,000 sends | Omnisend: Pro, $59/month for 2,500 contacts; unlimited emails |
| Top plan | Brew: Enterprise: custom volume and a dedicated account manager | Omnisend: Custom, price on request |
| Security and compliance | ||
| SOC 2 and ISO 27001 | Brew: No. Not yet; security review and DPA on request | Omnisend: No. Not listed on its site |
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 Omnisend sending until Brew passes your tests. We’ll do the move with you on a call if you like.
In Omnisend, go to Audience > Exports, click New Export, choose all contacts and download the CSV from the Exports tab. The file includes each contact’s email subscription status and opt-out date. Only the Owner, Admin and Analyst roles can export. 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 of an Omnisend email or forward a sent email to hello@email.brew.new; imports are free.
Connect Shopify, Stripe, Clerk or Supabase, or send your own events over the API, then describe each workflow. 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 design it as well as send it. 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. Brew is email only, so SMS, web push and popups stay in another tool.
Yes. You can design in Brew and keep Omnisend for SMS, web push and your store’s popups. Export the finished email as HTML and import it in Omnisend under Store settings, Saved templates, after removing the doctype and head tags as Omnisend asks. Brew does not export to Omnisend directly.
In Brew, your agent designs the finished email from brand files it reads every time, builds audiences, runs automations and sends. Omnisend’s MCP server lets Claude, ChatGPT or Cursor create, send and cancel campaigns, create and enable automation workflows and manage segments. Inside Omnisend, its AI writes and improves the copy in text blocks, suggests subject lines and builds segments and forms, and Brand Assets applies your store’s logo, colors and fonts to email templates; the layout of each email is still yours to build.
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. Omnisend’s AI writes copy in the builder’s text blocks, and Brand Assets, which needs a connected store, applies your logo, colors and fonts to its templates; you lay out each email yourself. 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. Omnisend bills on subscribed contacts plus anyone who received an automated message, not on unsubscribed ones, and Standard sends up to 12 times your list each month. Brew bills on sends and AI credits with unlimited contacts. 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, web push or popups keep a separate tool for those, or keep Omnisend for them and design their 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 workflows you run: contacts and their email status import from Omnisend’s CSV export, most teams have Brew redesign their emails rather than import them, and each workflow is rebuilt by describing it. Keep Omnisend 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 Omnisend? 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