Feed Scripts
About
Feed extensions are called after an RSS feed is read and before it is processed by NZBGet.
The extension receives the downloaded feed file and can check or modify it before NZBGet parses it.
Writing feed extensions
Please read Extensions for general information about extensions first.
An extension is called for feeds when its kind is set to FEED in manifest.json (see "kind"). Extensions of the old format (without manifest.json) declare this with a ### NZBGET FEED SCRIPT line in the script file.
The extension is called once for each feed, after the feed file has been downloaded and before it is parsed. The path of the feed file is passed in the environment variable NZBFP_FILENAME; the extension may rewrite that file — the items of the resulting file are the ones NZBGet processes afterwards.
Which extensions are called is set with the option FeedN.Extensions for a specific feed. If that option is empty, the extensions from the global option Extensions are used.
The extension must exit with the code 93 on success. With any other exit code the feed is marked as failed, its items are not processed and the log shows Feed-script <name> for Feed<id> failed.
Feed extensions are also executed when a feed is previewed in the web interface.
Feed information
The information about the feed which is currently processed:
- NZBFP_FILENAME - Path to the downloaded feed file.
- NZBFP_FEEDID - ID of the feed (
1forFeed1).
The program options are passed in NZBOP_* variables (for example NZBOP_VERSION), the options of the extension itself in NZBPO_* variables (see Extensions).
Introduction
Installation manuals
- Installation on Windows
- Installation on Windows via WinGet
- Installation on macOS
- Installation on macOS via Homebrew
- Installation on Linux
- Installation on Docker
- Installation on Docker - LinuxServer.io version
- Installation on Android
- Installation on Synology
- Installation on QNAP
- Installation on other NAS devices
Building manuals
Configuration
- Backup And Restore Settings
- Performance Tips
- Choosing Cipher
- Behind Other Web Server
- TLS certificate verification
- What is the Default NZBGet Password?
- NZBGet Docker Setup Guide
- NZBGet Port Settings and Access Guide
- How to Configure NZBGet: Complete Setup Guide
- What Is Usenet?
- NZBGet 502 Error: Quick Fix Guide
- How to Upgrade from NZBGet v21.1 to the Latest NZBGet Version
- Slow NZBGet Speeds? Here’s How to Fix It
- NZBGet Performance Optimization Guide
- NZBGet Path and Folder Structure Guide
- How to Link NZBGet with Sonarr, Radarr, and Other Tools
- Sonarr vs VideoSort: How They Work with NZBGet
- NZBGet Storage Guide: Improve Performance with Smarter Path Setup
- How to Configure NZBGet on Android TV
- Using NZBGet with Sonarr and Radarr on Android TV
Performance tuning
- How to Optimize Usenet Performance in NZBGet
- NZBGet SystemHealth: Configuration and Environment Diagnostics
- Testing Usenet Speed and Performance in NZBGet
- Diagnosing and Maximizing Usenet Speeds in NZBGet
- Understanding Download Health in NZBGet
- Finding the Optimal Connection Count in NZBGet
- Primary vs Fill Servers Explained
- Understanding the Statistics Page in NZBGet
Usage
- Quick Filter
- Keyboard Shortcuts
- RSS and duplicate check
- VideoSort
- Console Mode
- Command Line Reference
- Performing Speed Tests
- NZBGet Interface Buttons Explained: What They Do and How to Use Them
- How to Use the NZBGet Status Tab
Development
Extensions
- Extension Scripts
- Post-processing scripts
- Scan Scripts
- Queue Scripts
- Scheduler Scripts
- Feed Scripts
- NZBGet Extension Manager: What It Is and How to Use It
- API reference
News server setup
- Astraweb
- BlockNews
- Cheapnews
- EasyNews
- Eweka
- FreeDiscussions
- Frugal Usenet
- GigaNews
- NewsDemon
- Newsgroup Ninja
- NewsgroupDirect
- Newshosting
- Pure Usenet
- SunnyUsenet
- Supernews
- theCubeNet
- ThunderNews
- TweakNews
- Usenet.Farm
- UsenetExpress
- UsenetServer
- UseNext
- ViperNews
- XLned
- XS News