> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-components/action/send-e-mail.md).

# Send e-mail

An email template contains the email’s prepared content and layout. This journey step chooses that template and defines the sender details shown to recipients.

Use **Send E-Mail** to send a configured email template when users reach a journey step. Select the template, configure sender and message details, personalize supported fields, and save the action.

### Step 1: Add the action

1. In **Journey Builder**, select **Add Step**.
2. Under **Action**, select **Send E-Mail**.
3. Enter a **Step Name**.

Use a descriptive internal name, such as `Send abandoned-cart email`. It helps you locate the step in the journey. Recipients do not see it.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FOEf5o1pTvz9LYGtmwidQ%2FScreenshot%202024-10-02%20at%2015.39.37.png?alt=media&amp;token=d3254e01-9b29-4133-9068-47a692442497" alt="Send E-Mail action in the journey builder" width="319"><figcaption><p>Select <strong>Send E-Mail</strong> from the Action section.</p></figcaption></figure>

### Step 2: Configure the email

Complete the email settings.

Select the template first. Then complete the sender and inbox-preview fields. These fields help recipients recognize the email before opening it.

<table><thead><tr><th width="184.29296875">Field</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Step Name</strong></td><td>Internal name for the journey step.</td></tr><tr><td><strong>Mail Template</strong></td><td>Pre-designed email content and layout.</td></tr><tr><td><strong>From Address</strong></td><td>Sender address shown to recipients.</td></tr><tr><td><strong>Sender Name</strong></td><td>Name shown beside the sender address.</td></tr><tr><td><strong>Subject</strong></td><td>Email subject shown in the inbox.</td></tr><tr><td><strong>Preheader</strong></td><td>Preview text shown after the subject.</td></tr><tr><td><strong>Reply To</strong></td><td>Address that receives recipient replies.</td></tr></tbody></table>

For example, select a `Black Friday` template, set **Sender Name** to `Your Brand`, and use `Your offer ends tonight` as the subject.

Use a sender name that recipients recognize. Write a subject that describes the email’s value. Use the preheader to add supporting context.

Select **Mail Template** before completing the message details. The template provides the email body and layout. **Subject** and **Preheader** control the inbox preview. They do not replace the template content.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F09VlcxKC7tsJXH27zIuw%2FScreenshot%202024-10-02%20at%2015.37.14.png?alt=media&amp;token=58f538e3-4f35-4952-9827-8eb96e817a01" alt="Send E-Mail configuration panel" width="563"><figcaption><p>Select a template and configure sender details.</p></figcaption></figure>

### Step 3: Add personalization

Use supported profile attributes and journey variables in the subject or email content.

Profile attributes use stored user information. Journey variables use values collected or set in the current journey.

For example, use `Hello @name!` in the subject. The resolved profile name appears for each recipient.

Use journey values when the content depends on the current flow. For example, `@ProductName` can display the product captured during the journey.

Only use a value when it is available for the user reaching the step. For example, use a name stored in the user profile. Use a product variable only after an earlier journey step has provided it.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FoqmR3Gdhq6DzrH864FYV%2FScreenshot%202024-10-02%20at%2015.37.56.png?alt=media&amp;token=d806f909-843f-4082-94ea-958a1fcdd7dd" alt="Email personalization settings" width="563"><figcaption><p>Use supported values to personalize email content.</p></figcaption></figure>

### Step 4: Verify sender settings

Confirm that **From Address** and **Reply To** are configured through the email-provider integration.

The **From Address** identifies the sender. The **Reply To** address receives recipient responses. These can be different addresses.

Choose a **From Address** that recipients recognize. Choose a monitored **Reply To** address when recipients may need help or have questions about the email.

{% hint style="info" %}
The sender and reply-to addresses must be set in the email-provider integration before use. See [Email provider integration](/netmera-user-guide/omnichannel-engagement/email/email-onboarding.md).
{% endhint %}

### Step 5: Save the action

Select **Save**.

The email action appears in the journey flow. The selected template sends when eligible users reach the step.

For example, users who reach an abandoned-cart branch can receive the selected recovery email. Users who do not enter that branch do not receive it.

Review the selected template, sender fields, subject, and preheader before saving. These settings together determine the email recipients receive.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-components/action/send-e-mail.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.