For the complete documentation index, see llms.txt. This page is also available as Markdown.

Webhook or Watcher

Pick the right scrobble path. Watcher is recommended. Webhooks remain available.

Use this page if you want the quick answer.

CrossWatch supports two scrobble input paths:

  • Watcher — recommended

  • Webhooks — event-driven alternative

Use Watcher when

Choose Watcher if you want the supported path.

It is the right choice for most setups.

Why:

  • supports multiple routes and profiles

  • sends to Trakt, SIMKL, and MDBList

  • handles more playback edge cases

  • does not need Plex Pass or Emby Premiere

Guide: Watcher.

Use Webhooks when

Choose Webhooks when server-pushed events fit your setup better.

This is most useful for Trakt-focused webhook flows.

Limits:

  • Trakt only

  • more fragile around HTTPS and reverse proxies

  • Plex Pass or Emby Premiere may be required, depending on server

Guide: Webhooks.

Run both only when they own different Plex servers

Most setups should use one path.

Use both only when they handle different Plex servers.

Good pattern:

  • Watcher for a local Plex server

  • Webhooks for a remote Plex server

Split them with Plex Server UUID filters.

Filter basics for Plex

Plex scrobble filtering has three useful layers:

  • User filters — allow only specific Plex users

  • Server UUID filters — allow or block specific Plex servers

  • Library whitelist — accept only selected Plex libraries

A Plex event must pass every enabled filter.

If a Plex library whitelist is set and an event has no usable library id, CrossWatch skips it.

Blacklist wins over whitelist for Plex server UUIDs.

Quick decision

  • Want the supported setup: use Watcher

  • Want webhook endpoint setup: use Webhooks

  • Want the overview and setup flow: use Scrobble

TLS note

Last updated

Was this helpful?