Flow Triggers - Is Changed

In Spring ‘21 we finally have Is Changed in Flow Triggers… well sort of… it feels convoluted to set up but let’s compare it with Process Builder


  • Set a text field that the rate was changed.

  • Set a text field that the rate was not changed.

It’s a silly scenario but it’s good to show the setup because it covers both the true and false scenarios.

Process Builder

  • For a start, your Process Builder would NEVER look like this because we were told that the “best practice” is for one Process Builder per object, so these nodes would be one of about 50 in this humungous Process Builder that is so confusing to work out what its doing.

  • It’s easy to just choose Is Changed in the Operator… BUT you also have to check if it is not null.

  • The reverse scenarios are a pain to set up because it feels so repetitive to set up the criteria again. Easy for one field, but when I need to check if one of 20 rate fields have changed, then it’s not so easy.

  • Process Builders are so difficult to see what is happening, having to click into each node.

So overall it seems simple at first glance, but quickly turns into a nightmare. My Process Builders are a nightmare.


So overall I think the Is Changed in Flows is going to be much easier and nicer to work with.