Recorded on Nov 22, 2025 9:00 AM
Manually rebuilding email designs in your ESP and then copying translations back and forth between tools? There’s a better way. In this webinar, I show you how to design once in Figma, export directly to Iterable, and manage translations in Lokalise—all without touching a single line of code.
What You’ll Learn
If you’re sending multilingual email campaigns and dealing with the tedious process of managing translations across templates, this tutorial is for you. I walk through:
The Traditional Translation Workflow (And Why It Sucks)
Most teams are trapped in this painful cycle: Designer creates email → Developer rebuilds it in the ESP → Marketer exports content to translation team → Translation team returns files → Someone manually copies translated text back into multiple ESP templates → Repeat for every language and every campaign. It’s slow, error-prone, and makes you want to stick to English-only emails forever.
The Better Way: Design → Export → Translate → Sync
Instead of juggling files and manually copying content between tools, you can create a seamless workflow where: You design your email once in Figma → Export it as responsive HTML directly to Iterable → Import the template into Lokalise where your translation team (or AI) translates everything → Export back to Iterable where all your locale versions update automatically. Done.
Setting Up Your Template for Localization
Before you can translate anything, your Iterable template needs to be set up properly. I show you how to:
- Export your Figma design to Iterable using the Email Love Figma Plugin
- Add locale options to your template in Iterable (English, French, German, etc.)
- Prepare your template for import into Lokalise
Connecting Lokalise to Iterable
The integration is surprisingly straightforward. You’ll see how to:
- Create a new Marketing & Support project in Lokalise
- Select your base language and target languages
- Generate a server-side API key in Iterable
- Connect Lokalise to Iterable using that API key
- Import your templates from Iterable into Lokalise
The Translation Process
Once everything’s connected, your translation workflow becomes dead simple. I walk through:
- How Lokalise automatically extracts all translatable content from your email
- What the translation interface looks like (your translation team will actually use this part)
- How to use Google Translate for quick translations (or connect to professional translation services)
- Which elements get translated vs. which ones stay the same
Exporting Translations Back to Iterable
This is where the magic happens. Instead of manually copying translated text back into your ESP templates, you just:
- Click “Export to Iterable” in Lokalise
- Wait a few seconds
- Check your Iterable template and see all your locale versions automatically populated
I show you the French and German versions of the email appearing in Iterable—same design, different languages, zero manual copying.
Who This Is For
- Marketing teams sending multilingual campaigns
- Anyone currently copying translations between Google Docs and their ESP
- Teams using Iterable who need to scale their translation workflow
- Email designers who want to stop rebuilding the same email in multiple languages
- Operations folks tired of being the translation bottleneck
The Demo
I use a real email design (our Email Love trend email) and translate it from English into French and German. You’ll watch me:
- Export the design from Figma to Iterable
- Set up locale options in the Iterable template
- Create a Lokalise project and connect it to Iterable
- Import the template into Lokalise
- Translate a few elements (headline, body copy)
- Export back to Iterable
- View the translated versions live in the template
Full disclosure: I use Google Translate for the demo, so apologies to any French or German speakers watching—I’m definitely not fluent. But you’ll see exactly how the workflow works.
Why This Matters
Look, I’ve been in email marketing for 15+ years, and I’ve seen teams waste countless hours on translation workflows that should take minutes. The difference between manually managing translations and using a proper integration like this isn’t incremental—it’s transformative.
Once you set this up, launching a campaign in 5 languages takes the same amount of time as launching it in one. Your translation team works in a tool built for translation (not your ESP). Updates cascade automatically. And nobody’s copying text between systems at 11 PM before a launch.
What You Need
- Email Love Figma Plugin (for the Figma → Iterable export)
- Iterable account with API access
- Lokalise account (they have a free tier to test this out)
- Email templates that need translating
Watch the video above to see the entire workflow in action. And yeah, if you’re sending multilingual emails and you’re not using something like this, you’re making your life way harder than it needs to be.
Questions? Email us at [email protected]
Speakers
Andy King
Founder, Email Love
Andy King is the founder of Email Love, an email marketing intelligence platform that curates and analyzes campaigns from over 5,000 brands. With 15+ years of experience at ESPs like Campaign Monitor, Sailthru, and Liveclicker, Andy has designed, coded, and shipped thousands of email campaigns. He created the Email Love Figma Plugin to solve the workflow inefficiencies that plague email production teams—letting designers work in Figma and export directly to any ESP without rebuilding in code. Andy writes weekly about email design, strategy, and the realities of building a bootstrapped SaaS business.
