WEBHOOK CHAOS: NORMALIZE STRIPE + TWILIO + GITHUB IN ONE PLACE
Stripe sends payment_intent.succeeded with a nested data.object. Twilio sends CallStatus=completed as form-encoded. GitHub sends a push event with a ref field. Three providers, three payload shapes, three retry policies, three signature verification schemes. Every service your product integrates adds another bespoke webhook handler.
THE NORMALIZATION PROBLEM
Business logic shouldn't know which provider fired an event. It should receive a standard shape: what happened, who it happened to, when, and the raw payload if needed. That normalization is infrastructure work — yet most teams build it inline with product code.
[CURRENT REALITY]
Three webhook routes, three signature checks, three payload parsers, three retry handlers — before writing a single line of business logic.
HZRELAY EVENT SESSIONS
An event session accepts inbound webhooks from any configured provider, verifies signatures, normalizes the payload into a standard EventFrame, and fans it out to your configured sinks.