WebhookCore

WebhookCore is a reusable outbound webhook delivery subsystem for SaaS integrations, with explicit endpoint governance, signing, attempts, retries, and replay.

What is in the repository

• 8 workspace packages
• 2 runtime applications
• 1 runnable example integrations

Why teams adopt QueueFlow

• you want outbound webhooks to behave like a real subsystem, not helper code around fetch
• you need attempts, retries, and replay to stay visible and auditable
• you want secret rotation and endpoint governance behind a stable API
• you want retry orchestration to compose cleanly with QueueFlow and the rest of the Saazip stack

Start here

• Quick start
• Architecture
• Adoption paths
• Operate WebhookCore
• Maturity and scope
• Package reference
• Runtime reference
• Examples

How the pieces fit together

your app or service
  -> @saazip/webhook-core
  -> webhook-core api
     -> contracts + core + crypto + db + observability
     -> endpoint and delivery truth
  -> webhook-core dispatcher
     -> adapters-queueflow for retries and replay work

What QueueFlow owns

• endpoint lifecycle, secret versions, delivery attempts, and replay behavior
• the API surface for registration, delivery creation, listing, and replay
• the delivery domain model and signing primitives
• the operational seam for QueueFlow-backed retry orchestration

What your app still owns

• which domain events become outbound webhooks
• subscription semantics, product authorization, and payload design
• how delivery ownership fits inside the rest of your product platform

Current maturity

• already useful as a service-first outbound delivery subsystem
• best for teams who want explicit replay and delivery-state visibility
• still opinionated toward outbound delivery, not inbound gateway concerns

Source repository: saazip/webhook-core