# Can't edit existing webhooks and create new ones

**URL:** https://forum.youcanbook.me/t/cant-edit-existing-webhooks-and-create-new-ones/4216
**Category:** Notifications
**Created:** [July 22, 2025, 10:46am UTC](https://forum.youcanbook.me/t/cant-edit-existing-webhooks-and-create-new-ones/4216 "2025-07-22T10:46:30Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![39elbarto](https://avatars.discourse-cdn.com/v4/letter/3/e95f7d/32.png) [@39elbarto](https://forum.youcanbook.me/u/39elbarto)
#### Post date: [July 22, 2025, 10:46am UTC](https://forum.youcanbook.me/t/cant-edit-existing-webhooks-and-create-new-ones/4216/1 "2025-07-22T10:46:30Z")

</div>

Hello everybody! Few months I’ve configured webhooks in notifications. Everything works perfect and my automations run smoothly. But yesterday I wanted to edit them a bit and can’t go inside any existing webhook and can’t create a new one either. Every time I try to do this , I receive an error , as on the screenshot. I’ve checked from chrome and opera browsers: the same. I’ve created a ticket, but didn’t receive any reply.  
Does anybody know about such issue and is there any way to fix from my side?  
Thank you!

 ![image](https://canada1.discourse-cdn.com/flex027/uploads/ycbm/original/2X/3/339e15a01de7e7920d75c260db79c153a6f2b3f5.png)

---

<div class="post-metadata">

### Author: ![39elbarto](https://avatars.discourse-cdn.com/v4/letter/3/e95f7d/32.png) [@39elbarto](https://forum.youcanbook.me/u/39elbarto)
#### Post date: [July 23, 2025, 12:44pm UTC](https://forum.youcanbook.me/t/cant-edit-existing-webhooks-and-create-new-ones/4216/2 "2025-07-23T12:44:12Z")

</div>

Fixed by developers after 2 days, when I saw it first time.

---

<div class="post-metadata">

### Author: ![Ben](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.youcanbook.me/ben/32/772_2.png) [@Ben](https://forum.youcanbook.me/u/Ben)
#### Post date: [July 28, 2025, 4:03pm UTC](https://forum.youcanbook.me/t/cant-edit-existing-webhooks-and-create-new-ones/4216/3 "2025-07-28T16:03:25Z")

</div>

@39elbarto yes this should be fixed now. Sorry for any frustration. Let us know if you are hitting any other snags.