It would be great to see some love given to the webhook page

Contribute UX

AI-generated summary

The discussion focuses on improving the User Experience (UX) of the webhook management page, which is currently considered less polished than the API key page. jordan-violet highlights several inconsistencies and suggests enhancements, including a cleaner table layout with truncated URLs, adding a description field, displaying the creator, created date, and last triggered time, and standardizing edit buttons across both pages.

Later in the thread, putty revives the topic to request the ability to tag or label webhooks, noting that the current chronological ordering makes it difficult to group related webhooks without deleting and recreating them. Additionally, Richie proposes adding a column for “friendly names” to make identifying specific webhooks easier.

1

Currently, the API page looks like this:

image
image1903×414 28.1 KB

You get:

  • API Key (truncated of course)
  • Description
  • User who it can run as
  • Created Date
  • Last Used Date
  • Eyeball button to view/edit
  • Red X button to delete/remove

The webhook page looks a bit disheveled by comparison:

image
image1904×607 61.8 KB

You get:

  • Random one-sentence description at the top (probably not needed like the API page, honestly)
  • Latest status (nice)
  • URL (cool, but should be truncated and you can still copy the link if you need it)
  • Events subscribed to (nice)
  • Edit button to view/edit (should we be consistent on which button is used across both API and Webhook page here?

Nice to haves:

  • Cleaner table with truncated webhook URL
  • Description object
  • User it was created by
  • Created Date
  • Last triggered time
12 Likes
5

Forgive me for reviving this topic, but the intention is the same: could the webhook page get some TLC?

At the bare minimum, it would be great to be able to tag/label webhooks. The current order of the list is simply the order in which it was made, which is great if you think of every detail initially. If you add a new webhook later, it won’t be “grouped” with the others. The only workaround is to delete and recreate it. Not fun.

1 Like
6

It’d be really nice to have an extra column on https://example.com/admin/api/web_hooks that’d allow us to enter a “friendly name” for all our webhooks :slight_smile:

Screenshot 2026-10-27 at 13.47.35
Screenshot 2026-10-27 at 13.47.352816×770 209 KB

3 Likes