| name | meraki-webhooks |
| description | Receive and verify Cisco Meraki Dashboard webhook alerts. Use when setting up Meraki webhook handlers, validating the sharedSecret, or handling alert events like motion_alert, settings_changed, sensor_alert, or stopped_reporting.
|
| license | MIT |
| metadata | {"author":"hookdeck","version":"0.1.0","repository":"https://github.com/hookdeck/webhook-skills"} |
Cisco Meraki Webhooks
When to Use This Skill
- Setting up Cisco Meraki Dashboard webhook (HTTP server) handlers
- How do I verify Meraki webhooks? / validating the Meraki
sharedSecret
- Understanding Meraki alert types and payload structure
- Handling
motion_alert, settings_changed, sensor_alert, or stopped_reporting alerts
- Why is my Meraki webhook
sharedSecret check failing?
Verification (core)
Meraki does NOT use an HMAC signature header and does NOT follow the Standard Webhooks spec. There is no X-*-Signature header to check. Instead, Meraki puts a plaintext sharedSecret field inside the JSON request body. You verify by comparing that field against the shared secret you configured on the HTTP server (Dashboard → Network-wide → Alerts → Webhooks / HTTP servers).
The secret is optional and travels unencrypted, so ; the only proves the sender knows the value you set. Parse the body, then compare timing-safe.
