Webhook Logs Table
Webhook delivery log with event name, endpoint, HTTP status badge, duration, attempt ratio, and inline response body for failed rows.
Webhook delivery log with event name, endpoint, HTTP status badge, duration, attempt ratio, and inline response body for failed rows.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Webhook Logs Table is the delivery audit surface, six rows showing timestamp, event name in monospace, endpoint, HTTP status Badge, duration, and an attempt ratio. The failed project.deleted delivery sits expanded with its full response body, a JSON object whose message field says upstream timeout, plus a Retry now button and the note that Attempt 3 of 3 has been marked dead.
Logs are one typed array with responseBody and expanded on every entry so TS never widens the union. The expanded inline body is the feature that saves a context-switch to curl; the delivery story is complete without leaving the page.
Reach for this block on the developer or integrations settings page, wired to your webhook delivery endpoint and filtered to the active workspace. Pair the Retry now button with a POST to your delivery retry route.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the webhook delivery log. Other tables:
Tip: the footer retry policy note, 5 min, 30 min, 2 h, 8 h, 24 h, is what stops the where did my event go support ticket; put it in the block, not just the docs.