Atlas L6ynztjd84

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

Customer portal

How to create a scheduled email with Loops

How to send a daily, weekly or monthly email with a summary of what’s happened in your app.

This email type may also be referred to as a “rollup” email or a “summary” email. The idea is to send a single email that summarizes what’s happened in your app over a period of time.

These kinds of digest emails are a great way to keep your users engaged with your app.

The best way to do it today is a Loop with an 

 set to fire “every time” with an event payload containing the updated property you’d like to send.

Then at the end of the day, week or month you can trigger a digest email with a summary of the events that happened.

 trigger. You will enter the loop editor.

 node and type the name of your event. You can re-use an existing event or create a new one from this input.

 to your event. Properties are extra pieces of data that you can attach to each event. This data is then made available in every email you send.

 and add any properties you want to include in your digest email.

Make sure the “Trigger frequency” dropdown in the 

 selected, as we only want to email each user once per event.

The next step is to create the email you send to each contact.

. This will open the email editor, where you can 

When you want to add the event properties you created in the previous step, click the 

You will see a list of each event property, which you can then 

 for every property; if an event doesn’t have a value for a property in your email, the email will not send. Fallback values make sure that emails are sent to every contact.

When you’ve finished creating your email, click 

 in the top right. This will make your loop active and you can start triggering it by sending events.

With the API, it’s just a case of making a request to the 

 containing the contact’s details, the event name and your event properties.

{
  "eventName": "sendDigest",
  "email": "user1@gmail.com",
  "eventProperties": {
    ...
  }
}

Scheduled digest

Our updated, definitive guide for sending product updates.

A product update should be sent once a month with updates about what you shipped recently. This typically includes new features, improvements, and bug fixes.

Brevity is key. Users don't want to read a novel.

If you send valuable content, users will come to expect (and open) it.

It's okay to send multiple emails in a month if that's your shipping cadence.

Learn more tips for crafting effective emails and improving open rates.

Add a simple subject line, like "The latest updates from Loops"

Add a simple intro paragraph, with a link to the full changelog, potentially socials and a highlight of the most important changes along with a call to action to read the full email.

Try to limit the number of updates to 2-3, and make sure they are relevant to the content. It's better to have a single or a couple impactful, relevant updates than a long list of updates that are not relevant to the user.

In the footer, add a link to the full changelog, socials, and a link to unsubscribe.

Be careful not to overwhelm your users with too many updates. Focus on the most impactful changes.

If you're just starting out, send to all users and maintain a steady cadence over time.

If you have an existing list but haven't sent product updates before:

Send to active users who have engaged with your product in the last 30 days

Include users who have created an account in the last 30 days

If the audience size is less than 5,000 users, send to all users

Learn how to create targeted segments for your product updates. Learn how to create and send your first email in Loops. Add dynamic content to make your product updates more relevant. Create reusable elements for consistent product update emails. Explore different types of emails you can send with Loops.

Product updates

How to resend a campaign to new subscribers

A quick guide for sending a campaign to subscribers who signed up since you sent it out.

If you're regularly adding new subscribers via 

, it's likely that you will want to send a campaign to new contacts who signed up after you sent it initially.

In Loops, you can do this in two easy steps: duplicating the campaign and filtering the audience.

The first step is to duplicate the campaign so that you can send it out again.

To do this, go to the Campaigns page and click on the 

When you're ready to send the email, it's important that it only gets sent to contacts that haven't been sent it already.

 page of the sending flow, select "Not Sent" from the first dropdown and then the 

This will update the total contacts and the table below, which will show contacts that were not sent the original campaign.

Check that everything looks OK and continue sending the email.

Send to new subscribers again

How to send onboarding, dunning and churn emails to your customers with Loops.

For SaaS companies, there are a few important events in a customer lifecycle that email can help with.

 are emails sent after a user signs up for a waitlist, platform or newsletter.

 help brand new users get familiar with—and get the most out of—your product.

 attempt to get users active again if they haven’t used your platform recently.

 help reduce churn by prompting the user to re-activate a subscription or fix payment issues.

 attempt to bring users back after a cancelation.

With Loops, you can easily set up “loops” (email workflows) plus our API (or an integration) to help with each of these use cases.

To get this set up in Loops, the idea is to create a 

 for each of the types of email you want to send. So there would be a loop for activation emails and a loop for dunning emails and so on.

A loop is like an email sequence containing emails, time delays, audience filters and an initial trigger.

 to enter users into each of the loops at different times in their subscriptions.

; if the property is ever changed—using 

—we trigger a loop, which will send emails to the contact.

First, let’s add the contact property to the audience in Loops.

. Click on a table header to show the dropdown then select 

Enter “Subscription status” into the 

 is selected in the “Type” field. (You’ll notice that the “stored name” of your property is 

. This is the name we’ll use in the API and integrations).

 when you’re done. Your new property was added to the far right of the Audience table.

Now you can click on contacts and update the value manually one-by-one, or use the API or an integration to update contacts programmatically.

To update contacts in bulk you can download your Audience as a CSV, update values and 

The next step is to create the loops, one for each type of email. Repeat the following step for each of the different subscription statuses you want to send emails for.

 option, which will create a new loop using that trigger.

Now create the email(s) you want to send from each loop.

You can add as many emails as you like into each loop, separated with timers. If you want to send emails to certain groups of contacts, you can use Audience filters in your loop.

 available, which you can use as a base for all of your subscription emails.

If you want to use cohesive branding in your emails, make use of 

The final step is to make sure that your contacts have the correct “Subscription status” value assigned to them in Loops.

This will make sure they are in the correct loops at the correct moment within their subscription.

, with a request containing the contact’s email address and subscription status.

(You can also add more contact properties in this call if you want to add more data to the contact in Loops.)

Using the Update contact endpoint will either create or update a contact in Loops using the provided email address.

{
  "email": "canceleduser@gmail.com",
  "subscriptionStatus": "Canceled"
}

 allow syncing of contact data. Just make sure you create or update contacts and include the current 

Now you have set up different loops to trigger when the “Subscription status” value changes, your users will be automatically entered into each loop and receive the correct emails at the correct times during their subscription lifecycle.

Here are some example loops you can create along with a suggested trigger and loop contents.

: Contact added or Contact updated (e.g. 

: 1–5 welcome and onboarding emails over the first 30 days.

: 1–3 emails about paid-only features over the next 3 days.

Sent to customers who had a first failed payment.

: 1–3 emails during your dunning period.

Sent to customers who have just cancelled their payments.

: 1 email saying goodbye and asking for feedback.

Creating emails

Scheduled digest

Product updates

Send to new subscribers again

SaaS customer lifecycle emails