Webhooks
Brokerr exposes a generic source webhook route:
/webhooks/v2/sources/<source-id>The profile editor shows the complete URL and whether Process source webhooks is enabled. Configure that URL in Plex and use Brokerr’s webhook API key.
Events used
Section titled “Events used”Plex event parsing converts provider events into capability changes instead of
target-specific feature names. Completion/uncompletion, rating, and playback
state events can trigger targeted incremental work. Raw media.play,
media.pause, and media.resume noise is not independently synchronized when
a later stop/scrobble event supplies the authoritative observation.
Routing and coalescing
Section titled “Routing and coalescing”Brokerr:
- validates and stores the delivery;
- rejects duplicates;
- identifies the affected source item and library;
- selects only enabled, initialized profiles using that source and library;
- combines related deliveries for the same item during a five-second window;
- reads the newest Plex observation and runs targeted incremental planning.
This can produce two runs when Plex sends events far enough apart or when the first event arrives before Plex has exposed the final state. The delivery history remains visible even when events are combined into one run.
Custom-list collection lifecycle changes are not webhook-driven because Plex does not provide reliable collection events. Full and incremental runs compare collection fingerprints instead.