How it works
A producer emits an event when something happens. Consumers subscribe and act on it: send a receipt, update stock, post revenue. Events travel by webhook, message queue or stream. The pattern reduces latency and wasted calls, but it requires handling duplicates and out-of-order delivery, usually with event ids, idempotent handlers and occasional reconciliation against the source.
Example
When an order is refunded on Shopify, an event triggers a stock adjustment in the ERP and a credit note in the ledger within a minute, without a nightly batch.
In integrations
Unify Int is designed to publish changes on the Unify Graph as signed webhooks with event ids and replay, so your product can react to events across every connected platform with one handler. Workflows can chain actions on those events. Events make products feel immediate, but they are not a replacement for periodic reconciliation. Pair event handling with scheduled checks so missed events are caught.