Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Email Templates

Creating an email template for Umbraco Forms.

Forms include Send email with template (Razor) Workflow. This allows you to pick a Razor view file that can be used to send out a pretty HTML email for Form submissions.

Creating an Email Template

To use custom templates with the Send email with template (Razor) workflow, place your files in the ~/Views/Partials/Forms/Emails/ folder. They will then appear as options in the dropdown menu.

The Razor view must inherit from FormsHtmlModel:

@inherits Umbraco.Cms.Web.Common.Views.UmbracoViewPage<Umbraco.Forms.Core.Models.FormsHtmlModel>

You now have a model with your Form fields. This can be used in your email HTML markup, along with the UmbracoHelper methods like Umbraco.TypedContent and Umbraco.TypedMedia, and so on.

Below is an example of an email template based on Example-Template.cshtml shipped with Umbraco Forms. Use this as a base for creating your own template.

Absolute URLs in load-balanced or proxied environments

The example below builds an absolute domain from Context.Request.Scheme and Context.Request.Host. This relies on the incoming request's Host header, which is fine when an email is rendered during a normal front-end form submission. It can produce empty or incorrect links when the email is generated outside of that request. Examples include re-running a workflow from the backoffice, or running it from a background or scheduled job. On a different node, or behind a load balancer or reverse proxy, the Host header may not match your site's public address.

From Umbraco 17, the Host header is no longer used to auto-detect the application URL by default. In load-balanced, proxied, or multi-node setups, set the application URL explicitly. This ensures absolute links - including the FormPageUrl exposed on the email model - resolve consistently on every node:

{
  "Umbraco": {
    "CMS": {
      "WebRouting": {
        "UmbracoApplicationUrl": "https://www.your-site.com/"
      }
    }
  }
}

See Web Routing Settings for details. When you need the public site URL inside a template, prefer reading it from this configuration (or IHostingEnvironment.ApplicationMainUrl) rather than from Context.Request.Host.

PreviousCustom MarkupNextWorking With Record Data

Last updated

Was this helpful?