Current behavior: Outbound webhooks support two event types — workflow-completed and job-completed. When subscribing to job-completed, the webhook fires for every job in a workflow with no way to filter by job name. This is the same behavior on the workflow level.

Requested: Add a job and workflow name filter when configuring a webhook, so teams can subscribe only to specific jobs and workflows (e.g., deploy, publish) rather than receiving every job-completed or workflow-completed event across all jobs/workflows. The job.name and workflow.name field are already present in the payload, so this would be a configuration-side filter.

Use case: Teams with multiple workflows and jobs want targeted notifications/integrations for specific jobs & workflows (e.g., only trigger a downstream action when the deploy job completes) without building their own filtering logic on the receiving end.