Webhooks and CDC
Change data capture modes, managed webhook delivery history, and destination validation.
CDC configuration is managed from the database Cluster page, under the Change Data Capture tab. Delivery history is shown from the database Webhooks page.
Use this guide when you need downstream consumers to receive TigerBeetle changes through the CDC path.
CDC modes
The current CDC schema supports:
disableddirect_amqpmanaged_amqp
Direct AMQP stores TigerBeetle AMQP connection settings. Managed AMQP uses Parix-managed delivery and one or more webhook destinations.
Destination validation
Managed destinations must use HTTPS URLs. Authenticated destinations require a secret on first save. Static-header authentication also requires a header name. Managed CDC requires at least one active destination.
Delivery history
The Webhooks page shows managed CDC delivery history from durable storage. Filters include:
- range: 24 hours, 7 days, or 14 days
- status: all, success, or failed
- destination
The page paginates delivery history and links back to the CDC configuration page when Managed AMQP is not active.
Workflow behavior
CDC changes are queued. The browser request validates and records the desired configuration, then Parix enqueues the workflow that applies it to the provider-backed deployment.