Power Automate SharePoint Trigger Conditions: Ready-to-Use Formulas for Text, Date & User Fields

Following up on my previous article, I’ve put together a comprehensive collection of trigger condition formulas for different SharePoint list column types – text, numbers, dates/times, user columns, and many others.
Power Automate Trigger Condition Formulas Cheat Sheet: Ready-to-Use Examples for Business Hours & Email Filtering
Here's a collection of Power Automate trigger condition formulas that I personally use frequently or get asked about oft...
ippu-biz.com
2025.06.01
スポンサーリンク

Prerequisites

For this demonstration, I’ll be using the following SharePoint list: SharePoint list structure showing various column types for testing trigger conditions
Testing with the “When an item is created” trigger: Power Automate When an item is created trigger configuration
While the “When an item is created or modified” trigger works for both item creation and editing: Power Automate When an item is created or modified trigger configuration
The “When an item is deleted” trigger won’t work with these conditions: Power Automate When an item is deleted trigger configuration
This is because the “When an item is deleted” trigger contains only minimal information, making it impossible to write conditions targeting specific columns.
* However, you can still create trigger conditions based on “deleted by” or “deletion time” information. Limited data available in When an item is deleted trigger showing only basic deletion information

Text Columns

Let’s start with text columns (single line of text and multiple lines of text). SharePoint list text columns showing single line and multiple line text fields for trigger condition examples
// Match
@equals(triggerOutputs()?['body/[ColumnName]'], 'String')
// Example: Start the flow if the "Title" column is "abc"
@equals(triggerOutputs()?['body/Title'], 'abc')

// Contains
// * Note: Since "contains" does not accept null, add a null check with "and"
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  contains(triggerOutputs()?['body/[ColumnName]'], 'String')
)
// Example: Start the flow if the "Title" column contains "abc"
@and(
  not(empty(triggerOutputs()?['body/Title'])),
  contains(triggerOutputs()?['body/Title'], 'abc')
)

// The same applies to multi-line text columns
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  contains(triggerOutputs()?['body/[ColumnName]'], 'String')
)
// Example: Start the flow if the "multipleText" column contains "def"
@and(
  not(empty(triggerOutputs()?['body/multipleText'])),
  contains(triggerOutputs()?['body/multipleText'], 'def')
)

Number Columns

Next, let’s look at number columns. SharePoint list number column examples showing numeric field configurations for trigger conditions
// Equal
@equals(triggerOutputs()?['body/[ColumnName]'], Value)
// Example: Trigger when the number column "num" is 3 or more
@equals(triggerOutputs()?['body/num'], 3)
// Wrap with not for inequality (in this case, it also works if the number column is empty (null))
@not(equals(triggerOutputs()?['body/num'], 3))

// Greater than or equal to
@greaterOrEquals(triggerOutputs()?['body/[ColumnName]'], Value)
// Example: Trigger when the number column "num" is 3 or more
@greaterOrEquals(triggerOutputs()?['body/num'], 3)

// Less than or equal to
@lessOrEquals(triggerOutputs()?['body/[ColumnName]'], Value)
// Example: Trigger when the number column "num" is 3 or less
@lessOrEquals(triggerOutputs()?['body/num'], 3)

Yes/No Columns

Yes/No columns: SharePoint list Yes/No column examples showing boolean field configurations for trigger conditions
// To trigger the flow when the value is "Yes"
@equals(triggerOutputs()?['body/[ColumnName]'], true)
// Example: Trigger only when the Yes/No column "bool" is true
@equals(triggerOutputs()?['body/bool'], true)

// To trigger the flow when the value is "No"
@equals(triggerOutputs()?['body/[ColumnName]'], false)

Choice Columns

// Trigger the flow when a specific choice is selected
@equals(triggerOutputs()?['body/[ColumnName]/Value'], 'Choice')
// Example: Trigger when the choice column "choices" is "Choice 1"
@equals(triggerOutputs()?['body/choices/Value'], 'Choice 1')

// To trigger for multiple choices, wrap with or
@or(
  equals(triggerOutputs()?['body/[ColumnName]/Value'], 'Choice 1'),
  equals(triggerOutputs()?['body/[ColumnName]/Value'], 'Choice 2')
)

// To trigger when a choice other than a specific one is selected, wrap with not
// * With the formula below, it also triggers when the choice column is empty (null)
@not(equals(triggerOutputs()?['body/[ColumnName]/Value'], 'Choice'))

Date and DateTime Columns

Next, let’s cover date and dateTime columns. SharePoint list date and datetime column examples showing various date field configurations for trigger conditions
* All examples in this section use Japan Standard Time (JST) for the condition formulas. Setting SharePoint to JST makes it easier to verify trigger condition behavior. SharePoint regional settings configuration showing timezone settings for Japan Standard Time

Date Only

For columns that don’t include time: SharePoint date-only column trigger condition examples showing formulas for date fields without time components
// On or after (use "@greater" for strictly after)
@greaterOrEquals(triggerOutputs()?['body/[ColumnName]'], 'Date (yyyy-MM-dd)')
// Example: Trigger the flow if the date column "date" is on or after 2025/1/1
@greaterOrEquals(triggerOutputs()?['body/date'], '2025-01-01')

// On or before (use "@less" for strictly before)
@lessOrEquals(triggerOutputs()?['body/[ColumnName]'], 'Date (yyyy-MM-dd)')
// Example: Trigger the flow if the date column "date" is on or before 2025/1/1
@lessOrEquals(triggerOutputs()?['body/date'], '2025-01-01')


// For a range, wrap with and (example: 2025/1/1 to 2025/1/31)
@and(
  greaterOrEquals(triggerOutputs()?['body/date'], '2025-01-01'),
  lessOrEquals(triggerOutputs()?['body/date'], '2025-01-31')
)

// For outside of a range, wrap with or (example: up to 2024/12/31, from 2025/2/1)
@or(
  lessOrEquals(triggerOutputs()?['body/date'], '2024-12-31'),
  greaterOrEquals(triggerOutputs()?['body/date'], '2025-02-01')
)

// Equal
@equals(triggerOutputs()?['body/[ColumnName]'], 'Date (yyyy-MM-dd)')
// Example: Trigger the flow if the date column "date" is 2025/1/1
@equals(triggerOutputs()?['body/date'], '2025-01-01')

Date and Time

For columns that include time: SharePoint datetime column trigger condition examples showing formulas for date fields with time components
// On or after (use "@greater" for strictly after), you can also use addHours to add +9 hours instead of convertTimeZone
// * Does not work if the date-time column is empty (Null)
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  greaterOrEquals(
    convertTimeZone(triggerOutputs()?['body/[ColumnName]'], 'UTC', 'Tokyo Standard Time', 's'),
    'DateTime (yyyy-MM-ddTHH:mm:ss)'
  )
)

// Example: Trigger the flow if the date-time column "dateTime" is on or after "2025/1/1 09:00" Japan time
@and(
  not(empty(triggerOutputs()?['body/dateTime'])),
  greaterOrEquals(
    convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 's'),
    '2025-01-01T09:00:00'
  )
)

// * The following does not work correctly
@greaterOrEquals(triggerOutputs()?['body/dateTime'], '2025-06-04T09:00:00+09:00')

// On or before (use "@less" for strictly before)
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  lessOrEquals(
    convertTimeZone(triggerOutputs()?['body/[ColumnName]'], 'UTC', 'Tokyo Standard Time', 's'),
    'DateTime (yyyy-MM-ddTHH:mm:ss)'
  )
)
// Example: Trigger the flow if the date-time column "dateTime" is on or before "2025/1/1 09:00" Japan time
@and(
  not(empty(triggerOutputs()?['body/dateTime'])),
  lessOrEquals(
    convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 's'),
    '2025-01-01T09:00:00'
  )
)

// For a range, wrap with and
// Example: When the column "dateTime" is between "2025/1/1 9:00" and "2025/1/31 18:00"
@and(
  not(empty(triggerOutputs()?['body/dateTime'])),
  greaterOrEquals(
    convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 's'),
    '2025-01-01T09:00:00'
  ),
  lessOrEquals(
    convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 's'),
    '2025-01-31T18:00:00'
  )
)

// For outside the range, wrap with or
// Example: When the column "dateTime" is before "2025/1/1 9:00" or after "2025/1/31 18:00"
@and(
  not(empty(triggerOutputs()?['body/dateTime'])),
  or(
    lessOrEquals(
      convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 's'),
      '2025-01-01T09:00:00'
    ),
    greaterOrEquals(
      convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 's'),
      '2025-01-31T18:00:00'
    )
  )
)

// Equal (rarely used)
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  equals(
    convertTimeZone(triggerOutputs()?['body/[ColumnName]'], 'UTC', 'Tokyo Standard Time', 's'),
    'DateTime (yyyy-MM-ddTHH:mm:ss)'
  )
)
// Example: Trigger the flow if the date-time column "dateTime" is exactly "2025/1/1 09:00" Japan time
@and(
  not(empty(triggerOutputs()?['body/dateTime'])),
  equals(
    convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 's'),
    '2025-01-01T09:00:00'
  )
)

Time Only

When you want to write trigger conditions for datetime columns that ignore the “date” portion and focus only on the time component.

// On or after (use "@greater" for strictly after)
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  greaterOrEquals(
    convertTimeZone(triggerOutputs()?['body/[ColumnName]'], 'UTC', 'Tokyo Standard Time', 'HH:mm:ss'),
    'Time (HH:mm:ss)'
  )
)
// Example: Trigger the flow if the date-time column "dateTime" is on or after "09:00" Japan time
@and(
  not(empty(triggerOutputs()?['body/dateTime'])),
  greaterOrEquals(
    convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 'HH:mm:ss'),
    '09:00:00'
  )
)

// On or before (use "@less" for strictly before)
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  lessOrEquals(
    convertTimeZone(triggerOutputs()?['body/[ColumnName]'], 'UTC', 'Tokyo Standard Time', 'HH:mm:ss'),
    'Time (HH:mm:ss)'
  )
)
// Example: Trigger the flow if the date-time column "dateTime" is on or before "09:00" Japan time
@and(
  not(empty(triggerOutputs()?['body/dateTime'])),
  lessOrEquals(
    convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 'HH:mm:ss'),
    '09:00:00'
  )
)

// For a time range, wrap with and
// Example: When the column "dateTime" is between "09:00" and "18:00" Japan time
@and(
  not(empty(triggerOutputs()?['body/dateTime'])),
  greaterOrEquals(
    convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 'HH:mm:ss'),
    '09:00:00'
  ),
  lessOrEquals(
    convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 'HH:mm:ss'),
    '18:00:00'
  )
)

// For outside the time range, wrap with or
// Example: When the column "dateTime" is before "09:00" or after "18:00" Japan time
@and(
  not(empty(triggerOutputs()?['body/dateTime'])),
  or(
    lessOrEquals(
      convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 'HH:mm:ss'),
      '09:00:00'
    ),
    greaterOrEquals(
      convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 'HH:mm:ss'),
      '18:00:00'
    )
  )
)

// Equal (rarely used)
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  equals(
    convertTimeZone(triggerOutputs()?['body/[ColumnName]'], 'UTC', 'Tokyo Standard Time', 'HH:mm:ss'),
    'Time (HH:mm:ss)'
  )
)
// Example: Trigger the flow if the date-time column "dateTime" is exactly "09:00" Japan time
@and(
  not(empty(triggerOutputs()?['body/dateTime'])),
  equals(
    convertTimeZone(triggerOutputs()?['body/dateTime'], 'UTC', 'Tokyo Standard Time', 'HH:mm:ss'),
    '09:00:00'
  )
)

User Columns

Finally, let’s look at user columns. SharePoint list user column examples showing person field configurations for trigger conditions
* Department and job title information can be configured in the admin center. Microsoft 365 admin center showing user profile settings for department and job title configuration
// DisplayName matches
// * Does not work if the user column is empty (null)
@equals(triggerOutputs()?['body/[ColumnName]']?['DisplayName'], 'User Name')
// Example: The DisplayName of the user column "user" is "John Smith"
@equals(triggerOutputs()?['body/user']?['DisplayName'], 'John Smith')

// DisplayName contains a specific string
// Since contains does not accept null, add a null check with and
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  contains(triggerOutputs()?['body/[ColumnName]']?['DisplayName'], 'Specific String')
)
// Example: Trigger the flow if the DisplayName of the user column "user" contains "John"
@and(
  not(empty(triggerOutputs()?['body/user'])),
  contains(triggerOutputs()?['body/user']?['DisplayName'], 'John')
)

// Email matches
@equals(triggerOutputs()?['body/[ColumnName]']?['Email'], 'Email Address')
// Example: Trigger the flow if the Email of the user column "user" is "TestUser@sample.com"
@equals(triggerOutputs()?['body/user']?['Email'], 'TestUser@sample.com')

// Email contains a specific string
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  contains(triggerOutputs()?['body/[ColumnName]']?['Email'], 'Specific String')
)
// Example: Trigger the flow if the Email of the user column "user" contains "TestUser"
@and(
  not(empty(triggerOutputs()?['body/user'])),
  contains(triggerOutputs()?['body/user']?['Email'], 'TestUser')
)

// Department matches
@equals(triggerOutputs()?['body/[ColumnName]']?['Department'], 'Department Name')
// Example: Trigger the flow if the Department of the user column "user" is "Sales Department Section 1"
@equals(triggerOutputs()?['body/user']?['Department'], 'Sales Department Section 1')

// Department contains a specific string
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  contains(triggerOutputs()?['body/[ColumnName]']?['Department'], 'Specific String')
)
// Example: Trigger the flow if the Department of the user column "user" contains "Sales Department"
@and(
  not(empty(triggerOutputs()?['body/user'])),
  contains(triggerOutputs()?['body/user']?['Department'], 'Sales Department')
)

// JobTitle matches
@equals(triggerOutputs()?['body/[ColumnName]']?['JobTitle'], 'Job Title')
// Example: Trigger the flow if the JobTitle of the user column "user" is "Manager"
@equals(triggerOutputs()?['body/user']?['JobTitle'], 'Manager')

// JobTitle contains a specific string
@and(
  not(empty(triggerOutputs()?['body/[ColumnName]'])),
  contains(triggerOutputs()?['body/[ColumnName]']?['JobTitle'], 'Specific String')
)
// Example: Trigger the flow if the JobTitle of the user column "user" contains "Manager"
@and(
  not(empty(triggerOutputs()?['body/user'])),
  contains(triggerOutputs()?['body/user']?['JobTitle'], 'Manager')
)

Related Articles

Power Automate Trigger Condition Formulas Cheat Sheet: Ready-to-Use Examples for Business Hours & Email Filtering
Here's a collection of Power Automate trigger condition formulas that I personally use frequently or get asked about oft...
ippu-biz.com
2025.06.01
How to Filter SharePoint Yes/No Columns in Power Automate with OData Filter Queries
I was asked how to filter a "Yes/No" column in SharePoint using the "Get items" action in Power Automate, so here are my...
ippu-biz.com
2025.05.13
A Deep Dive into Power Automate Excel Filter Queries: Filtering Greater Than, Less Than, and Removing Blank Rows
I discovered that the "greater than or equal to" (ge) and "less than or equal to" (le) operators cannot be used in Excel...
ippu-biz.com
2025.04.30
Power Automate: Advanced DateTime Filtering in SharePoint Lists - Complete Guide
This article continues from our previous guide about date-only filtering, focusing on DateTime columns (including time c...
ippu-biz.com
2025.02.12
Complete Guide to OData Operators in Power Automate: Filtering SharePoint List Items
When setting up filter queries in Power Automate's "Get Items" action, you need to specify them using OData filter query...
ippu-biz.com
2025.02.12

コメント

Copied title and URL