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

Contribute UX
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
10 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