Event-triggered workflows
Smithers used to run only when you told it to. Now the outside world runs it for you. A signed webhook fires a durable, replayable workflow, on its schedule, not yours.
Why this exists
Triage this issue, review this PR, respond to this event. It all lands on someone else's schedule, and you are asleep, in a meeting, or heads down on something else. Smithers had no way to hear it happen.
How it works
Drop <OnWebhook> into a workflow and point it at a GitHub event. The integrations package handles the ingress.
Every delivery has its signature checked and its cursor tracked, so a replayed or forged event never runs twice.
The event kicks off a real Smithers run: checkpointed, retryable, and fully replayable after the fact.
What you get
A ready GitHub webhook source and an <OnWebhook> trigger. Any signed webhook is next.
Deliveries are authenticated at the door. A spoofed payload does not get a run.
Delivery and cursor state are persisted, so retries and replays never double-fire your workflow.
The run an event caused is durable and replayable. Rewind it, inspect it, or fork from any step.
Add the integrations package, subscribe to an event, and never babysit a trigger again.