<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=533953) </details> <!--IssueSummary end--> ### Proposal - A customer raised a support ticket to enquire how to exclude a field from a webhook payload ([Customer ticket, internal-only](https://gitlab.zendesk.com/agent/tickets/616492)) - This is technically possible via [custom webhook templates](https://docs.gitlab.com/user/project/integrations/webhooks/#custom-webhook-template), _however_ it would mean reconstructing the rest of the usual webhook payload structure - This would be tedious as there are many attributes on a webhook payload, [for example a pipeline event webhook payload has 200+ attributes](https://docs.gitlab.com/user/project/integrations/webhook_events/#pipeline-events) - To make excluding specific attributes more straightforward and practical the customer linked above requested that we consider implementing a function to exclude specific attributes inside GitLab - this function could appear in the interface in the same area as the custom webhook template fields