Custom Znuny plugin & module development
Need custom features or legacy package updates? Softoft builds maintainable, release-ready Perl and web modules for Znuny.
Znuny Add-ons, Plugins & Extensions
Znuny is an open-source ticket system you can extend with OPM packages (plugins, skins, integrations). Whether you need UI tweaks, reporting, integrations, or AI — the community and vendors publish hundreds of extensions.
Package catalog: The central hub for Znuny plugins and add-ons is OpenITSMHub — searchable by category, compatibility, and maintainer.
Browse all Znuny packages on OpenITSMHub →
What are Znuny add-ons?
Section titled “What are Znuny add-ons?”In Znuny, extensions are usually packages (OPM files). They can:
- Add features — e.g. advanced dynamic fields, ticket printing, time accounting
- Customize the UI — skins, themes, extra dashboard widgets
- Connect systems — REST clients, monitoring, CMDB, chat
- Automate processes — event handlers, Generic Agent extensions
Packages are installed via Package Manager in the admin UI or on the console with Admin::Package::Install. To build your own: Plugin development with OPM packages.
Finding packages on OpenITSMHub
Section titled “Finding packages on OpenITSMHub”OpenITSMHub aggregates packages for Znuny, OTOBO, OTRS Community Edition, and related ITSM stacks. Useful entry points for Znuny:
| Resource | Link |
|---|---|
| Znuny plugin overview | openitsmhub.com/znuny-plugins |
| All packages (Znuny filter) | openitsmhub.com/packages?systems=znuny |
| Znuny system page | openitsmhub.com/systems/znuny |
OpenITSMHub shows license, framework version, maintainer, and often direct download or repository links before you deploy to production.
Example extensions
Section titled “Example extensions”A sample of common categories — the full, up-to-date list lives on OpenITSMHub:
| Category | Example (OpenITSMHub) |
|---|---|
| Attachments & ticket UI | Znuny4OTRS Download All Attachments |
| Dynamic fields | Znuny4OTRS Advanced Dynamic Fields |
| Development & API | Python REST API Client, pyznuny |
| AI & automation | otai-otobo-znuny |
| IDE & tooling | vscode-znuny |
For AI-assisted ticket classification in Znuny, see OpenTicketAI and Znuny Artificial Intelligence.
Installing an add-on
Section titled “Installing an add-on”Via the admin UI
Section titled “Via the admin UI”- Open Admin → Package Manager
- Upload the OPM file or use an online repository (if configured)
- Confirm installation and rebuild SysConfig if needed (
Maint::Config::Rebuild)
Via the console (Docker or server)
Section titled “Via the console (Docker or server)”bin/znuny.Console.pl Admin::Package::Install /path/to/package.opmbin/znuny.Console.pl Maint::Config::Rebuildbin/znuny.Console.pl Maint::Cache::DeleteOn Docker stacks, run these inside the app container — see Znuny Docker.
GUI extensions and skins
Section titled “GUI extensions and skins”UI customizations (skins, themes) are often available as packages or separate downloads. OpenITSMHub lists compatible skins under Skins. Basics: Znuny GUI and Skins & themes.
Building your own add-on
Section titled “Building your own add-on”Start with Plugin development — SOPM layout, building OPM files, event handlers, and dynamic fields. You can publish packages on OpenITSMHub for the community.
Related topics
Section titled “Related topics”- Znuny REST API — integrations and automation
- Web Services — configure the Generic Interface
- Znuny Docker — manage packages in container environments
- OpenITSMHub – Znuny plugins — package catalog
Frequently asked questions
Where is the primary catalog for Znuny add-ons and how can I effectively use it to find packages?
The central hub for finding Znuny add-ons and plugins is OpenITSMHub. This platform aggregates packages for Znuny and other ITSM systems, allowing you to browse, search, and filter extensions by category, compatibility (framework version), and maintainer. Before installing, OpenITSMHub provides crucial information such as the license, required framework version, and often direct download links or repository access. It's recommended to use the dedicated Znuny plugin overview or filter all packages by the Znuny system to narrow down your search.
Quellen:
What are the detailed steps for installing a Znuny OPM package, both through the admin interface and the console?
You can install Znuny OPM packages via two main methods. For the admin UI, navigate to Admin → Package Manager, then upload the OPM file directly or utilize a configured online repository. After confirming the installation, it's often necessary to rebuild SysConfig (Maint::Config::Rebuild). For console installation, which is common in Docker or server environments, execute bin/znuny.Console.pl Admin::Package::Install /path/to/package.opm. Following this, always run bin/znuny.Console.pl Maint::Config::Rebuild and bin/znuny.Console.pl Maint::Cache::Delete to ensure changes are applied and caches are cleared. In Docker setups, these commands must be run inside the application container.
Quellen:
Why is it essential to test new Znuny packages in a staging or test system before deploying them to a production environment?
Installing new packages directly into a production environment carries significant risks, including system instability, data corruption, or unexpected behavior that could disrupt critical operations. It is crucial to first test all new add-ons in a dedicated staging or test system. This allows you to verify compatibility with your existing Znuny setup, check for conflicts with other installed packages, and ensure the add-on functions as expected without impacting live services. Always review the framework version and dependencies listed on OpenITSMHub to prevent compatibility issues before any deployment.
Quellen:
What are the common categories of Znuny extensions, and can you provide some examples of available add-ons?
Znuny extensions, typically delivered as OPM packages, cover a wide range of functionalities to enhance your ticket system. Common categories include adding new features (e.g., advanced dynamic fields, ticket printing, time accounting), customizing the user interface (e.g., skins, themes, extra dashboard widgets), connecting systems (e.g., REST clients, monitoring, CMDB, chat integrations), and automating processes (e.g., event handlers, Generic Agent extensions). Specific examples found on OpenITSMHub include "Znuny4OTRS Advanced Dynamic Fields" for enhanced data input, "Znuny4OTRS Download All Attachments" for convenience, and "otai-otobo-znuny" for AI-assisted ticket classification.
Quellen:
How can I get started with developing my own custom add-ons or plugins for Znuny, and is there a way to share them with the community?
To begin developing your own custom add-ons for Znuny, you should start by exploring the Plugin development guide. This resource covers essential topics such as the Standard OPM Layout (SOPM), the process of building OPM files, implementing event handlers to react to system events, and creating dynamic fields to extend ticket data. Developing custom packages allows you to tailor Znuny precisely to your organization's unique needs. Once developed, you have the option to publish your packages on OpenITSMHub, making them available to the broader Znuny community and contributing to the ecosystem.
Quellen:
Are there specific add-ons or methods available for customizing the visual appearance and user interface of Znuny, such as skins or themes?
Yes, Znuny offers various ways to customize its visual appearance and user interface, often through dedicated add-ons or packages. These UI customizations can include different skins and themes that alter the look and feel of the agent and customer portals, as well as additional dashboard widgets for personalized information display. Many such packages are available on OpenITSMHub, where you can find compatible skins listed under the "Skins" section. For a deeper understanding of UI customization, you can also refer to the "Znuny GUI" and "Skins & themes" documentation, which provide foundational knowledge on how to manage and apply these visual enhancements.
Quellen: