Templates
Write the email once, send it with your data.
Save a template with merge fields, then send it by alias and pass a model of values. Keep the design in one place, out of your codebase, and preview exactly what recipients will see.
Subject: Reset your password, {{name}}
Hi {{name}},
Tap the link to set a new password. It
expires in {{expiry_minutes}} minutes.
{{reset_url}}
— The {{product}} teamTemplates that live outside your code
Change wording without a deploy, keep a plain-text alternative in step, and see the result before anyone else does.
Merge fields
Drop {{ placeholders }} into subject and body, then send a model of values and Mailhuset fills them in per recipient.
Send by alias
Reference a template by a stable alias, so you can edit copy in the dashboard without touching or redeploying your app.
Versioned edits
Every change is a version, so you can compare, roll back a mistake, and know exactly what was sent when.
Preview and test send
Preview a template with sample data and send a test to yourself before it reaches a single real recipient.
Shared layout
Keep a common header and footer in one layout, so a brand change updates every template at once.
Plain text kept in sync
Each template carries an HTML and a text version, so clients that prefer plain text still get a clean message.
Common questions
- Can I edit a template without deploying my app?
- Yes. Templates are referenced by alias, so you change the wording in the dashboard and your next send uses it, with no code change.
- What if a merge field has no value?
- You can set a fallback, and the preview shows unfilled fields clearly, so a missing value never ships as a broken placeholder.
- Can I roll back a template change?
- Every edit is versioned. You can compare versions and restore an earlier one whenever you need to.
Move your emails out of your codebase
Create a template, add your merge fields, and send it by alias from a single request.