oh That would not be as I expected it either then.
Use Case Scenario, I want to run a spellcheck webhook every time a new post is added. A new post can be added when adding a new tag, new category, new user, new comment, etc. So I have to then create the same webhook for every single parent object and look for deeply nested data and run the correct webhook. That is not what I was expecting this does. I (and at least another user) expected that this ran the webhook for whenever that data is added.
But, I guess that makes sense, the webhook is tied directly to the generated mutation (lambdaOnMutate), not the type as it appears in the schema. Just more extra steps to get what we need then.
The main problem here is schema scale. I setup up webhooks and then scale my schema adding more types that can create new posts as their children and forget to add the webhooks for those mutations watching for children and running my existing webhooks, then it easily becomes something that I just don’t do. I hope this can be expanded to cover the use case presented to run everytime the type is added not just the add mutation is ran for that specific type that has the webhook.