Smee (unverified webhooks)

Receive generic SSE webhooks in standalone and Overwolf, without a companion. These are unverified events, not authenticated Kick or GitHub events.

1. Create a channel on smee.io or a compatible server.
2. Under Connections > Webhook delivery, add a Smee connection with that HTTPS channel URL.
3. Under Connections > Sources, add Smee (unverified webhooks) and choose the connection.
4. Configure the sender’s webhook URL to the channel URL.
5. Match events in rules using source Smee, feature unverified.

The event name is the forwarded x-github-event or kick-event-type header, falling back to webhook. The parsed payload is data.body and data.verified is always false. Sensitive forwarded headers are not included. Stream Pulse’s own forwarding marker is preserved for the forwarding loop guard. Test with synthetic payloads and keep Dry run enabled until rules are ready.

The relay sees webhook content. Anyone with the channel URL may be able to listen or inject events. Unverified events can still trigger real actions in Live mode. Keep the URL private and use suitable rule filters and cooldowns.

Standard Smee parses and reconstructs JSON, losing exact signed bytes. It cannot be selected as verified Kick delivery. Use an HTTP tunnel or a compatible raw-body relay for that instead; never bypass signature checks.

Channel URLs are stored locally but removed from configuration exports. Re-enter them after importing.

See Webhook delivery and pairing for the verified relay protocol and architecture. The Smee setup example includes a screenshot of the delivery fields, channel creation resources and a synthetic PowerShell POST you can match with a dry-run rule.