Channels Template Editors

The channel template editors are where you define the content of the notification that is delivered to your subscribers when a workflow runs. Each channel exposes an editor aligned with how messages are delivered on that channel:

• SMS and chat: Body field only
• Push, email, and in-app: Subject and body fields

All editors (including the Subject field editors) support variables and dynamic data that can be used to personalize notification content. Notification preview is also supported on all editors. While some channel editors share common features, some channels expose additional channel-specific features that can be used to configure and customize the notification content for that channel.

​

In-app template editor

The in-app template editor defines how notifications appear inside your application through the Novu <Inbox />. In-app notifications are UI-driven, not just message-driven. This means that the template is responsible for both content and interaction. The template editor lets you control what users see, how they act on it, and how it appears in your application and consists of the following configurable fields:

​

Disable content sanitization

By default, Novu sanitizes both the subject and body fields to prevent unsafe HTML from being rendered. This includes sanitizing:

• Suspicious HTML tags.
• HTML entities such as <, >, and &.

You should only disable content sanitization when:

• You fully trust the trigger payload.
• You control all dynamic data sources.

​

Avatar customization

You can control how the notification avatar is displayed using one of the following methods:

• Provide a custom avatar URL.
• Select from the available built-in icons.

​

Action buttons

In-app notifications support primary and secondary actions. For each action, you can configure:

• Button text
• Redirect URL
• Navigation targets (_self, _blank, _parent, _top, and _unfencedTop)

Actions allow users to respond directly from the Inbox without navigating elsewhere in the UI.

​

Redirect URL

The redirect URL defines where the user is navigated when the notification itself is clicked. You can:

• Define a static or dynamic URL.
• Control navigation behavior using targets.
• Omit the redirect URL and handle clicks using the onNotificationClick handler in the <Inbox /> component.

This enables full control over client-side navigation behavior.

​

Data object

The data object is a customizable key-value store available in the in-app step. You can use it to extend each Inbox component notification by embedding custom data.

​

Email template editor

The email template editor defines how email notifications are structured, rendered, and delivered. Novu dashboard provides multiple authoring modes:

​

Block editor

The block editor is a WYSIWYG editor that allows you to create and edit email templates. It has two fields: subject and body. A block can be added by clicking on the plus (+) icon in the top-left corner of body field or by adding a forward slash (/). In both cases, a menu appears with the list of supported blocks: You can duplicate or delete blocks using the block menu controls.

​

Custom HTML block

The custom HTML block allows you to insert raw HTML inside a block editor layout.

• Allows injecting variables using {{ ... }}
• Supports LiquidJS control structures like {% for %} or {% if %}

Use this block when you need inline markup control within a visual layout, but don’t require full LiquidJS logic.

​

Repeat block

The repeat block lets you iterate over an array and render its child blocks for each item in that array. It works similarly to a JavaScript for loop and is used for displaying structured or repeated data such as order items, activity feeds, or grouped records. When the workflow runs, Novu evaluates the array you provide and repeats the block’s content for every element, allowing you to build dynamic lists. In the video above, the repeat block iterates over the following array:

• {{payload.order.items}} is the array containing the items in an order.

Within the repeat block, each item in the array becomes the current iteration context, which allows you to reference item-level properties directly. For example:

• {{payload.order.items.name}}
• {{payload.order.items.price}}

This approach ensures each item in the array is rendered with its own data, making the Repeat block ideal for building dynamic, data-driven content.

​

Show block conditionally

The show block conditionally feature lets you control whether a content block is rendered based on runtime data. It allows you to show or hide specific parts of a template using conditions evaluated against subscriber properties or payload variables when the workflow runs. This is useful for keeping templates flexible and avoiding duplicated layouts, for example, showing a call-to-action only when it’s relevant to the recipient. The feature is supported by the following blocks:

• Button block
• Custom HTML block
• Image block
• Repeat block

In the editor, conditional visibility is accessed using the eye icon on a supported block. When enabled, you define a condition that determines whether the block is rendered. For example, you can display a Track your order button only when a subscriber has a custom data field showTracking set to true. You can apply the same logic using payload variables passed when triggering the workflow, allowing content to adapt dynamically to each notification.

​

Digest block

The Digest block allows you to loop over the events collected by your digest step and displays them in your email content. It handles both layout and repetition automatically. The Digest block is only available in Email steps that come after a Digest step in the workflow. When you add a digest block to your email template editor:

• Novu automatically inserts a Repeat block that iterates over the digested events.
• You can define how many times the event is iterated.
• Inside the loop, you can also use the special alias variable current to reference the item currently being processed, for example, current.payload.name.
• The block also supports rendering a summary using the steps.digest-step.eventCount variable, typically with the pluralize LiquidJS filter.

​

Code editor (Custom HTML)

The code editor provides a built-in interface for writing raw HTML and embedding LiquidJS expressions directly inside the Novu dashboard. This gives you full control over layout, structure, and rendering beyond the capabilities of Novu’s block editor. The editor supports advanced use cases such as:

• Migrating existing HTML email templates
• Implementing full design systems
• Executing flow control logic directly inside email templates
• Complete layout and styling freedom without editor constraints

​

Email layouts

Layouts are reusable components used with email steps in the workflow, designed to bring consistency, maintainability, and efficiency to your email communications. With layouts, you can create a component using headers, footers and other branding elements and reuse that component across multiple email steps. Every layout must include the {{content}} variable. This variable dynamically injects the content of the email step.

​

Layout features

• Reusable across workflows.
• Support both block and code editors.
• Each environment maintains its own set of layouts.
• Supports variables and translations.

​

Apply an email layout to a workflow

1. Navigate to Workflows page on Novu dashboard.
2. Select a workflow from the list.
3. Select an email step.
4. Choose your layout from the Layout selector.

The selected layout wraps around the content written in the email editor.

​

Manage email layouts

Email layouts are managed from the Layouts section of the Novu dashboard. From here, you can create, edit, delete, and reuse layouts across workflows. Create an email layout

1. Navigate to the Layout page on Novu dashboard.
2. Click on the Create layout button on the top right corner.
3. Fill in:

• Layout name: Provide a human-readable name.
• Identifier: Provide a unique ID. Novu generates one automatically if you do not provide it. You cannot change the identifier after it is created.

4. (Optional) Enable translations for the layout.
5. Click Create layout.

A new layout is created and can be edited using either the block editor or the code editor. Edit email layout

1. Navigate to Layout page on Novu dashboard.
2. Select a layout from the list.
3. To update the layout name or enable translations, click the cog icon in the editor.

4. Modify the layout content using the block or code editor.
5. Click Save changes.

Changes apply immediately to all workflows using the layout. Delete an email layout

1. Navigate to Layout page on Novu dashboard.
2. Select a layout from the list.
3. Click the cog icon in the layout editor.
4. Click Delete layout and confirm. If the layout is used by an email step, then you are notified on which step uses this layout.