Webhooks: Events Fire, Nothing Runs
Event-driven automation lives and dies on the boundary between a platform and your receiver. This lab wires a real Cisco platform to a containerized webhook receiver so you can trace an event end to end and find where a silent drop hides.
The problem
A webhook receiver is registered to trigger automation when a platform event fires. The platform shows the events being sent, but the automation never runs, and there are no errors in the receiver's logs.
What you'll practice
- Register a webhook and inspect its delivery attempts
- Validate incoming webhook signatures and secrets correctly
- Return correct status codes so retry logic behaves
- Trace an event from platform through receiver to handler
- Diagnose deliveries that are silently rejected
The topology
A Cisco platform emits events to a containerized webhook receiver that triggers automation, with a delivery log on the platform side, so you trace an event end to end instead of guessing where it stopped.
Topology diagram
Frequently asked
Why are the receiver logs clean?
Because the request is rejected at the edge, before it reaches the handler that logs. Signature or secret validation that fails silently looks exactly like nothing arriving.
Does this map to DEVCOR?
Yes. Webhooks, signature validation and event-driven design are core DevNet Professional (350-901) application topics.
Ready to run this lab yourself?
No setup, no image sourcing. Book a session or ask for a live demo.