Ensure that the markup used for the email is approriate for the email clients the recipients might use for the best results.
Field | Description |
Name | Name of the email. |
Envelope From | Also known as Return-Path or MAIL FROM most often the same as
the From email. |
From | The mail header FROM . Example: Alice <[email protected]>. |
Subject | Email subject shown as the title of the email. |
Add tracking pixel | Adds the tracking pixel {{.Tracker}} variable to the email. |
Click Editor
to show the editor options.
Button | Description |
Load File | Load the email contents from a file. |
Preview | Split the editor in half and previw on the right side. Auto updates on chages to content. |
Templates | List of available template variables to insert. |
Select domain | Select a domain to use when previewing the email. |
New Window | Opens a new window for previewing. Auto updates on changes to content. |
Create an attachment to sent it with emails.
Column | Description |
Name | Name of the attachment. |
Description | Description of the attachment. |
Embedded content | If set, the attached file will be scanned for embedded variables such as {{.URL}} this only works with plaintext file formats. |
Files | The file(s) to upload. Multiple files while create multiple attachments. |
STMP configurations are used for sending emails and setting mail delivery headers
Field | Description |
Name | SMTP configuration name. |
Host | The SMTP hostname. |
Port | The SMTP port, typically 465 or 587. |
Username | SMTP username to use for authentication. |
Own managed TLS | SMTP password to use for authentication. |
TLS certificate validation | If TLS errors while connecting via. SMTP should be ignored. |
Add custom headers to the SMTP delivery
To add a header, fill out the Key
and Value
and click
Save
API Senders are a alternative to delivering e-mail / lures with SMTP.
It allows you to send to each recipient via. a external API, by designing the outgoing request
and the expected response.
To use a API Sender, select API Sender
when creating a template.
Create a API Sender by describing the API request and the expected response content.
Column | Description |
Name | Name of the API Sender. |
Request URL | The URL to send the delivery request to. |
Request method | The HTTP method used for the delivery request. |
API Key | API key can be used as {{.APIKey}} in the request header and body. |
Request headers | HTTP headers for the request. |
Request body | The body of the request. |
Expected response code | The HTTP status code expected from the API response. |
Header matches | An expected match in the header. |
Response contains | An expected match in the body. |
Custom field 1 | Can be used as a template variable as {{.CustomField1}} . |
Custom field 2 | Can be used as a template variable as {{.CustomField2}} . |
Custom field 3 | Can be used as a template variable as {{.CustomField3}} . |
Custom field 4 | Can be used as a template variable as {{.CustomField4}} . |