Skip to content

Transactional Emails

Transactional emails are essential emails needed for basic functions like registration or password resets. For example, if a user wants to register with their email address or reset a forgotten password, an email must be sent.

Users can't unsubscribe from transactional emails because they are necessary. Also, transactional emails are not associated with any subscriber lists. They are sent directly to specific email addresses.

You can find the transactional emails of a project under the Transactional Emails tab.

A screenshot of a project's transactional emails.

Creating a Transactional Email

To create a new transactional email, click the Create button.

A screenshot of a project's transactional emails - new button highlighted.

Next, select a template category defined in your project's design system.

A screenshot of a project's transactional emails - create: select template category.

Then, choose a template to start from, also defined in your design system.

A screenshot of a project's transactional emails - create: template selection.

Enter the name, subject line, and preview text for your email. You can personalize these with merge tags!

A screenshot of a project's transactional emails - create: enter data.

After that, you will see a summary page. Click "Launch Editor".

A screenshot of a project's transactional emails - create: summary.

Finally, make changes in the drag-and-drop email editor:

A screenshot of a project's transactional emails - create: edit.

When you're done, click "Save & Close". You can make changes later as well.

Transactional Email Integration

Every transactional email in bluefox.email has a unique URL for sending the email. Send an HTTP request to this endpoint. You can generate sample code in multiple programming languages by clicking this icon:

A screenshot of a transactional email card, with the code button highlighted.

Copy the generated code to use it in your project:

A screenshot of a transactional email's generated code, copy button highlighted.

Security Warning

Your bluefox.email API key is included in the request Authorization header. Never send these requests from your frontend!

See our API docs for more details.

Transactional Email Personalization

You can personalize transactional emails with handlebars. The data you send to the transactional email's endpoint determines the available variables. For example, you can send a user's name:

javascript
await fetch(yourEndpoint, {
    method: 'POST',
    headers: {
        'Content-Type': 'application/json',
        'Authorization': 'Bearer YOUR_API_KEY'
    },
    body: JSON.stringify({
        email: 'joe@doe.com',
        data: {
            name: 'Joe Doe'
        }
    })
})

You can use any handlebars variables in your email while editing. Click on the edit icon on the card:

A screenshot of a transactional email card, edit button highlighted.

Enter your variables with Handlebars syntax:

A screenshot of a transactional email being edited, a merge tag is being added.

You can also use merge tags in the email's subject line and preview text!

A screenshot of a transactional email, with a merge tag being used in the subject and the preview text.

For more details, read our guide on personalization with merge tags and Handlebars.