Except for "updates", all of the outgoing webhooks include in their payloads enough information to fully understand the change: what was the state, and what's the state .

This information is essential to make useful automations and integrations using Favro's webhooks.

This information is completely absent for the "Card updated" event, which is a particularly large problem because that's the one event where we literally can't know which changed without that information.

For example, if this event triggers because a user was assigned to a card, I have that it was this assignment that caused the event. All I know is that the user is assigned, but I can't infer that they previously assigned. In short, card-update triggers cannot be used for any meaningful purpose.

This is a business-impacting missing feature, since it severely limits our ability to integrate Favro with our internal tools and other 3rd party services.