About this block

Webhook Events Table puts the complete event reference on the marketing page, seven rows, each with the mono event name, a plain sentence about when it fires, and the payload size. The surrounding copy carries the operational promises that matter, signing, retries with backoff, and replay from the dashboard.

A small events list drives the table, and the claim that seven events cover everything is itself the pitch, a finite surface reads as a designed one.

When to use

Reach for this block on developer pages where event driven integration is the main consumption pattern. It pairs naturally with the webhook tail terminal and gives the status page delivery promises something concrete to refer to.

A natural flow around it on a Marketing Pro page:

Before

• Quickstart showing the request side before the event side

After

• Rate limits and the rest of the operational contract
• Trust for the signing and retention details

What you can display

One strong use is your real event catalog with honest payload sizes. Other tables:

• Audit events. What lands in the audit log and when.
• Job statuses. The states an import or export moves through.
• Notification types. Everything that can ping a user.

Tip: small payload sizes are a feature, publish them, nobody wants a 40 kb webhook.