Specify fields in taskUpdated Webhook
not on the roadmap
L
Lyn Finman
I am asking for “fields[]” to be added to the ‘Create Webhook’ call, so I could register for “events”: [“taskUpdated”], “fields”: [“ticketPhase”]. I would then receive alerts only when the “ticketPhase” on the task is changed, not when comments are posted, priority changes, other custom fields are changed, etc. Right now I have to parse all those alerts and discard the majority. That will be way too much traffic in our production environment, I fear.
Log In
Canny AI
Merged in a post:
Filter criteria in webhooks
John
Allow us to add additional filters for triggering subscription webhooks and additional fields to have returned. i.e.
POST api/v2/team/:teamId/webhook
{
"endpoint":"https://webhook.endpoint.com",
"statuses":["done","complete"],
"events":["taskUpdated"],
"fields":["status","description"]
}
Because the payload only contains the field that was changed, you need to retrieve the task to get the full context. This approach would allow fewer API calls to retrieve that additional data.
Brenno Vicario Nicolau
If I understood John correctly, and using his example, I really miss the functionality of specifying which taskUpdate I want to be notified. Allowing filters, like it is possible in Pipefy, would be amazing.
Sometimes I want to be notified only when a priority has changed, and it would still be better if I could pinpoint from and/or to a specific priority. The same logic applies to other fields, including custom fields.
B
Brian Shen
not on the roadmap