Automating the path from Figma to enterprise email campaigns

A major Spanish retailer designed its corporate emails in Figma and rebuilt them manually for Salesforce Marketing Cloud. Tailor created a plugin that generates production-ready email HTML, then integrated it across five internal teams and the company's existing security, infrastructure and production systems.

Automating the path from Figma to enterprise email campaigns

Client

The client is one of Spain's largest retail corporations. Its digital marketing operation works within a large technology organisation responsible for infrastructure, production, information systems, architecture and security.

Corporate email is used across different parts of the business, each with its own footer, content and tracking requirements. Every campaign also has to render reliably across email clients that interpret HTML in different ways.

Challenge

The marketing team designed its emails in Figma. Turning each design into a working campaign required someone to export the layout, adapt it manually and prepare the HTML for Salesforce Marketing Cloud.

An external production supplier handled that conversion. Each email therefore generated another block of recurring, billable layout work before the campaign could be launched. The manual handoff also created repeated opportunities for small differences, broken links, missing accessibility attributes or rendering problems to reach the final campaign.

The client wanted to connect the tools already used by both teams, allowing designers to produce email HTML from Figma while preserving the company's standards and production controls.

What we built

Tailor built a Figma plugin in TypeScript that converts approved email designs into HTML prepared for Salesforce Marketing Cloud.

The plugin applies the company's email rules during generation. It supports 15 corporate footers, responsive desktop and mobile menus, UTM parameters, ALT text and the adjustments required for Outlook, Yahoo and other major email clients. Images are stored through the client's existing SGFM server.

The workflow keeps design and generation inside Figma. The resulting HTML is prepared for the system where the campaign will be managed and sent.

Working inside the constraints

The functional plugin established the core workflow. Reaching production required another five months of integration within the client's existing technology environment.

The code moved into the corporate Bitbucket and every change had to pass Kiuwan and Sonar quality and security checks. Delivery involved five internal teams: Distributed Systems DevOps, Infrastructure, Production, Information Systems, and Architecture & Security.

Automated email testing shows how those constraints shaped the product. Litmus was the initial choice. The API access required by the plugin was unavailable, and its native Salesforce Marketing Cloud integration required an Enterprise plan outside the client's existing setup.

Tailor ran a structured evaluation of Email on Acid. Its documented API allowed the plugin to upload and test HTML without additional SMTP or domain configuration. Tests could be launched from Figma against selected email clients and devices, then shared with stakeholders through public review links.

The team selected the testing platform that could be automated, approved and operated within the client's environment.

Impact

The marketing team gained a repeatable path from an approved Figma design to HTML prepared for its campaign platform. The plugin automates the translation work that previously had to be commissioned from an external production supplier for every email and applies corporate requirements during generation.

Each compatible campaign can now be generated within the team's existing Figma workflow, avoiding another unit of external layout work and its associated lead time. For a retailer producing emails across multiple business divisions, that saving repeats every time the plugin is used.

The product reached production after passing the company's code, security and architecture controls. Tailor continued working on accessibility, testing, technical debt and later evolutions after the initial delivery.

The current documentation does not contain the volume or cost data needed to quantify the result. The number of emails generated, supplier hours or fees avoided, internal review time saved, reduction in production errors and number of active users still need to be validated.