Forwarding events

HTTP webhook and custom WebSocket actions can tick Forward the incoming event as-is instead of building a custom body. The action sends:

{
  "event": "name",
  "feature": "...",
  "data": {},
  "gameKey": "...",
  "kind": "event",
  "category": "...",
  "timestamp": 0,
  "sourceId": "...",
  "forwardedBy": "stream-pulse"
}

sourceId is present only for events from a configured source.

Loop guard

A Custom WebSocket or Custom REST source that receives an event tagged forwardedBy: "stream-pulse" marks it as forwarded. Forward actions skip such events and log them as skipped, so two Stream Pulse instances cannot loop.

Other actions on a forwarded event still run, so rule cooldowns remain the safeguard for Streamer.bot loops.