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 Resend if your developers send email from code, want a transactional API, SMTP relay and React Email in one place, and will code each email.
THE BROWSERCOMPANY
Brew is fully agentic: your agent designs on-brand emails, sends them and runs your automations. In Resend, your agent sends HTML it has to write itself.
 Brew | Resend | |
|---|---|---|
| Key differences | ||
| Fully agentic | Brew: Yes. Your agent designs, sends and runs automations end to end | Resend: Partly. Partly: Your agent sends and builds flows; it writes the HTML itself |
| Designs finished, on-brand emails | Brew: Yes. Layout, copy and images from your brand, ready to send | Resend: Partly. Partly: Editor AI drafts emails; 100 AI credits a month on Pro |
| Remembers your brand for every email | Brew: Yes. Brand files your agent reads every time | Resend: Partly. Partly: Global email theme; AI can reuse past emails as reference |
| Unlimited contacts | Brew: Yes. On every plan; you pay for sends | Resend: No. Marketing priced by contacts, 5,000 for $40/month |
| Marketing and transactional on one plan | Brew: Yes. One plan, billed on sends | Resend: No. Separate transactional and marketing plans |
| Brew | Resend | |
|---|---|---|
| Creating emails | ||
| Visual editor | Brew: Yes. Infinite canvas, edit by hand or in chat | Resend: Yes. No-code editor for broadcasts and templates |
| Bring the emails you already have | Brew: Yes. HTML, MJML, React Email, Figma or a forwarded email | Resend: Yes. HTML through the API or code view; React Email |
| Works without a developer | Brew: Yes. Connect your tools, design and automate in chat | Resend: Partly. Partly: Broadcasts in the dashboard; events and API sends need code |
| Automation and data | ||
| Event-triggered automations | Brew: Yes. Stripe, Shopify, Clerk, Supabase or your own events | Resend: Yes. Custom events from your app and contact changes |
| Triggers without code | Brew: Yes. Connect Stripe, Shopify, Clerk or Supabase | Resend: Partly. Partly: Your app sends each event over the API |
| Builds an automation from a description | Brew: Yes. Emails, waits and branches together | Resend: Yes. AI generates automations in the dashboard |
| Channels | ||
| Email from your own domain | Brew: Yes. Marketing and transactional | Resend: Yes. Transactional API and marketing Broadcasts |
| 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 | Resend: Yes. MCP server sends emails and broadcasts |
| MCP server for AI agents | Brew: Yes. Every Brew tool, in Claude, ChatGPT, Cursor and Grok | Resend: Yes. Emails, broadcasts, contacts and automations |
| API and CLI | Brew: Yes. REST API, typed SDK and CLI | Resend: Yes. REST API, SMTP relay, official SDKs and a CLI |
| Pricing | ||
| Billed on | Brew: Emails sent and AI credits | Resend: Emails for transactional; contacts for marketing |
| Getting started | Brew: Free trial with 500 AI credits and 1,000 sends | Resend: Free plan: 3,000 emails a month, 100 a day, 1,000 contacts |
| First paid plan | Brew: Growth, $99/month: 10,000 AI credits and 50,000 sends | Resend: Pro, $20/month: 50,000 transactional emails |
| Next plan | Brew: Pro, $249/month: 25,000 AI credits and 200,000 sends | Resend: Pro marketing, from $40/month for 5,000 contacts |
| Enterprise | Brew: Custom volume and a dedicated account manager | Resend: Custom volume, SSO and a dedicated CSM |
| Security and compliance | ||
| SOC 2 Type II | Brew: No. Not yet; security review and DPA on request | Resend: Yes. Certified |
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 Resend sending until Brew passes your tests. We’ll do the move with you on a call if you like.
In Resend, open Contacts and click Export to download them as a CSV. Include subscription status before importing into Brew. 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 your React Email templates, paste the HTML or forward a sent email to hello@email.brew.new; imports are free.
Connect Stripe, Shopify, Clerk or Supabase, or point the events your app already sends at 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 design and run your marketing and lifecycle email, not only send it. Brew designs finished, on-brand emails from your brand, sends them and runs your automations from your AI agent, with marketing and transactional email on one plan and unlimited contacts. Developers can still work in code with Brew’s REST API, typed SDK and CLI.
Yes. You can keep Resend for the transactional email your code sends and run marketing and lifecycle email in Brew. You can also export any finished Brew email as HTML and send it through Resend’s API.
Brew’s agent designs the finished email from your brand files, so what goes out is on-brand without anyone writing HTML, and you approve it before it sends. Resend’s MCP server gives your agent Resend’s API: it sends the emails and broadcasts your agent writes as HTML itself. Resend’s own AI drafts emails in its editor on monthly AI credits.
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. Resend’s editor AI drafts emails on monthly AI credits, styled by a global theme you set, and through its MCP server your agent sends HTML it writes itself. 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 what you send. Resend prices transactional email by emails a month and marketing by stored contacts, on separate plans: Pro is $20/month for 50,000 transactional emails, and marketing starts at $40/month for 5,000 contacts. Brew bills on sends and AI credits with unlimited contacts on one plan, and its price covers the agent. Start with the free trial and compare at your own numbers.
No. Connect Stripe, Shopify, Clerk or Supabase, design emails on the canvas or in chat, and describe each automation. Developers can still send events over the REST API, typed SDK or CLI, and import React Email templates.
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 Resend’s CSV export, most teams have Brew redesign their emails rather than import them, and each flow is rebuilt by describing it. Keep Resend 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 Resend? 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