We use Railway project webhooks to send critical deployment and infrastructure alerts to Slack. The current project-level configuration is too broad for this use case.

We would like each webhook to support:

1. Environment filtering

   • Include/exclude specific environments
   • Example: send production events but ignore staging

2. Service filtering

   • Include/exclude selected services within the project

3. Actor metadata

   • Include who initiated the action when available
   • Ideally include user ID/name and source, such as dashboard, GitHub, API, or automation

Currently, environment and service filtering require us to operate a proxy that receives every event, filters the payload, and forwards selected events to Slack. This adds unnecessary infrastructure, another secret-handling boundary, and another failure point solely for notification routing.

This would make Railway’s direct Slack webhook integration practical for projects with multiple environments and many services.