9 June 2026

Fixed — exported Braze templates now render their buttons and spacing

The Stripo-to-Braze export carried the email's HTML but not Stripo's separate stylesheet, so in Braze the call-to-action buttons fell back to plain underlined links and padding collapsed. Stripo returns a template's styling in two parts — the HTML document and a separate CSS field with the real button look, spacing, and mobile rules — and the export now folds that CSS into the template's head before it reaches Braze, so an exported email renders the way it does in Stripo's own preview.

What shipped

•The fix — orbit_export_stripo_email_to_braze folds Stripo's separate CSS field into the exported template's head as a style block. Stripo's GET on an email returns two style carriers: the HTML document (which holds only stub class rules) and a separate ~16KB CSS field with the real button styling, padding, and mobile overrides. The first cut sent only the HTML, so buttons rendered as plain links and class-based spacing collapsed; the folded template now matches Stripo's hosted preview.
•Safe to re-run — the fold is idempotent (it will not stack a second copy on a re-export) and passes the HTML through untouched when an email has no separate CSS. Each exported email reports css_folded and css_byte_count so you can confirm the styling travelled.

NewerImproved — exporting to Braze overwrites by name instead of piling up duplicates OlderNew — export finished Stripo emails to Braze as templates, in one batched call

What's new