Get Email List (Connections) Query Filter Syntax

I am moving to the 365 integration activities and the original query strings I was using don’t work. The activity is UiPath.MicrosoftOffice365.Activities.Mail.GetEmailListConnections
It’s documented here

I am trying to work out the equivalent for the 365 integration but the documentation doesn’t even mention the Query Filter option that is available. I’ve seen one other post claiming that it uses the OData format, however attempting to use the syntax I found from Microsoft here doesn’t work.

What am I missing?

I have tried with a bunch of variations in and around the following:
“contains(subject, ‘Verification Passed’)'”
“subject LIKE ‘Verification Passed’”
“SQL=urn:schemas:httpmail:subject LIKE ‘%Verification Passed%’”


Edit (9-Feb-26): corrected incorrect link to documentation

Hi @matt.theisen

Pls try this might be work:
use Microsoft Graph OData filter syntax in Query Filter. Examples:
contains(subject,‘Verification Passed’)
startswith(subject,‘Verification’) and isRead eq false
subject eq ‘Verification Passed’
receivedDateTime ge 2025-12-01T00:00:00Z
from/emailAddress/address eq ‘noreply@contoso.com

Do not use LIKE, SQL, DASL, or wildcards. Query Filter = $filter; Search Query = $search for KQL. Dates must be ISO 8601 UTC.

If helpful, mark as solution. Happy automation with UiPath

@matt.theisen

refer this solution

Hi @matt.theisen

The Microsoft 365 activities use Microsoft Graph and OData syntax, not SQL or Exchange queries.

For example, to filter emails with a subject containing “Verification Passed,” use:

contains(subject,‘Verification Passed’)

  • From a sender: from/emailAddress/address eq ‘sender@company.com’
  • Received after a date: receivedDateTime ge 2026-01-01T00:00:00Z

Do not use LIKE or SQL=. Property names must match Graph API exactly, and contains() is case-sensitive. Test with simple filters first to ensure it returns results.

Hi all,

None of the solutions worked so I am wondering if this is a bug or if it is badly documented.

Most of the replies here seem to be referencing the wrong activity.

The free text field matched both subjects and content by checking if the passed in string is contained in either.

I have changed to the contains in subject search option (the Additional filters option configured for the subject contains filter). Unfortunately, this means I lose programmatic building of filters.

Thanks all