Email editor
Compose lifecycle emails. Personalize from the same profile that triggers them.
A block-based editor wired directly to your event stream. Drop in personalization tokens, branch on plan or behavior, preview against real profiles, and send a test before you commit.
Inside the editor
The building blocks behind every template.
Eight block types, personalization variables pulled straight from the profile, and saved sections you can reuse across templates.
Heading
Text
Button
Image
Divider
Columns
Condition Soon
HTML
Personalization pulls straight from the profile, no separate merge-field list to maintain:
-
user.first_name(trait) -
user.plan(trait) -
user.signup_age_days(computed) -
event.source(event) -
workspace.name(trait)
Saved blocks carry over between templates: Header - logo + plan , Footer - legal , CTA - primary .
A worked example. A trial-activation
template, from hello@getfluxly.com to {{user.email}}, subject {{user.first_name}} - your first project is
one click away.
Hey Neo, your first project is waiting.
You signed up
{{user.signup_age_days}}days ago but haven't created a project yet. The fastest way to feel what your team can do here is to start one - even an empty one. We'll have it ready in under a minute.Create your first project →
Below the fold: "If this isn't useful, you can unsubscribe from onboarding emails. We won't send these forever."
Built for lifecycle, not for newsletters
Behavior in. Personalized email out.
The editor isn't a separate tool, it lives next to the same automations and segments that decide who gets the email. Edit the template and the next run picks it up.
Block-based, not blank-canvas
Heading, text, button, image, columns, divider, condition, raw HTML. Drag in, drop out. No template chaos.
Variables from real profiles
Any trait, any event property, any computed value on the profile. Type two braces to insert.
Conditional blocks Coming soon
Show a block only if the user is on a specific plan, in a segment, or matches a property. One template, many audiences.
Test against a real profile
Render the email exactly as it'll send for any profile in your workspace. Catch broken variables before they go out.
Any trait. Any event property. Any computed field.
Use anything that's on the profile, no separate "merge fields" to maintain. When a trait updates, the next send picks it up.
-
{{user.first_name}}with smart fallbacks -
Liquid-style filters:
| capitalize,| date,| pluralize - Trigger event properties available alongside profile traits
One template, many audiences.
Show or hide a block based on plan, segment, or any trait. The same trial-activation email can read differently for free, team, and self-serve users. Conditional blocks are coming soon.
-
if/elseif/elseon any block - Reference segments by name, not raw filters
- Preview the email as any specific profile
For example: show "Invite your team - your first 5
seats are free" when user.plan is team,
"Try a paid plan free for 14 days" when it's
free, and "Pick up where you left off" otherwise.
Preview the email as any real profile.
Pick a specific profile, render the template the way it'll actually send for that user, and ship a test send to your inbox before going live.
- Render with real trait values, not "John Doe" placeholders
- Side-by-side desktop / mobile preview
- Variable lint warns on missing or undefined fields
Rendering as neo@zion.io, three days after
signup and on the free plan, resolves to "Hey Neo,
your first project is waiting."
Specs
The boring details (that aren't, actually).
Rendering
Rendered server-side, sent through your provider
Templates render to HTML on send, with your variables resolved against the customer profile at that exact moment. Not at template-edit time, not at queue time.
Compatibility
Email client compatibility you can audit
HTML output uses table-based layouts under the hood. Renders cleanly in Gmail, Apple Mail, Outlook 2016+, and the major mobile clients. Dark-mode friendly.
Versioning
Every save is a version
Every save creates a version you can roll back to. See who changed what, when, and which automation runs used which version of the template.
Localization
Locale-aware (coming soon)
Per-locale variants of the same template, picked by user.locale. Coming soon.
Get started
What you can do on day one.
No separate add-on, no extra cost: the editor ships on every plan.
- Build a template with blocks, variables, and conditions.
- Trigger it from any tracked event or trait change.
- Send through your existing ESP (SES, Mailgun, Resend, SMTP).
- See per-template send, open, and click metrics.
FAQ
Questions, answered.
Do I need to know HTML to use the email editor?
No. The editor is block-based: heading, text, button, image, columns, divider, and raw HTML if you want it. Drag a block in, drop it out, and nothing requires markup unless you choose the HTML block yourself.
Where do the personalization variables come from?
Straight from the customer profile. Any trait, any event property from the event that triggered the send, and any computed field GetFluxly derives, like signup_age_days, are all available. There's no separate merge-field list to maintain.
Can the same template show different content to different segments?
Conditional blocks, which let one template branch on plan, segment, or any trait, are coming soon. Today you build a separate template per audience; conditional blocks will collapse that into one template with branches.
Which email providers can I send through?
Whichever you already use. Send through your existing ESP, Amazon SES, Mailgun, Resend, SMTP2GO, or any custom SMTP relay, and GetFluxly handles the template, the personalization, and the trigger.
Is the email editor included?
Yes, it's part of the one plan at no separate cost. Every new account also starts with a 14-day trial, no card required.