---
title: "Conditionally Remove Recipient Email from Recipient Row"
slug: "conditionally-remove-recipient-email-from-recipient-row"
status: "new"
updated: 2026-07-21T20:32:05Z
published: 2026-07-21T20:32:05Z
canonical: "knowledge.technolutions.net/conditionally-remove-recipient-email-from-recipient-row"
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.

# Conditionally Remove Recipient Email from Recipient Row

Use [Liquid markup](/v1/docs/getting-started-with-liquid-markup) in a Deliver [recipient](/v1/docs/adding-a-recipient-list) row when a recurring internal mailing should send only to recipients who have relevant query results. This can be useful for staff notifications such as reader assignment reminders, unassigned Inbox message reminders, or upcoming event reminders.

The recipient list query still returns one row per potential recipient. Liquid markup determines whether the recipient email value is output for that row.

> [!TIP]
> ⭐ Get Inspired
> 
> This article was adapted from [a post by Technolutions staff](https://community.technolutions.net/get-inspired/post/conditionally-removing-recipient-email-from-recipient-row-using-liquid-eETBYiT57G2zqSt) 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)!

## Before you begin

- Create the Deliver recipient list query that returns the users or people who might receive the mailing.
- Add a dictionary subquery export that returns the related rows you want to test, such as assigned applications or open Inbox messages.
- Give the dictionary export a computer-friendly name. The examples below use `user_assigned`.
- Export the recipient email address. The examples below use `user_email`.

## Configure the recipient row

1. Open the Deliver mailing.
2. Open the recipient list settings.
3. In the recipient row, replace the plain email merge field with Liquid markup that outputs the email address only when the dictionary export contains at least one item.

```plaintext
{% if user_assigned.size != 0 %}{{user_email}}{% endif %}
```

When `user_assigned` contains rows, the mailing receives the value of `user_email`. When `user_assigned` contains no rows, the recipient row outputs nothing and the mailing does not send to that user.

> [!WARNING]
> 📝 Note
> 
> Replace `user_assigned` and `user_email` with the exact export names in your recipient list query.

## How the size filter works

The `size` filter returns the number of characters in a string or the number of items in an array. Dictionary subquery exports return an array, so `.size` can tell Liquid markup whether that export returned any rows for the current recipient.

For example, this expression returns the number of characters in a string:

```plaintext
{{ "Hello Slate Community Forums!" | size }}
```

This expression returns the number of rows in a dictionary export:

```plaintext
{{ user_assigned.size }}
```

## Test the mailing

1. Preview the recipient list query with users who should and should not receive the mailing.
2. Confirm that the dictionary export returns rows only for users who need the message.
3. Send a test mailing to confirm that recipient rows without related results do not receive the message.

## Related articles

- [The For Tag and Liquid Looping](https://knowledge.technolutions.net/docs/en/liquid-markup-looping)
- [Liquid Markup Filters](https://knowledge.technolutions.net/docs/en/liquid-markup-filters)
- [Subquery Exports & Outputs](https://knowledge.technolutions.net/docs/en/subquery-exports-outputs)
- [Recipient Lists](https://knowledge.technolutions.net/docs/en/adding-a-recipient-list)