Webhook Responses: Documentation incorrect
Adam Coster
The official documentation for the Favro API and Webhooks show sample data for webhook responses that include fields for the type of action that triggered the event, the person responsible for that action, plus other event-specific data (e.g. from which widget a card was moved, for that event).
However, the only data sent by Favro Automations are the payloadId and card fields. So we can see the current data for the card that was impacted by the trigger, but we have no way to get information about what that trigger actually
was
.This
dramatically
reduces the usefulness of the outgoing-webhooks trigger in Favro Automations, since we can't base decisions on what exactly changed.I've confirmed this to be the case for Card Created, Card Moved, and Card Updated events. In all cases only the card data is sent.
I have not yet set up a webhook via the API to see if those webhooks yield different results.
See the relevant section of the docs at: https://favro.com/developer/#webhook-responses
Dovidas Baranauskas
open
When you trigger a webhook, it shows correct result in received payload.
Then it can be compared wit hour current API documentation. https://favro.com/developer/
Adam Coster
Dovidas Baranauskas: To clarify, Webhooks created via the Favro API and webhooks created via the Favro UI have different results. The API documentation is correct for API-created webhooks, and incorrect for UI-created webhooks, since UI-created webhooks do not include the essential information about
what
was changed.Dovidas Baranauskas
under review
Adam Coster
Adam Coster
UPDATE: Webhooks created via the API
do
include the data as documented.That makes this issue something between a bug report and feature request, since I would expect webhook data from the UI-created webhooks to be consistent with the webhook data sent from API-created webhooks.