Power Automate Trigger Conditions

[Nor644]

Hi all, 

I'm Building a flow when an item is created or modified trigger. but it'll end up infinite loop. 

I have solved by using this condition. @not(equals(triggerOutputs()?['body/Editor/Email'], 'myemail')). it worked just find. 

but i want to add another condition which says if "payment_status" column is equal to "Paid" do not trigger the flow. so if the finance team edits list and change status to paid. the flow has to stop and not run again. 

I couldn't combine the NOT & AND. 

I would high request two solutions. 

1. how to include multiple emails @not(equals(triggerOutputs()?['body/Editor/Email'], 'myemail'))

2. how to include not equal email condition and also column choice condition. 

[v-chengfen-msft]

Hi @Nor644 ,

Please try adding another condition.
The flow will only trigger when both conditions return True

Best Regards

Cheng Feng

[Nor644]

Hi thanks for support, 

that's what i'm missing, i couldn't figure out the correct syntax for the second condition. 

Column = "Payment_status" 

Value = "Paid" 

is this a correct condition. 

@not(equals(triggerOutputs()?['body/Payment_Status/value'], 'Paid')). I want the flow to NOT triger is payment status is paid. 

[Nor644]

@v-chengfen-msft 

[VictorIvanidze · Accepted solution]

The this combined condition:

@And(not(equals(triggerOutputs()?['body/Editor/Email'], 'myemail')),not(equals(triggerOutputs()?['body/Payment_Status/value'], 'Paid')))

[v-chengfen-msft · Accepted solution]

Hi @Nor644 ，

Please try:

Or

Here is a link about trigger condition for you reference:

Power Automate Trigger Conditions [33 Useful Examples] - SPGuides

Best Regards

Cheng Feng

[Nor644]

@v-chengfen-msft @VictorIvanidze 

Still same issue, flow trigger although i put all the conditions as you contributed. 

Scenario 1

• @not(equals(triggerOutputs()?['body/Payment_Status/value'], 'Paid'))
• @not(equals(triggerOutputs()?['body/Editor/Email'], 'myemail'))

the other option was and it still triggers. 

@And(not(equals(triggerOutputs()?['body/Editor/Email'], 'myemail')),not(equals(triggerOutputs()?['body/Payment_Status/value'], 'Paid')))

[VictorIvanidze]

Could you show the output of trigger?

[Nor644]

@VictorIvanidze  thanks for the support. 

regarding your question. i have not placed any output.  

[VictorIvanidze]

Remove the trigger conditions and run the trigger. Could you show all trigger parameters?

[Nor644]

@VictorIvanidze @v-chengfen-msft 

Finally, Alhamdullillah it worked.  instead of Payment_status i used only status. 

@not(equals(triggerOutputs()?['body/Status/value'], 'Paid'))

@not(equals(triggerOutputs()?['body/Editor/Email'], 'myemail'))

Thank you so much both, for the support, the two solutions worked and will close this post. 

[Rohith_Raghav]

Hi, 

Has anyone configured trigger conditions for the teams trigger "When a new chat message is added" ?

We are trying to create a rule which can avoid the messages posted by the flow bot.

Few articles suggests to us "@not(equals(triggerOutputs()?['body']?['from']?['application']?['applicationIdentityType'],'bot'))" but that doesn't work, since the triggerOuputs() JSON block doesn't have the actual message content.

Below is the array/json content of TriggerBody

{

  "value": [

    {

      "subscriptionId": "****",

      "changeType": "created",

      "clientState": "secretClientValue",

      "subscriptionExpirationDateTime": "*****",

      "resource": "chats('19:*****@thread.v2')/messages('****')",

      "resourceData": {

        "id": "***",

        "@odata.type": "#Microsoft.Graph.chatMessage",

        "@odata.id": "chats('19:****@thread.v2')/messages('***')"

      },

      "tenantId": "****",

      "conversationId": "19:****@thread.v2",

      "messageId": "***",

      "linkToMessage": "https://teams.microsoft.com/l/message/19:*****@thread.v2/*****?tenantId=****&context=%7B%22contextTy..."

    }

  ]

}

Is there a way to leverage "linkToMessage" value to access/get the actual connect of the message in trigger condition rules ?

[VictorIvanidze]

No way. Just don't use a trigger condition and filter later.