Atlas L6ynztjd84

Stay updated on the status of all your company's support tickets.

Customer portal

Learn about sending transactional email with Loops.

Transactional emails are automated, API-triggered emails that are sent to individual contacts based on a specific action they have taken.

Unlike marketing emails (campaigns or loops), transactional emails are not promotional in nature and as a result, they do not require unsubscribe information to be included in the email.

Read how to send transactional email with our API. Read our detailed guide for sending transactional emails.

 are a type of promotional email that are sent to your list of subscribers or customers with the goal of promoting your product, service, or brand.

These types of emails can take many forms such as investor updates, product update newsletters, special offers, webinar invitations, customer case studies, and much more.

Marketing emails are a 1-to-many communication, meaning that the same exact email that you craft can (and probably will) be sent and read by a number of recipients or customers.

 are automated messages that are triggered by a specific user action.

These types of emails can include things like a purchase confirmation or password reset instructions.

Transactional emails are a 1-to-1 communication, meaning that the specific email sent will only be read by the single recipient it was sent to. These emails will typically include content that is unique and changing based on who is receiving it.

Marketing email (campaigns and loops) you send with Loops will contain an 

This key difference is due to legal requirements. You 

 send marketing emails as transactional emails through Loops.

Contacts behave slightly differently between transactional and marketing emails (campaigns and loops).

Your Audience only contains marketing contacts. If a new contact is sent a transactional email, they are not added to your Audience.

Sending a transactional email to a new contact will not trigger the 

 does not affect transactional emails. Unsubscribed contacts will still receive all transactional emails they are sent.

Introduction

How to send transactional email with Loops.

Sending transactional email with Loops has two steps.

First, you need to create transactional emails within Loops using our handy email editor. In your email you add data variables, which let you insert custom data into each email you send. To send transactional emails you need to use the Loops API. All it takes is a simple call to our transactional endpoint. Your request needs to include the ID of the transactional email you created, the receipient's email address and the data variables needed for the email.

There are two ways to create emails in Loops: using our editor or import an MJML template.

, letting you easily add formatting, images and buttons.

You can add dynamic data into your emails by using data variables (like 

 in the example above). Read on for more information about data variables.

 to use in the email. This is useful if you have a pre-existing template you want to use.

Like emails created in our editor, you can add data variables to MJML templates. To add a data variable called 

<mj-text>{DATA_VARIABLE:PasswordResetLink}</mj-text> 

Note the uppercase “DATA_VARIABLE” and the colon before the variable name.

Data variables let you insert dynamic values into each transactional email you send. Once you have added data variables into your email, you specify the value of each data variable in the API call to send each transactional email.

Let's say you have a password reset email that is sent once a user clicks a "Reset Password" button in your application.

For this we add two data variables to the email: 

We do not currently offer optional or conditional data variables. Using an empty string "" will also cause the email to fail.

You can insert data variables into the text of the email with the 

You can also add data variables as links (on text, images and buttons). This is how we add 

If you want to write the tags manually in your content, you can use our 

. To add a reset URL you can write a tag like this:

Data variables are also available in the email sending settings fields, like 

 button to view all fields and then click the data variable icon.

To send data to these fields, simply include the data variables in your API call as normal.

Read more about adding dynamic content into your emails.

Important information about data variables

 in your request. If you do not include the correct set of data variables in your API call, the send will fail.

We do not currently offer optional or conditional data variables. Using an empty string 

Data variable names are case-sensitive (meaning 

Data variable values sent over the API can be 

, you'll see the API Details section. This contains the data variables used in the email as well as a sample payload for reference. The “Transactional ID” lets you distinguish between different transactional emails when calling the API and is required.

To enable sending the email, it needs to be published by clicking 

In the example above, two Data Variables were used in the email and there is a transactional ID needed as part of our API call. Any data variables created in the email are required when making the API request.

Here's an example of the request for sending this email:

Send a POST to this endpoint (make sure to authenticate)

https://app.loops.so/api/v1/transactional 

You can copy an email's example payload from its Publish page in Loops by clicking the 

Chris

You can add contacts to your audience from this call by adding 

Read how to send transactional email with our API. Integrate our SDK into your JS or TS application.

The previous published version of the email will remain, and will continue sending until you republish the email. This means you can make changes to transactional emails without disrupting ongoing email sending.

When you have a draft, we retain both versions and you can switch between your draft and the published version using the toggles in the top left.

 and click the confirmation. Your draft will seamlessly become the published version.

After emails are sent, details are shown in the email's Metrics page.

These include send time and if messages experienced any issues with delivery (bounces or spam complaints).

Note that open and click tracking is disabled for transactional messages to improve deliverability for infrastructure-level communications.

You can test your transactional email integration by sending to email addresses with 

Everything will work as normal (e.g. you will receive success responses from the API), but no emails will be sent to 

 email addresses, making this a good way to test transactional emails without affecting your sending domain’s reputation.

This is a known issue with Apple Mail. Make sure that your links start with 

The first place to start is to check the body of the response. It will contain a JSON object with a 

 property that will give you more information about the error. Here are common reasons that the API might return with a 400-level error:

Trying to use the API for a transactional email without a published email message.

Missing a data variable that is required by the email message.

Guide

How to send attachments with your transactional email.

Need to send attachments with your transactional email? Just [reach out to us](mailto:help@loops.so) and we can enable the feature on your account.

 for a refresher on the transactional API email payload.

To attach a file to a transactional message, you'll need to add a 

 key to the standard transaction API email payload. The 

 key should be an array of objects, each with the following keys:

 - the base64 encoded content of the file

Here's an example of a transactional email payload with 

When you send this payload, the recipient will receive an email with the ICS file attached:

All the usual [transactional API email payload](/api-reference/send-transactional-email) keys are still required. The `attachments` key is in addition to the standard payload.

The total size of the payload must be less than 4MB

Attachments are not generally available. Please 

 if you need this feature enabled on your account.