Sync Live HTML to Marketo
Courtney Scharff, manager of marketing ops at Figma, on Figma's marketing operations stack
This feature request shows that the bottleneck in email production is no longer writing HTML, it is moving approved code into the sending system without breaking the workflow. Figma uses Parcel as the place where marketers build and review email code, but Marketo is still the place where subject lines, tests, and final sends happen. That leaves a manual copy and paste step every time the team edits an email, which turns a modern editor into a partial solution instead of the system of record.
-
Figma’s team owns the full marketing email process in Marketo for roughly 130 marketers worth of launches, newsletters, events, and lifecycle sends. Parcel improved collaboration versus local editors, but final testing still happens in Marketo, so syncing live HTML would remove repetitive handoff work at the exact point where campaigns ship.
-
Parcel’s broader product vision already points in this direction. Its component system lets teams update a button, color, or layout once and regenerate current HTML everywhere, but Parcel still requires manual export into the ESP. Automatic sync into the sender is the missing link between design system logic and actual campaign execution.
-
This is also where tools split. Parcel is strongest as a developer style email editor with comments, previews, and reusable components. Litmus has historically pushed further into ESP integrations and in app previews inside tools like Marketo. The market is moving toward fewer import and export steps, because that is where teams lose time and introduce mistakes.
The next phase of email tooling is direct connection between creation and sending. The winning products will make the HTML, brand rules, approvals, and ESP record all update together, so teams no longer rebuild the same email in two places and can treat every send as a live artifact instead of a pasted file.