Currently, the conditions engine is pretty basic. It can only perform checks on the original received event, and it can only work on strings in the record. The benefits is that it's fast and it allow the jetstream subscriptions to be quickly and efficiently filtered it. From a technical point of view, we want to keep this first layer of filtering. But we want to add more complex conditions for each steps of a workflow. - After a data source fetch - After an actions ran For the users, it has to remain simple, while the conditions could handle complex scenarios, the users should see simple interactions for example: - don't check that a request status is 200 or 404, but simplified sugar-syntax for "exist", "doesn't exist", "success", etc. We could eventually rely on https://jsonlogic.com/, while abstracting most of the complexit