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 Salesforce Marketing Cloud if your marketing runs on Salesforce CRM across email, SMS, WhatsApp and push, and you have admins to build and activate each journey.
THE BROWSERCOMPANY
Brew is fully agentic: your agent designs on-brand emails, sends them and runs your automations. In Marketing Cloud, Agentforce drafts; your team saves and activates.
 Brew | Salesforce Marketing Cloud | |
|---|---|---|
| Key differences | ||
| Fully agentic | Brew: Yes. Your agent designs, sends and runs automations end to end | Salesforce Marketing Cloud: Partly. Partly: Agentforce drafts campaigns; your team saves and activates |
| Designs finished, on-brand emails | Brew: Yes. Layout, copy and images from your brand, ready to send | Salesforce Marketing Cloud: Partly. Partly: Agentforce drafts text and sections; you lay out the 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 | Salesforce Marketing Cloud: Partly. Partly: Engagement’s MCP publishes journeys within granted scopes |
| Remembers your brand for every email | Brew: Yes. Brand files your agent reads every time | Salesforce Marketing Cloud: Partly. Partly: Brand kits set styles and tone for agent-written text |
| Unlimited contacts | Brew: Yes. On every plan; you pay for sends | Salesforce Marketing Cloud: No. Engagement editions cap contacts, from 15K |
| Start in a day, self-serve | Brew: Yes. Free trial, then Growth at $99/month | Salesforce Marketing Cloud: No. Annual contracts from $1,500 per org a month |
| Brew | Salesforce Marketing Cloud | |
|---|---|---|
| Creating emails | ||
| Visual editor | Brew: Yes. Infinite canvas, edit by hand or in chat | Salesforce Marketing Cloud: Yes. Drag-and-drop editors in Next and Content Builder |
| Bring the emails you already have | Brew: Yes. HTML, MJML, React Email, Figma or a forwarded email | Salesforce Marketing Cloud: Yes. Paste custom HTML into Content Builder |
| A/B testing | Brew: No. Not built in | Salesforce Marketing Cloud: Yes. Email Studio A/B tests; path experiments |
| Automation and data | ||
| Event-triggered automations | Brew: Yes. Stripe, Shopify, Clerk, Supabase or your own events | Salesforce Marketing Cloud: Yes. Journeys start on API events or data extensions |
| Builds an automation from a description | Brew: Yes. Emails, waits and branches together | Salesforce Marketing Cloud: Yes. Agentforce drafts the campaign flow |
| Best send time per contact | Brew: Yes. Intelligent Send | Salesforce Marketing Cloud: Yes. Einstein Send Time Optimization |
| Product recommendations | Brew: No. Not built in | Salesforce Marketing Cloud: Yes. Salesforce Personalization add-on |
| Channels | ||
| Email from your own domain | Brew: Yes. Marketing and transactional | Salesforce Marketing Cloud: Yes. Promotional and transactional |
| SMS and push | Brew: No. Email only | Salesforce Marketing Cloud: Yes. SMS and push in Engagement |
| Two-way SMS and WhatsApp | Brew: No. Email only | Salesforce Marketing Cloud: Yes. Marketing Cloud Next Advanced |
| Forms and landing pages | Brew: No. Email only | Salesforce Marketing Cloud: Yes. Marketing Cloud Next Growth and up |
| Agents and developers | ||
| MCP server for AI agents | Brew: Yes. Every Brew tool, in Claude, ChatGPT, Cursor and Grok | Salesforce Marketing Cloud: Yes. Hosted server for Engagement, in Claude Code and others |
| API | Brew: Yes. REST API, typed SDK and CLI | Salesforce Marketing Cloud: Yes. Marketing Cloud Engagement APIs |
| Pricing | ||
| Billed on | Brew: Emails sent and AI credits | Salesforce Marketing Cloud: Per org per month, billed annually |
| Getting started | Brew: Free trial with 500 AI credits and 1,000 sends | Salesforce Marketing Cloud: Through sales; no trial listed for these editions |
| First paid plan | Brew: Growth, $99/month: 10,000 AI credits and 50,000 sends | Salesforce Marketing Cloud: Next Growth, $1,500/org/month, billed annually |
| Next plan | Brew: Pro, $249/month: 25,000 AI credits and 200,000 sends | Salesforce Marketing Cloud: Next Advanced, $3,250/org/month, billed annually |
| Contacts and emails included | Brew: Unlimited contacts; sends by plan | Salesforce Marketing Cloud: Engagement Pro+, $2,000/org/month: 15K contacts, 2.5M emails |
| Top plan | Brew: Enterprise: custom volume and a dedicated account manager | Salesforce Marketing Cloud: Engagement Enterprise+, $30,000/org/month: 500K contacts |
| Security and compliance | ||
| SOC 2 and ISO 27001 | Brew: No. Not yet; security review and DPA on request | Salesforce Marketing Cloud: 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 Marketing Cloud sending until Brew passes your tests. We’ll do the move with you on a call if you like.
In Marketing Cloud Engagement, open Subscribers > Data Extensions and choose Export for each data extension you want, as a CSV with column headers; files over 20MB go to your Enhanced FTP. Export unsubscribed subscribers from All Subscribers by status, which needs the account admin role or list access. 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 a Content Builder email 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 journey. 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, with unlimited contacts on every plan. Brew is email only and is not a CRM, so SMS, WhatsApp, push, landing pages and your Salesforce records stay where they are.
Yes. Design in Brew, export the finished email as HTML and paste it into a Content Builder HTML email, and keep your CRM data, journeys, SMS and push in Salesforce. Many teams design in Brew first and move their email sending over later.
In Brew, your agent designs the finished email from brand files it reads every time, builds audiences, runs automations and sends. In Marketing Cloud Next, Agentforce drafts a campaign brief, a flow and the message text from your prompt, and your team saves the campaign and activates it once its emails are published. Marketing Cloud Engagement has a separate hosted MCP server: clients such as Claude Code can create HTML emails, build and publish journeys and send transactional email, within the permission scopes of an installed package your admin sets up.
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.
Partly. In Marketing Cloud Next, Agentforce drafts text and email sections grounded in your campaign brief and the assigned brand kit, which sets colors, fonts, tone and guardrails, and your team arranges the components and publishes the email. Through the Engagement MCP server, the AI client writes the HTML 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 your volume and the editions you need. Marketing Cloud Next lists Growth at $1,500 and Advanced at $3,250 per org per month, billed annually; Engagement editions start at $2,000 per org per month with 15,000 contacts and 2.5 million emails. 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, WhatsApp or push keep Marketing Cloud for those 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 journeys you run: contacts import from your data extension exports, unsubscribes from an All Subscribers export, most teams have Brew redesign their emails rather than import them, and each journey is rebuilt by describing it. Keep Marketing Cloud 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 Salesforce Marketing Cloud? 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