Automation trigger status from "Any" to "Any"
Jonathan Benton
There is no efficient way to trigger an automation on any work order status change.
Currently, “Any” can be selected in the “from” field, but the “to” field must be a specific status. As a result, triggering on any status transition requires creating separate automations for each possible status.
Requested enhancement: Allow “Any” to be selectable in both the “from” and “to” fields so a single automation can trigger on any status change.
Aleksei Mikhailov
Hi Jonathan, thanks for the detailed write-up! To help us better understand the need, could you share a bit more about your use case? Specifically, what automation(s) are you looking to trigger on any status change, and what should happen when they fire? Knowing the real-world workflow you're trying to build will help us prioritize this effectively.
Jonathan Benton
Aleksei Mikhailov We want to use certain work order status changes to trigger webhooks that update records in our database. If we want these webhoook triggers for, say, 20 work orders, the number of automations we'd have to create using the current process would equal 20 x [# of status values], which is impractical. Another example is project status. We want to know when a status changes, so we had to create one automation per status value.