Skip to main content
Your CRM, contacts, workflows, and reporting live in HubSpot. The slow part is making the email: design, copy, and brand review. This recipe keeps HubSpot as your system of record and sending platform, and moves only creation to Brew. Nothing about your HubSpot setup changes. Brew exports finished designs into Marketing Hub as reusable templates. Your audiences, automation, and attribution stay where they are.
Before you start. Add your brand from your website, and connect the HubSpot integration. Custom email templates need HubSpot Marketing Hub Professional or Enterprise. You do not need a verified Brew sending domain for this recipe, because HubSpot does the sending.

1. Create the Email in Brew

Open Emails and describe what you need. Brew designs it on brand from your design system: layout, copy, and images. Iterate in chat or edit inline until it’s ready. Merge tags convert to HubSpot’s syntax on export. Standard fields such as {{ firstName }} map to HubSpot’s property names, and a fallback becomes HubL’s default filter. Write a custom field as {{ contact.<internal name> }}. A bare {{ company }} reads nothing in HubSpot. The HubSpot integration page lists every mapping. After the export, preview the email as a specific contact in HubSpot to check that the personalization renders.

2. Export the Design to HubSpot

Click Send in the top right, choose Export template, and pick HubSpot. The design lands in the Brew folder of HubSpot’s email template picker, under Marketing → Email → Create email. The HubSpot integration page covers the full click-path. Exports cost no credits.

3. Send from HubSpot as Usual

In HubSpot, build your email from the exported template, pick your list, and send or schedule. Your HubSpot workflows can use the template like any other. Opens, clicks, and attribution report in HubSpot, next to the rest of your funnel.

When to Revisit This Split

This split solves the creation bottleneck. Two signals it’s time to go further:
  • You want engagement-based audiences and per-step automation analytics in one place. That’s Brew’s Audience and Automations surface.
  • Your team or agents want to run the whole loop, create to send to analytics, over MCP.
Until then, this recipe works as a complete setup.

From an Agent or Code

Over MCP, create_email and edit_email make the design, and export_email with provider: "hubspot" pushes it to Marketing Hub. Over the API that is POST /v1/emails/{emailId}/export. Pass dryRun: true first to check the design and the connection without creating anything. The HubSpot page has the request and the error codes. A dry run doesn’t prove HubSpot accepts the template, so open it in HubSpot after the real export.
  • HubSpot: connecting the account and where exports land.
  • Emails: exporting from the canvas.
  • Merge Tags: how tags map to another platform’s syntax.
  • Integrations: the other platforms Brew exports to.

Need Help?

Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you:

Search Documentation

Type in the “Ask any question” search bar at the top left to instantly find relevant documentation pages.

Ask ChatGPT or Claude

Click here to open the Copy page menu at the top of this page, then send the page to ChatGPT, Claude, or your editor.