Get Started
Integrations
Docs chevron_right Integrations chevron_right Export to HubSpot

Export to HubSpot

Push any finished EmailFlow AI email into your HubSpot portal as a coded email template in the Design Manager — the exact final HTML the AI Design Studio produced, plus the small footer block HubSpot requires of every email template.

Connecting HubSpot

Open Integrations in the sidebar and click Connect on the HubSpot card. You are sent to HubSpot's own authorization screen; pick the portal, approve access, and you are returned here with the connection live. Tokens are stored encrypted at rest, and HubSpot's short-lived access tokens are refreshed automatically in the background — you never re-authorize just because time passed.

info
Coded email templates live in HubSpot's Design Manager, which requires Marketing Hub Professional or Enterprise on the connected portal. That is a HubSpot product boundary, not ours — on lower HubSpot tiers the push is refused by HubSpot and the error appears in your export log.

Pushing an email

From Email Templates, open the more_vert menu on any template card and choose Push to ESP — or use the Push to ESP button in the AI Design Studio's top bar. Pick HubSpot and the export is queued; when it lands, the dialog links you straight to your portal's Design Manager.

emailflow.ai/rui/email-templates
The Push to ESP dialog listing Mailchimp, Klaviyo, and HubSpot: connected providers show a Push button, unconnected ones a Connect link
Pick a destination — connected providers push immediately, the rest link to setup.

The design lands in Design Manager under an emailflow/ folder, named after your template. To send with it, create a marketing email in HubSpot and choose the template from the coded-templates list.

What HubSpot receives

HubSpot is stricter than other ESPs about what an email template must contain, so the pushed file is your final HTML — identical to Download HTML, byte for byte — wrapped in exactly two HubSpot-specific additions:

  • A template annotation at the top marking the file as an email template, so it is selectable when you create a marketing email.
  • A CAN-SPAM footer before the closing tag, using HubSpot's own variables for your company address and the unsubscribe links. HubSpot refuses to send marketing email from templates without these; the block renders from the portal's account settings, so it always shows your details. If your design already carries HubSpot unsubscribe variables, no second footer is added.

The export log

Every push is recorded on the connection's Manage page (Integrations → HubSpot → Manage) with its status, timestamp, a Design Manager link, and — for failures — HubSpot's error message verbatim.

emailflow.ai/rui/integrations/mailchimp
The Manage connection page for an ESP: connection status card with Disconnect, above a table of past exports with status badges, timestamps, and links to the exported artifact
The Manage page (shown here for Mailchimp) — the surface is identical for every ESP.

Troubleshooting

  • The connection shows an error badge. HubSpot rejected our credentials — typically the app's access was revoked in the portal, which also invalidates the refresh token. You get an in-app notification when this happens. Click Reconnect on the Manage page to re-run the OAuth approval; history is kept.
  • An export failed with a permissions or product-tier error. The portal likely lacks Marketing Hub Pro/Enterprise (see the note above), or the approving user cannot write to the Design Manager. The log row carries HubSpot's exact message.
  • Push to ESP asks me to upgrade. Template export follows the same plan flag as Download HTML; it is available on paid plans.

Disconnecting from the Manage page deletes the stored tokens immediately, while your export history stays visible.