Reliable Public Webhook Ingress
Turn a public webhook into a bounded interface with validation, authentication, stable responses and retry-safe side effects.
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
An ingress flow that is easier to secure, test and recover when upstream callers retry or send malformed data.
Define the request schema.
Know whether the provider supports signatures/authentication.
Define idempotency for side effects.
Validate at the edge
Reject malformed input before expensive workflow work.
Verify authenticity when supported
Use the provider signing method rather than trusting source IP or obscurity.
Design retry-safe writes
Duplicate delivery must not multiply business side effects.
Return a stable response envelope
Keep the caller contract independent from internal workflow shape.
Keep a triage path
Use the webhook runbook and capture failures as regression cases.
Turn the Recipe into checkable work.
Progress, notes and history stay in this browser.