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 Postmark if your developers send transactional email from your app, want inbound email parsed into JSON for your app, and will code each template themselves.
THE BROWSERCOMPANY
Brew is fully agentic: your agent designs on-brand emails, sends them and runs your automations. In Postmark, your app sends each email and your lists live elsewhere.
 Brew | Postmark | |
|---|---|---|
| Key differences | ||
| Fully agentic | Brew: Yes. Your agent designs, sends and runs automations end to end | Postmark: Partly. Partly: Your agent sends over MCP and writes each email itself |
| Designs finished, on-brand emails | Brew: Yes. Layout, copy and images from your brand, ready to send | Postmark: No. No AI design; you code each 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 | Postmark: Partly. Partly: Local MCP server sends emails; no flows to run |
| Remembers your brand for every email | Brew: Yes. Brand files your agent reads every time | Postmark: Partly. Partly: Shared layouts for CSS, headers and footers |
| Holds your contacts and audiences | Brew: Yes. Contacts, audiences and unsubscribes in one place | Postmark: No. Lists stay outside Postmark, in your app |
| Unlimited team seats | Brew: Yes. No seat limits on any plan | Postmark: Partly. Partly: 4 users on Basic, 6 on Pro, unlimited on Platform |
| Brew | Postmark | |
|---|---|---|
| Creating emails | ||
| Visual editor | Brew: Yes. Infinite canvas, edit by hand or in chat | Postmark: No. Code editor with a preview; no WYSIWYG editor |
| Bring the emails you already have | Brew: Yes. HTML, MJML, React Email, Figma or a forwarded email | Postmark: Yes. Template import tool and Templates API |
| Works without a developer | Brew: Yes. Connect your tools, design and automate in chat | Postmark: No. Every send goes through the API or SMTP |
| Automation and data | ||
| Event-triggered automations | Brew: Yes. Stripe, Shopify, Clerk, Supabase or your own events | Postmark: No. None built in; your app decides each send |
| Sending and receiving | ||
| Email from your own domain | Brew: Yes. Marketing and transactional | Postmark: Yes. Transactional and broadcast streams, kept apart |
| Inbound email | Brew: No. No inbound email | Postmark: Yes. Parsed to JSON for your webhook, Pro and up |
| Agents and developers | ||
| MCP server for AI agents | Brew: Yes. Every Brew tool, in Claude, ChatGPT, Cursor and Grok | Postmark: Yes. Local server: sends, templates, bounces and stats |
| API | Brew: Yes. REST API, typed SDK and CLI | Postmark: Yes. REST API, SMTP and official SDKs |
| Pricing | ||
| Billed on | Brew: Emails sent and AI credits | Postmark: Emails sent and received a month |
| Getting started | Brew: Free trial with 500 AI credits and 1,000 sends | Postmark: Free Developer plan: 100 emails a month |
| First paid plan | Brew: Growth, $99/month: 10,000 AI credits and 50,000 sends | Postmark: Basic, $15/month: 10,000 emails |
| Next plan | Brew: Pro, $249/month: 25,000 AI credits and 200,000 sends | Postmark: Pro, $16.50/month: 10,000 emails and inbound |
| Top plan | Brew: Enterprise: custom volume and a dedicated account manager | Postmark: Platform, from $18/month; sales for high volume |
| Security and compliance | ||
| SOC 2 | Brew: No. Not yet; security review and DPA on request | Postmark: No. No SOC audit of its own; its data center has one |
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 Postmark sending until Brew passes your tests. We’ll do the move with you on a call if you like.
Postmark keeps no contact lists, so export your contacts as a CSV from the app or tool that holds them. In Postmark, open each stream’s Suppressions tab and click Export to download suppressed recipients as JSON, then mark those contacts as unsubscribed. 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 Postmark template or forward a sent email to hello@email.brew.new; imports are free.
With Postmark, the logic for who gets which email lives in your code. Connect Stripe, Shopify, Clerk or Supabase, or send the same events to Brew’s API, then describe each flow. Brew builds the emails, waits and branches.
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, and holds your contacts, audiences and unsubscribes. Brew has no inbound email, so replies your app parses stay with another tool.
Yes. Connect Postmark in Brew with a Server API token, and Brew saves any email straight into Postmark as a template, ready for your transactional and broadcast streams. Many teams design in Brew and keep Postmark sending from their app.
Brew’s agent designs the finished email from your brand files, builds audiences, runs automations and sends, so what goes out is on-brand without anyone writing HTML. Postmark’s MCP server runs locally and gives your agent Postmark’s API: it sends single and batch emails, creates and edits templates, and reads bounces and delivery stats, and your agent writes each email itself.
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. Postmark has no AI that designs emails: templates are edited as code, with shared layouts for CSS, headers and footers, or your agent writes the HTML and sends it through the MCP server. 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 what you send. Postmark bills on emails sent and received a month: paid plans start at 10,000 emails, at $15/month on Basic, $16.50 on Pro and $18 on Platform, with overage per 1,000 emails. Postmark holds no contact lists or automations, so those run in your app or another tool. Brew bills on sends and AI credits with unlimited contacts, and covers design, campaigns and automations in one plan. Start with the free trial and compare at your own numbers.
Yes. Brew holds your contacts, audiences and unsubscribes, and sends campaigns and automations from your own domain. With Postmark, your lists stay in your app or another tool, and each broadcast goes out through the API or SMTP.
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 much of your email your app sends: contacts come from the tool that holds them and opt-outs from Postmark’s suppression exports, most teams have Brew redesign their emails rather than import them, and each flow is rebuilt by describing it. Keep Postmark 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 Postmark? 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