Webhooks & event-driven integrations
Deploy reliable, idempotent webhooks and replayable domain events without losing audit context.
Feature profile
Primary engines
Event Bus + Transactional Outbox
Safety model
HMAC signing + idempotency + key rotation
Tenant artifacts
DomainEvent + WebhookSubscription + WebhookDeliveryLog
Problem
Operational events lose trust when delivery is best-effort.
Teams need reliable, auditable signals when work orders complete, inventory moves, or quality gates clear. Without delivery guarantees, downstream systems drift and operators lose confidence in the integration layer.
Operational impact
- Missed handoffs when webhook payloads fail silently
- Duplicate processing without idempotency guards
- Manual reconciliation across ERP, WMS, and customer portals
Engine
Event Bus + Transactional Outbox + Safety Guardrails
Events are persisted inside the same transaction as the operational change, then dispatched through signed webhooks and replayable delivery logs so integrations can trust every signal.
- Outbox persistence of DomainEvent records before publish
- HMAC signatures with secret rotation windows
- Replay endpoints and delivery logs for failed notifications
- Schema-stable payloads with dedupe keys for consumer idempotency
Engine promise
This engine anchors the feature with reusable operational logic, ensuring every workflow stays aligned with tenant-owned data models.
Workflow
How the workflow moves from signal to action.
Step 1
Emit a customer-facing domain event
Services write DomainEvent records with schema version, dedupe key, and tenant context.
Step 2
Persist to the outbox and enqueue delivery
Outbox processing queues webhook deliveries for subscribed event types.
Step 3
Deliver signed webhooks
WebhookService signs payloads, retries deliveries, and records response metadata.
Step 4
Monitor and replay
Integration teams review delivery logs and replay events to recover from downstream outages.
Data artifacts
Tenant-owned artifacts that power downstream systems.
Every workflow produces structured records that stay in the customer domain.
DomainEvent
Tenant-owned outbox events capturing event type, payload, schema version, and dedupe key.
WebhookSubscription
Customer-defined targets, filters, and secrets for event delivery.
WebhookDeliveryLog
Delivery attempts, response codes, and retry scheduling for each webhook.
API preview
The endpoints teams integrate first.
The API surface remains consistent across industries, with schema-stable event hooks.
/api/v1/portal/webhooks/subscribe Create a webhook subscription for a customer event type.
/api/v1/portal/webhooks/{subscription_id}/rotate-secret Rotate HMAC secrets with a zero-downtime window.
/api/v1/integrations/events List customer-facing domain events from the outbox.
/api/v1/integrations/events/{event_id}/replay Replay a webhook delivery for a specific event.
/api/v1/integrations/webhooks Review webhook delivery logs with pagination.
/api/v1/webhooks/stream Open a real-time WebSocket stream of customer-facing events.
Cross-industry examples
One engine, many instantiations.
The same operational logic adapts across manufacturing, healthcare, logistics, and regulated industries.
Manufacturing
Work order completions trigger ERP billing and downstream scheduling updates.
Logistics
Inventory moves stream into a TMS for instant shipment status updates.
Healthcare
QC gate results post to LIMS systems with audit-ready evidence.
Fintech
Payment confirmations and settlement events sync to customer portals.
Retail
Fulfillment milestones update commerce platforms without polling.
Energy
Inspection and compliance events trigger partner acknowledgements.
Embedded operations
Manufacturing status, inspection results, and compliance signals stream to platform customers embedding ops capabilities.
FAQ
Answers for security, data, and rollout teams.
What delivery guarantees do webhooks provide?
Events are delivered at least once with delivery logs and replay support. Consumers should use dedupe keys for idempotency.
How are webhook payloads secured?
WebhookService signs each payload with HMAC, and secrets can be rotated with a dual-signing window.
Can we replay missed events?
Yes. Event replay endpoints enqueue a new delivery log so downstream systems can recover after outages.
Are events tenant-owned?
Yes. DomainEvent records and delivery logs live in tenant data stores for audit and export workflows.
Explore more