How do I edit email templates?

Modified on Tue, 6 Jan at 11:30 AM

How do I edit email templates?

This guide covers how to edit email templates in Hubhus using the template editor for real-data previews, placeholder search, and advanced logic.

On this page

When you need to update the content, layout, styling, or logic in your Hubhus email templates, use the Hubhus Template Editor. It supports real-data preview, placeholder search, HTML components, and correct @if-logic evaluation. For a complete guide to using the editor, see Working with the template editor.

This article covers:

  • Where email templates are created and edited

  • How to modify template content

  • Using placeholders and dynamic logic

  • Working with layouts

  • Testing templates before sending

  • Conditional send requirements

  • Spam-protection rules

  • Common HTML email issues


Where to edit email templates

1. Campaign settings → Emails (create templates)

This is where you create and manage email templates.

Path:
Campaign Settings → Emails → New Email Template

After creating the template, click Edit to open the template editor.


2. Template Editor (edit templates)

The template editor is where you edit template content, test with real leads, and verify logic.

Advantages of using the template editor:
✔ Preview templates with real lead data
✔ Placeholder search using CTRL+K / CMD+K
✔ Correct evaluation of @if/@else logic
✔ Access to layouts, HTML components, and CSS
✔ Full visibility of spam rules, sender info, and requirements


For a complete guide, see Working with the template editor.


3. Automations / Action Listeners

You can create a template from an automation, but the editor view is the same.

We recommend:
Create template in automation → then click Edit to open the template editor for content editing and testing.


Editing template fields and configuration

Each template supports configuration of:

Recipient fields

  • To

  • CC

  • BCC

  • From name

  • From email

  • Reply-to email

All of these allow dynamic placeholders, e.g.:

%lead_email%
%assigned_person_email%
%brand_contact_email%

With conditional fallback logic such as:

@if(%assigned_person_email%){
  %assigned_person_email%
}@else{
  %brand_contact_email%
}@endif

Using the template editor

The template editor gives you all the tools needed for advanced email templates.

Search placeholders instantly (CTRL+K / CMD+K)

This opens the placeholder modal where you can find:

  • Lead placeholders

  • Event placeholders

  • Select field values

  • Booking form placeholders

  • Assigned person & brand placeholders

  • HTML components

  • Page links (@page[...])

  • Custom fields (API names)

  • Checklists

  • Relations

  • Files

  • JSON/data examples

  • Loops, variables, and advanced examples

You can search with natural language:
"lead name", "address", "event date", "signature", "assigned person", "offer", "checklist", etc.


Using @if / @else logic (correct Hubhus syntax)

Basic @if

@if(%assigned_person_name%){
Your consultant: %assigned_person_name%
}@endif

If / else

@if(%lead_postal_code% == 2000){
Special information for your area!
}@else{
General information…
}@endif

Comparison operators

Supported:
== != ~= >= <= > <

@if( {{post-nr}} >= 6000 ){
We cover your region.
}@endif

Contains (case-insensitive)

@if(%lead_email% ~= @gmail.com){
You are using a Gmail address…
}@endif

Logical operators

@if(%lead_type% == business || %lead_type% == vip){
Business/VIP info block
}@endif

Parenthesis are NOT supported.
|| is evaluated before &&.


Working with layouts

Templates can optionally use a parent layout, which defines:

  • Branding

  • Header / footer

  • Section structure

  • Styles

  • Wrapper layout

You only write the core content; the layout wraps it automatically.

Path:
Campaign Settings → Layouts


Dynamic content with placeholders

Placeholders inject dynamic lead/event data.

Examples:

%lead_firstname%
%lead_email%
%event_datetime%
@select[select_customer-type]
%assigned_person_phone%

Use CTRL+K / CMD+K to find them.


Testing templates

The template editor supports:

✔ Preview with real lead data
✔ Switch between different leads
✔ Test @if/@else logic
✔ Render HTML components
✔ Send test emails
✔ View final output exactly as customers see it

This eliminates guesswork.


Conditional sending requirements

Templates can be restricted to send only if certain conditions are true.

Two modes:

  • Always allowed to be sent

  • Conditionally allowed to be sent

Example requirement:

@if(%lead_postal_code% == 2000){1}@endif

If the expression evaluates to false / empty / 0 / false / off / nej / no,
→ The email will NOT send.


Spam protection rules

Each template includes configurable sending limits:

  • Max emails per lead

  • Max emails per email address

  • Blacklist campaigns

  • Whitelist campaigns

  • Frequency limit (e.g., max 1 per hour)

  • Unsubscribe handling

If emails aren't sending, always check these rules.


Common HTML issues in email clients

Email HTML is old-school. Follow these best practices:

✔ Use <table> based layout
✔ Keep styles inline
✔ Use absolute URLs for images
✔ Use Hubhus HTML components when possible
✔ Close all tags
✔ Avoid advanced CSS, scripts, flexbox, grid, external stylesheets


Summary

To edit email templates correctly:

✔ Create templates under Campaign → Settings → Emails

✔ Click Edit to open the template editor

✔ Insert placeholders using CTRL+K / CMD+K

✔ Use Hubhus-style @if logic (not standard code syntax)

✔ Apply or change layout when needed

✔ Configure conditional sending rules and spam protection

✔ Test with real leads before activating the template

? Common searches

email setup • send email • email template • automated email

? Also known as

message • notification • mail

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article