Myndbend™ Process Manager processes a lot of data in the background, to make sure that we keep every part of your workflow exactly where it should be. Each time approver approves, child ticket gets solved or updated, data gets synced from parent to a child (or vice-versa) - Our app ensures that the data is set how it should be - tags our app manages are set correctly, comments and the data is synced according to your settings, etc.
In order to do some of these actions, our app needs to be notified by Zendesk that there was an update on the ticket that has a workflow that our app manages. That is where our processing trigger steps into play!
The "processing trigger" is created by Myndbend Process Manager during the initial setup process (it can also be created manually from the Webhook page). It is created in a way so that it triggers on each ticket update if there our app was used on that ticket (so don't worry if you see that the trigger is fired frequently!).
It acts as a notification for our server to take a look at the ticket that was updated to make sure that all of the data, tags and comments related to our app are set just like they should be - So, in a way, trigger just pings our app to say "Take a look at this ticket".
Unless discussed with the Myndbend team, conditions (nor the message) of the trigger shouldn't be updated, as faulty conditions (or trigger being inactive) could result in parts of our app not working as expected.