Webhooks
Prov1.0.0Webhook endpoints, delivery health over 24 hours, retries and a payload inspector.
Build for your project
Code/install build
Usage
Import it and pass your content. The props that matter most are listed next.
Example
import { Webhooks, type WebhookEndpoint } from "@/components/ui/notchset/blocks/webhooks";
export function WebhookSettings({ endpoints }: { endpoints: WebhookEndpoint[] }) {
return (
<Webhooks
endpoints={endpoints}
onRetry={async (endpoint, delivery) => {
const r = await fetch(`/api/webhooks/${endpoint.id}/deliveries/${delivery.id}/retry`, { method: "POST" });
if (!r.ok) throw new Error("retry failed");
return r.json();
}}
onSendTest={(endpoint) => fetch(`/api/webhooks/${endpoint.id}/test`, { method: "POST" })}
/>
);
}Props
endpoints–{ id, name, url, events, secretSuffix, apiVersion?, total, buckets, deliveries }[]buckets are 48 half-hour counts, oldest first. Only the secret's last four characters reach the client.
deliveries[]–{ id, event, status, duration, time, attempt, response, payload, headers, bucket? }status ≥ 400 counts as failing; bucket places a failure on the chart so a fixed retry clears it there.
onRetry–(endpoint, delivery) => Promise<delivery>Re-send; resolve with the new state (a 2xx clears the failure everywhere), reject to keep it failed.
onSendTest–(endpoint) => PromiseAdds SEND TEST EVENT; resolving adds one to the 24-hour count.
retryNote–stringThe note after the counts (default RETRIES FOR 3 DAYS).
Anatomy
- Failing counts, rates and failed bars are worked out from the deliveries you pass.
- A retry's result replaces the delivery locally until your data refreshes.
- The inspector copies whichever tab is open.
Webhooksdata-slot="webhooks"Endpoints, the 24-hour chart, deliveries and the inspector.
Source
components/ui/notchset/blocks/webhooks.tsx
This component is included with Pro.
Try the live preview above. Get Pro to install the source.
Build for your project
Code/install build
Installation
pnpm dlx shadcn@latest add @beautiful-ui-pro/webhooksNeeds your registry key. Your components.json style picks the Base UI or Radix build: radix-*, new-york and default get Radix, base-* gets Base UI.
Styles didn't apply?
The CLI adds the styles to the CSS file named in components.json (tailwind.css). Check that it points at your global stylesheet, that the project uses Tailwind CSS v4, and that the file is imported in your root layout. Installed by hand: paste styles.css into that file.
For coding agents
Give your coding assistant the Markdown guide instead of screenshots.
Use it for
- A developer settings page where customers manage webhook endpoints
- Debugging failed deliveries and retrying them
Use something else when
- An audit log of user actions: use a Data Table
- Real-time event streams: use a live log view
Mistakes to avoid
- Never send the full signing secret to the client: pass its last four characters
- Return the delivery's real new status from onRetry, so a retry that fails again stays failed
Agents find it by
- webhooks, webhook endpoints, delivery log, retry deliveries, event delivery, payload inspector, developer settings, Notchset
Where agents read it
- Guide for this component: https://beautiful-ui.dev/md/webhooks.md
- Every component, for tools without MCP: /llms.txt
- MCP server:
https://beautiful-ui.dev/api/mcp(setup)
Behaviour
Keyboard
- Enter / Space
- Select an endpoint (again: fold its deliveries)
- ↑ ↓
- Move through recent deliveries
- Tab
- RETRY, COPY and the tabs
Accessibility
- Endpoints and deliveries are listboxes; the DELIVERIES header is a button with aria-expanded, and folded content is inert
- RETRY buttons are named with the event and time; the failing count is announced as it changes
- PAYLOAD and HEADERS are tabs over a focusable, scrollable code panel; the chart has a text label with the totals
Motion
- Chart
- Bars settle in, 6ms apart; a fixed failure drains from its bar
- Retry
- The scanner, then the status box turns to 200 and the counts roll
- Deliveries
- Unroll in 420ms and fold in 280ms
- Endpoint
- A 3px bar grows on the selected row
Responsive
- Under 640px (container width) each endpoint stacks its name, events and rate; the deliveries and the inspector stack under 680px.
Performance
- 48 SVG bars and plain rows; nothing runs while idle.
Changelog
v1.0.0 · 2026-10-04
First release
Part of
Included with Pro
Pro is in early access.
