Hello all, is creating a custom webhook supported on the local version of the server? It lets me create the webhook, but all the fields (e.g JSON data) are all disabled and so when the webhook is called none of the fields are passed.

hi @Jagi Natarajan - we do not yet support webhooks in OSS, though we'd like to add this soon!

is there an alternate approach to sending notifications that you can suggest and supported by the OSS version?

oh sorry I misunderstood your question yes, you can create automations in OSS that can be configured to have an action that sends a custom webhook

the trigger section in the screenshot most of the properties are disabled for us

so its • create a custom webhook block • create an automation ◦ set your trigger, ie when should this happen? ◦ set action, select this custom webhook

image.png

oh thats odd what version of the server do you have?

3.0

sorry, i meant which specific version

where can i find the specific version? i don't see it in the UI

prefect version

in the CLI will work or

pip list | grep prefect

Version: 3.0.4 API version: 0.8.4 Python version: 3.11.5 Git commit: c068d7e2 Built: Tue, Oct 1, 2024 11:54 AM OS/Arch: darwin/x86_64 Profile: local Server type: server Pydantic version: 2.9.2 (env) (base)

are you able to upgrade with

pip install -U prefect

? there were some issues with settings in 3.0.4 which I doubt are related, but its possible

yeah let me try

hrm. are you willing to open an issue? the greyed out fields are confusing to me and something seems off about that

i sure can, I will ask my team to deploy the latest version in our cluster, double check that this issue exists on the cluster as well and open an issue. Just to make sure its not something about the way i am running

thank you!

thanks for your time today Nate

just wanted to flag the same issue on 3.1.0, I was using it for Slack alerts so just resorted to using the Slack block but had the exact same issue as @Jagi Natarajan when trying to set up custom webhooks (also OSS)

@Nate I opened a bug #16056. Thanks