Whatseerr
A self-hosted WhatsApp bot for Seerr that lets users search for and request movies and TV shows directly from WhatsApp messages.
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
38/100 Low
- Maintained
- 49last commit 244 days ago
- Popular
- 3659 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 201 serious finding, 16 minor, CI
Based on 4 of 5 factors.
Security check: 1 serious finding
- Uses proxy-addr 2.0.7, which has a known critical vulnerability (npm)
Automated checks on commit 3edc9bc, 12 Nov 2026. Not an audit.
Availability: platform listings confirmed today, links checked 17 days ago
- GitHub stars
- 59
- Open issues
- 3
- Last commit
- 2026-03-22
- Latest release
- v1.0.5
- License
- MIT
- Activity
- stale
Checked 5 days ago - source: GitHub (sufxgit/whatseerr)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- First-time setup Run a WAHA (WhatsApp HTTP API) service and a Seerr instance first. On first run, whatseerr creates /config/config.example.json; rename it to config.json and set the host, the Seerr API key (Seerr Settings > General), the WAHA API key, and userIdMappings mapping WhatsApp numbers to Seerr user IDs. Point the WAHA webhook at your whatseerr host (e.g. port 3006, /requests path), and optionally set a S source
- Docker quick start Run Docker, a configured WAHA (WhatsApp HTTP API) service, and a Seerr instance before pulling and starting the Whatseerr container. source
Fetched 43 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What services must be running before deploying Whatseerr?
It requires a running and configured WAHA WhatsApp HTTP API service and a Seerr instance. Whatseerr is connected to both through its config file.
Where does Whatseerr create its configuration file on first run?
On first run it creates /config/config.example.json. Rename it to config.json and set the host, Seerr API key, WAHA API key, and user mappings.
How do I allow specific WhatsApp numbers to request media?
Add a userIdMappings entry in config.json for each phone number, using the number with country code and no @c.us suffix. Set it to the user's Seerr user ID, with an optional username and admin flag.
Which WAHA events should I enable for the bot to work?
Point the WAHA session webhook at your Whatseerr host on port 3006 under the /requests path. Enable the session.status, message, and message.reactions events.
How do I receive request status updates from Seerr?
Add an optional Seerr webhook for notifications such as approved, available, or declined. Point it at your Whatseerr host on port 3006 under the /seerr path and select the notification types you want.
Answers sourced from github.com
Community
- Reddit (reddit)
- WhatsApp but self-hosted? : r/selfhosted - Reddit (reddit)
Collected 49 days ago - public community threads