Choose which events each webhook receives

Description: Today a webhook is a single global subscription: you add a URL and it receives every event your workspace produces — new posts, comments, votes, subscriptions, users, changelog entries, survey and satisfaction responses. There is no way to say "only tell me when a post is created". This request is to make each webhook event-scoped. When you add or edit a webhook you pick the events it should receive from a list (post created, post updated, comment created, changelog published, and so on), and only those events are delivered to that URL. Purpose: Let each endpoint receive exactly the events it was built to handle, instead of every endpoint receiving everything and filtering on your side. Benefits: Far less traffic to your endpoint — a Slack notifier for new posts stops receiving every single vote No filtering logic to write and maintain on your side Separate URLs for separate jobs, each with its own event list Easier to debug: when something arrives, it is something you asked for Key Features: Per-webhook event selection when creating or editing a webhook A published catalogue of every available event, so you always know what you can subscribe to Signed deliveries, so your endpoint can verify a request genuinely came from Sleekplan Automatic retries with backoff when your endpoint is temporarily unavailable A delivery log in the dashboard showing what was sent, when, and what your endpoint replied