Zammad Addons New [ REAL ]
To register the addon with Zammad, we need to add a few lines of code to the config/initializers/zammad.rb file.
# config/initializers/zammad.rb
Zammad::Addon.register(MyAddon)
While these new addons are exciting, remember the Zammad golden rule: Keep it lean. Installing 20 addons can slow down ticket creation.
Start with these three core pillars:
Zammad GmbH has launched a curated marketplace for paid and free addons. Vendors must pass a security review. Look for the "Marketplace" tab in your Zammad Admin UI (v6.0+).
| Metric | Verdict | | :--- | :--- | | Installation | Instant. Click "Activate" in the Admin UI. No server restarts. | | Speed impact | Negligible (~50ms extra load on the ticket view). | | Upgrade safety | Survived three Zammad minor version upgrades (v6.0 -> v6.2) with zero breakage. | | API access | All add-on features are exposed via the REST API. We automated ticket merging via a webhook. |
Where Zammad used to be generic, new addons target specific industries. zammad addons new
Running an old version of Zammad with outdated plugins is a security risk. The landscape of zammad addons new releases shows a clear trend: Low-code, AI-first, and Omnichannel.
Whether you opt for the commercial power of a WhatsApp Business bridge or the simplicity of a community bulk-close tool, the right addon turns Zammad from a simple ticket tracker into a business growth engine.
Action Steps:
Don’t let your helpdesk stagnate. The new era of Zammad customization is here—plug in, upgrade, and support smarter.
Have you tried a new Zammad addon recently that we missed? Tell us in the comments below or contribute to the community repository. To register the addon with Zammad, we need
The ecosystem for Zammad "addons" is currently in a state of evolution, moving from a community-driven, undocumented landscape toward a more formalized, AI-integrated future. For users and developers looking at "new" ways to extend Zammad, the focus has shifted from traditional plugins to core AI features and specific package-based modifications. The Evolution of Extension: Packages vs. Addons
Historically, Zammad has not featured a "marketplace" or a formalized "addon" system similar to WordPress or Shopify. Instead, extensions are typically handled through Zammad Packages (.zpm files) The Technical Reality
: There is no official "cookbook" or documentation for creating upgrade-safe addons. Maintenance Challenges
: Because Zammad does not provide a stable API for UI modifications, custom addons often overwrite core classes (like search_controller.rb
). This means a Zammad update can break the addon, or the addon can revert core system updates. Community Workarounds While these new addons are exciting, remember the
: Developers often rely on forum threads and unofficial tutorials to manage packages. Common community requests—such as customer satisfaction ratings (1-5 scales)—are still frequently handled through third-party integrations like LimeSurvey rather than native "new" addons. Zammad Community The "New" Standard: AI as the Native Addon With the release of Zammad 7.0
, the definition of an "addon" has effectively been internalized. Rather than seeking third-party plugins for productivity, users now leverage native AI integrations that act as sophisticated, built-in assistants. Writing Assistant
: This "addon-like" feature allows agents to expand drafts, fix grammar, and change the tone of responses directly within the editor. Ticket Summarization
: A new tool that saves time by condensing long ticket histories into brief summaries, essential for handovers between agents. Language Detection
: Zammad now includes built-in backend services for automatic language detection of incoming articles, improving global support workflows. Zammad Admin Documentation Strategic Customization Beyond Plugins
For organizations needing features not covered by native AI or basic settings, the "new" approach to extensions involves deep system configuration: Zammad Package or a my own version of zammad repository