> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reelevant.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Email

> Render personalized visuals for inclusion in email campaigns

<img src="https://mintcdn.com/reelevant/amH2YHA9709Bju3v/images/workflows/node-email.png?fit=max&auto=format&n=amH2YHA9709Bju3v&q=85&s=caa0b5a9795b5294a2d7de6df607f4df" alt="Email channel node on the workflow canvas" width="1024" height="768" data-path="images/workflows/node-email.png" />

## Overview

The Email channel renders a personalized visual for inclusion in email campaigns. It is the most commonly used channel type.

| Property          | Value                                                                    |
| ----------------- | ------------------------------------------------------------------------ |
| **Channel type**  | Email                                                                    |
| **Output format** | Email content                                                            |
| **Use case**      | Newsletter banners, product recommendations in emails, promotional slots |

## How It Works

When a user opens an email containing a Reelevant visual zone, the workflow is triggered in real time. The engine evaluates the workflow branches and returns the most relevant content for that specific user.

The rendered output is an image that is served dynamically at the moment the email is opened — ensuring the content is always up to date and personalized.

## Configuration

1. Add an Email channel node to your workflow canvas.
2. Connect it downstream to [data nodes](/product-guide/workflows/data-nodes), [logic nodes](/product-guide/workflows/logic-nodes), and an [output node](/product-guide/workflows/output-nodes).
3. After publishing, use the [Integration modal](/product-guide/workflows/integration) to get the embed code for your email template.

## Best Practices

* Use **multiple Email channels** if your email has several personalized zones (e.g., header banner, product grid, footer recommendation).
* Connect each channel to different data and logic branches if the zones require independent personalization logic.
* Test your email workflows with the preview feature before publishing to ensure the visual renders correctly across email clients.