User Problem

Users who integrate Trello with their internal systems via the REST API need an efficient way to avoid processing webhook events triggered by their service accounts. Currently, webhook processing often runs unnecessarily, only to discard events originating from their own accounts. This creates inefficiencies, increases operational costs, and consumes unnecessary resources both for users and Trello.

Suggested Solutions

Introduce an option at the webhook level to exclude specific `memberIDs`. Users could specify which `memberIDs` they want to exclude when creating or updating a webhook. Actions initiated by these excluded `memberIDs` would not trigger the webhook at all. This would eliminate the need for users to filter these events manually, reducing unnecessary processing and improving overall system performance. The existing `X-Trello-Client-Identifier` header could still be supported for those who prefer the current approach.

Current Workarounds

None available.