---
title: "Recurring Staff Notifications for Outgoing Messages"
slug: "recurring-staff-notifications-for-outgoing-messages"
status: "new"
updated: 2026-07-21T20:30:04Z
published: 2026-07-21T20:30:04Z
canonical: "knowledge.technolutions.net/recurring-staff-notifications-for-outgoing-messages"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Recurring Staff Notifications for Outgoing Messages

This article shows you how to create a recurring Deliver mailing that notifies staff about upcoming outgoing mailings. This approach uses a user-based recipient list query, an independent subquery export with a dictionary output, and Liquid markup to list the upcoming mailings in the message body.

This example is useful when staff need a weekly view of communications scheduled to go out from Slate.

> [!TIP]
> ⭐ Get Inspired
> 
> This article was adapted from [a post by Technolutions staff](https://community.technolutions.net/get-inspired/post/weekly-deliver-mailing-to-staff-notifying-them-about-outgoing-mailings-vLFjWGxhi4TKkvs) in the Slate Community Forums' Get Inspired space. Have a great idea for a Get Inspired post? [Let us know](https://community.technolutions.net/get-inspired/new?post_type=gnHx7As1gZ8r6Ld)!

## Build the recipient list query

1. Create a recipient list query with a **User** base. This returns one row per staff user who should receive the notification.
2. Add an **Independent Subquery Export**.
3. Set the independent subquery export base to **Message Mailing**.
4. Set the output to **Dictionary**.
5. Add exports for the mailing details you want to include in the staff notification.

Useful exports include start date, status, name, subject, URL, and username.

![Recipient list query with an independent subquery export for upcoming message mailings](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/01-8AoY2SUzP3xamosf1p38R.webp)

![Dictionary export configuration for upcoming message mailing details](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/02-jjxu1zyl3a9MTtz70bqxJ.webp)

> [!WARNING]
> 📝 Note
> 
> Use computer-friendly export names because Liquid markup references those names in the Deliver mailing. Keep names lowercase and avoid spaces.

📖 [Subquery Exports & Outputs](https://knowledge.technolutions.net/docs/en/subquery-exports-outputs)

## Add Liquid markup to the mailing

In the Deliver mailing body, use a Liquid `for` loop to display each row in the dictionary export. In this example, the dictionary export is named `upcomingmailings`.

```xml
{% for mailing in upcomingmailings %}
<ul>
  <li>
    {{mailing.username}} is sending this mailing: {{mailing.start | date: "dddd MM/d/yyyy"}} - <a href="{{mailing.url}}">{{mailing.name}}</a>
  </li>
</ul>
{% endfor %}
```

You can also add a summary sentence that counts the number of mailings and the number of unique users sending them.

```Liquid
{% assign mail = upcomingmailings | map: "username" | uniq %}There are {{upcomingmailings.size}} emails going out this week from {{mail.size}} users.
```

The `assign` tag creates a new variable called `mail`. The `map` filter extracts the username values from the `upcomingmailings` dictionary export, and `uniq` counts each username once.

![Deliver mailing body using Liquid markup to summarize upcoming outgoing mailings](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/03-KyhEo6jGHMqGHn2U1nN1E.webp)

📖 [The For Tag and Liquid Looping](https://knowledge.technolutions.net/docs/en/liquid-markup-looping)

## Schedule the mailing

1. Schedule the Deliver mailing to run on the cadence staff need, such as once per week.
2. Review the recipient list query filters so the dictionary export only returns the mailings that should appear in that notification window.
3. Set **Deduping Settings** to **Allow Recurring Delivery of this Message to the Same Recipient**.

> [!WARNING]
> 📝 Note
> 
> If recurring delivery is not allowed, staff may stop receiving the recurring notification after the first delivery.