Webhook payload.

[Ocean West]

I can't fathom how any webhook would make any use of this even if I was sending webhooks to my own receiver. Seems like a lot of noise. 

 

[Marc]

Im not sure what the question is here or which webhook you are referring to. Please could you clarify? 

[Adriano Faria]

9 hours ago, Ocean West said:

Seems like a lot of noise. 

Almost 30 groups only in this image. You should have a lot of work to manage permissions in your board. The more groups you have, more “noise” it will make. 

[Daniel F]

I’m also not sure what the question is.

Any node will have the permissions as part of it‘s payload.

[Ocean West]

I keep going back to the verbosity of the payload throwing everything and the kitchen sink to whom ever you send a web hook to to / Zappier < insert > third party. There is a lot of trust that must be had with these services as there is way too much PII info in the payload that is not necessary for 99% of the bits needed for taking action on. I've queried this before but have not got adequate answer as to when we can restrict what bits get issued in the payload. 

[Daniel F]

18 minutes ago, Ocean West said:

I've queried this before but have not got adequate answer as to when we can restrict what bits get issued in the payload. 

As far as I remember we said that we won't change this in the 4.x lifetime.

By the way, not sure if you noticed this, but PII data are only included in the response when authorization happened with a generic API KEY.
If you use the REST API and GraphQL with oAuth authentication, all sensible data are stripped.

[Ocean West]

RestAPI and Graph QL with OAuth is for polling for data web hooks  trigger on events of an action can we setup web hooks with the same permissions? All web hooks are run with full access and kimono wide open.