For me personally, webhooks work quite good already, although if i were to add something it would certainly be making more events be able to trigger em, like maybe the creation of services, or maybe even have something like custom rules for when to send webhooks!

I've seen Luna ask for a webhook to fire when environments are created (PR, Forked, etc)

I would love to see webhooks on a per-service or per project level. That way I can direct each webhook to a different location if I wanted. Or give me the ability to add multiple webhook endpoints, with a selection of the ones I created on each individual service. Kind of make it a setting, when creating them, instead of turning on the feature globally.

On the service or project, I would like to select from multiple created webhooks to send notifications to multiple locations. For example, Discord AND Slack, or Discord and a Dashboard.

But then again, this is just my $0.02 do with it what you please.

Okay, so it's been a while since I've used webhooks… Not project level, because they already are… Give me service level, where I can configure what events will trigger it! There we go… Fixed my response since no edit button yet! :D

Webhooks can't be triggered by deployments inside PR environments, correct? At least right now, only my "permanent" environments trigger web hooks, not my "ephemeral" PR environments. Anyone else?

That's correct, PR envs won't trigger any webhooks.

Thanks for a swift confirmation @brody
Is there any way we can get PR envs to trigger webhooks? A feature flag or beta enrollment?
It's the missing piece for our deployment pipeline...

Some history here, at first we did do webhooks for services in PR environments, but our users asked us not to because they were often too noisy, so we have disabled them for PR envs.

And I think that is a good compromise given we have no controls around webhooks besides on or off.

We know our webhook story could be much better, hence the thread, and you can see that the main ask here is for more control, so hopefully controls for enabling PR webhooks and everything under that will be picked up in Q1 planning.

In the meantime, counter question, what are you needing webhooks for PR environments for?

I appreciate the backstory, makes sense where you come from. Although I will say, it's easier to just filter out unwanted webhook events, than to not be able to receive them at all

We use PR envs for E2E testing (like most teams). We create isolated database instances for every PR env, and hence need to (1) listen for new PR envs, (2) spin up ephemeral DB instance and (3) redirect Railway env variables to that instance.

For now, we'll resort to GH webhooks. As FYI, GitHub web hooks config panel offers "send me everything" versus selecting specific events. Tbh, even a "get web hooks for PR envs" toggle would help.

Ultimately, we first wanted to just do web hooks in Railway because we perceive that "everything is easier in Railway than in GitHub or X other infra provider".