Configure Shortcut Webhooks and Verify Event Delivery
Register an outgoing Shortcut webhook with a receiver URL, then verify a Story change reaches that receiver. Filter and process events in the receiving integration.
UI webhook setup lives in Settings > Integrations > Webhooks. Programmatic registration requires a token from a non-Observer member; keep secrets out of documents and browser logs.
Example: send Story state changes to an internal release dashboard, while the receiver ignores unrelated activity rather than assuming every event means a release.
Step-by-step guide
Prepare an event receiver
Create a receiver endpoint that can record a safe test payload. Decide which Story changes the integration should use and how duplicate delivery will be handled before connecting production actions.
Register the endpoint
Open Settings > Integrations > Webhooks and choose Add New Webhook. Enter the receiver Payload URL. For API registration, use the documented webhook endpoint and Shortcut-Token header.
Configure receiver authentication
For a custom receiver, use a webhook secret where supported and verify the Payload-Signature HMAC header. Store the secret securely instead of pasting it into a public workflow description.
Trigger and inspect a test event
Move a harmless Story or add a label, then inspect the received payload. Confirm the receiver recognizes the intended entity and change before letting it trigger downstream writes.
Common mistakes
Treating every webhook as the desired event
A receiver must inspect the delivered event before acting. A label update should not accidentally be interpreted as completed delivery.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.