Webhooks and events

Incoming webhooks let systems without a native integration start or update a run. A monitoring alert, an internal tool, a form submission, or a vendor callback can all carry their payload into a session as context.

The event arrives with the run, so the run starts knowing what caused it rather than having to go and look.

Conditions matter more than triggers

The trigger decides what can start work. The conditions decide what should. A webhook wired without conditions turns every event into a session, which is how a noisy source becomes an expensive one.

Trigger:     webhook from monitoring
Conditions:  severity >= high, service in [payments, auth],
             not a duplicate of an open investigation
Action:      update the persistent incident monitor
Limits:      20 invocations / hour
Owner:       on-call, notified on failure