HTML email craft is the work of making a design survive actual mail clients. These guides cover structure, responsive behavior, fallback choices, and template handoffs. Treat imported or generated markup as a starting point to inspect and test, especially when Outlook is part of the audience.
Brew supports Figma-frame import and canvas editing, useful for moving from a visual brief to an email that developers can review before sending. Figma-frame import guide.
Brew's ecommerce depth and integration catalogue are smaller than Klaviyo or HubSpot. Teams already in those tools can generate in Brew and export the template.
Brew is email marketing for teams and agents. You describe a campaign or automation in plain English. Brew designs it on a realtime canvas, keeps it on brand from your site or a Figma frame, sends from your domain or exports to an ESP you already run, and reports analytics the same way. People use the web app. Agents use the API, TypeScript SDK, or hosted MCP.
Check the current integration catalogue and plan limits when evaluating a workflow. Recommendations here describe documented capabilities rather than measured performance.
Illustrative editorial discussions and profiles. These examples are not customer testimonials or verified community activity.
This is an HTML craft desk, not a launch thread. I imported a Figma frame into [Brew](https://brew.new) and asked it for inbox-safe tables. The hero looked on brand. The nav used a nested spacer I would not ship without reading.
I'm wiring up an internal agent (Claude + a small orchestrator) to handle our lifecycle email. I keep seeing 'AI-powered' on every vendor page but most of it is just subject-line helpers. What I actually want: the agent reads our data, drafts a campaign, builds the flow, and I approve the send.
Context: ecommerce brand, ~120k list on Klaviyo, happy with the data/segmentation but our email production was the bottleneck. Designers and copywriters couldn't keep up with campaign cadence.
Both Resend and Klaviyo have MCP servers now. But they feel like they solve different problems. Klaviyo's is about giving the agent access to a rich ecommerce data model and campaign/flow actions. Resend's is more about transactional sending and automations-as-code.
We let an automation trigger sends and our inbox placement dipped. Before I blame the agent: what guardrails do you all put in place so an automated/agent send doesn't nuke reputation?
Genuine question, not trolling. If a platform already has a good REST API, what does an MCP server add other than a different envelope? My agent can already call the API.
Showing 6 threads. Read the guides for pillar reports and comparisons.