It would be especially helpful if we could have the ability to send an outbound request for further information to filter on. This is useful in situations, such as with ConnectWise's callbacks, where not all needed information is included in the initial event/trigger.

Situation:

---

We use ConnectWise events fairly often and currently cannot filter on custom fields because custom field data is not returned in the event body. This means we will have to perform at least one task before we can rule out a ticket as actually requiring automation.

If we're monitoring for ticket updates but only want to affect ones with certain custom fields, we need to field all updates; we can work around this with org variables + the limited filtering for companies, contacts, etc, but this is not ideal.

Proposed Solution:

---

Either allow for complex triggers where we can make one outbound call to retrieve "full context" that we can filter on.

OR

Only start counting task executions if 2 or more tasks have run in a flow (meaning if a single task runs, then the flow is cancelled; this is counted as a "filtered" run).