Adam Coster
When automations are created via the UI, using an outbound webhook as the consequence, the payload contains no information about what changed.
The absence of this information dramatically limits the utility of this feature, since we can't infer what exactly changed.
We can only infer the
type
of change based on how the automation was set up to be triggered in the UI -- even that piece of information is not in the webhook payload.
In addition to making it impossible to set up most kinds of useful integrations with internal and other 3rd party services, we also can't efficiently centralize webhook processing (e.g. using the same webhook target for multiple automations) because we have to separate them by trigger in order to infer
anything
about the change that occurred.
This is a significant and business-impacting missing feature.
September 30, 2021