Content Templates

Content templates enable automatic generation of files and texts during or after posting. Create forum post templates, generate .nfo files, or build custom documentation — the possibilities are endless.

Overview

Templates can be configured per profile and execute at different stages of the posting workflow. Generated content appears in task logs and can be saved to various locations.

📖 Variable Reference: Complete list of available variables and helpers

Configuration Options

Timing & Location

Option	Description	Variable Availability
Include in post	Generated before posting, included in RAR archive	⚠️ Limited (no post-completion data)
Include with NZB	Saved alongside NZB file after posting	✅ All variables available
Custom location	Saved to specified folder	✅ All variables available

Note: If no location options are selected, content is only available in task logs.

Template Properties

Name (UI)

Display name for dropdowns and interface elements. Also used to generate the template ID.

File Extension

Save template output with any file extension (.txt, .nfo, .md, etc.)

File Name

Final filename for generated files. Supports template variables for dynamic naming.

File Contents

Complete template content using Handlebars syntax and available variables.

Use Cases

Forum Post Template

****

📁 **Original Size**: 
📦 **Archive Size**:  ( files)
🛡️ **Recovery**:  ( files)
⏱️ **Processing Time**: ::

**Files Included:**

•  ()

NFO File Generation

╔══════════════════════════════════════╗
║                            ║
╚══════════════════════════════════════╝

Size........: 
Files.......: 
Upload Time.:  minutes

Generated by NZB Flow

Processing Report

# Processing Report: 

## Timing Breakdown
- RAR Creation: s
- PAR Creation: s
- Upload: s
- **Total**: s

## File Analysis
- Original:  files ()
- Compressed:  files ()
- Recovery:  files ()

Advanced Features

Dynamic File Naming

Use variables in filenames to prevent overwrites:

_report_.txt

Conditional Content

Archive created with  volumes

Files posted without compression

Custom Variables

Reference undefined variables to create user-editable fields:

Release Notes: 
Quality: 
Source: 

These will appear as editable fields in the task logs after upload completion.

Best Practices

✅ Do:

Use descriptive template names
Test templates with sample data
Include fallbacks for optional variables
Use custom location with dynamic filenames

❌ Avoid:

Complex logic in templates (keep it simple)
Hardcoded paths in custom locations
Including sensitive information
Overwriting existing files without variables