What is a webhook?
A webhook is one system calling a URL of yours the moment something happens, instead of you asking repeatedly whether it has. It is how a payment, a form submission or an alert reaches your software within a second. The catch is that delivery is the sender's problem, so a missed call is usually silent.
They call you when it happens, instead of you asking every minute.
Why it matters to you
Two failure modes cause most webhook incidents, and both are cheap to handle if you know about them in advance.
The first is duplicates. Many senders retry when your endpoint is slow or returns the wrong status, so the same event can arrive twice. An endpoint that charges a card or sends a mail without checking whether it has already seen that event id will eventually do it twice.
The second is loss. If your endpoint is down when the sender calls, some senders retry for a while and some give up immediately, and either way nothing appears in your logs because the request never arrived. A system that only learns about events through webhooks needs a periodic reconciliation against the source of truth, or it will quietly drift.
Where this turns up in something OCTYN runs
Each line carries the date it was recorded and where it came from.
- 2026-07-06
A Cloudflare Worker takes Sentry alert webhooks and posts them into a Telegram supergroup with full-context attachments, for every OCTYN project
src/lib/projects.tssentry-telegram-relay → - 2026-09-14
Deploys on octyn.co run through a push, a webhook, a build and a rolling restart, and the same pattern runs every other OCTYN site
docs/growth/case-studies/octyn-site.md, section 3octyn-site →
- stack
- Cloudflare Worker · Sentry webhooks · Telegram Bot API
- routes
- every OCTYN project · one supergroup
If a proposal used this word and did not explain it, ask.
Book a call →