Released: March 2026
Forget copy-pasting into ChatGPT. This new community addon integrates a local LLM (like Llama 3 or Mistral) directly into the Zammad ticket mask.
Q: Do new Zammad addons break during a minor upgrade (e.g., 6.0 to 6.1)?
A: Usually yes, if they hook deep into the UI. New addons built with the official ui_plugin API (v2) are version-locked. Always check the addon’s zammad_requirement field.
Q: Where is the official marketplace for new Zammad addons? A: Surprisingly, Zammad doesn't have an "App Store" like Jira does. The best sources are:
Q: I need a custom new addon. Where do I start?
A: Hire a developer familiar with lib/tasks/zammad/ and the Channel::Driver pattern. Many new addons are simply smart webhooks.
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.
The release of Zammad 7.0 on March 4, 2026, introduced a wave of new features and integrations that function like modern "addons," focusing heavily on AI automation and updated communication channels.
Below is a draft blog post highlighting these recent developments.
Zammad 7.0: The Dawn of AI-Powered Support and New Integration Horizons
The wait is over! With the launch of Zammad 7.0, we aren’t just looking at a minor version bump; we are entering a new era of "intelligent" helpdesk management. While Zammad has always been the Swiss Army knife of open-source support, these latest features and "addons" bring a level of automation that was previously the stuff of sci-fi.
Here’s a breakdown of the most exciting additions and what they mean for your team. 1. The AI Writing Assistant: Your New Personal Editor
One of the most significant "addons" to the Zammad core is the AI Writing Assistant. Integrated directly into the ticket editor, this tool allows agents to: Polish Drafts: Instantly correct spelling and grammar.
Change Tone: Rewrite messages to be more professional, friendly, or concise.
Translate on the Fly: Bridge language gaps without leaving the ticket interface. 2. AI Ticket Summaries: Catch Up in Seconds
We’ve all been there—opening a ticket with 50+ entries and trying to figure out what actually happened. The new AI Ticket Summary provides a structured overview of long threads, allowing agents to jump into complex cases with full context in seconds. 3. Smarter Workflows with n8n and Webhooks
While Zammad has always had a rich list of integrations, the push toward n8n and generic webhooks is the real game-changer for 2026.
n8n Integration: Connect Zammad to over 1,000 other services to automate cross-platform communication.
Slack Transition: Note that the old native Slack integration is being deprecated in favor of pre-built webhooks, providing more flexibility and stability for your notifications. 4. Enhanced Mobility and User Experience
The new Mobile View ensures that your support doesn't stop when you leave your desk. Coupled with the Bubble Menu in the desktop editor, formatting text and accessing AI tools is now just a click away, eliminating the need to memorize complex keyboard shortcuts. 5. Technical Maintenance: Moving Forward
To support these heavy-duty features, Zammad 7.0 brings some critical technical shifts: zammad addons new
PostgreSQL Only: Zammad has officially deprecated MySQL to ensure a more stable and high-performance database environment.
Infrastructure Updates: Support for Redis Sentinel and improved Docker backup/restore modes are now native, making it easier for DevOps teams to maintain large-scale deployments. Ready to Upgrade?
Zammad 7.0 is now available for both SaaS and self-hosted users. If you're on version 6.5, we highly recommend checking the official release notes for breaking changes—especially regarding the PostgreSQL requirement—before making the jump.
Zammad 7.0 PostgreSQL Upgrade required - Technical assistance
Zammad is built on Ruby on Rails, and its addon system relies heavily on Rails Engines. Creating a new addon involves generating a specific directory structure and registering the addon with Zammad.
Here is a guide on how to create a new addon from scratch.
Since "piece" is not a standard Zammad command, you likely need to:
Are you trying to create a specific type of addon (e.g., a new Ticket Overview, a Channel integration, or a generic UI modification)? I can provide more specific code if you clarify the goal.
The Evolution of Zammad: Advancing Helpdesk Efficiency through New Add-ons and Integrations
In the rapidly evolving landscape of customer support technology, Zammad has emerged as a powerhouse by maintaining a delicate balance between open-source flexibility and enterprise-grade performance. As of 2026, the concept of "add-ons" in Zammad has shifted from simple community scripts to a structured ecosystem comprising official premium features, native AI capabilities, and sophisticated third-party integrations. This transition reflects a broader trend in the helpdesk industry: moving beyond basic ticket management toward intelligent, highly customizable workflows. The Shift to Official Premium Add-ons
For much of its history, Zammad maintained a parity between its community and paid versions. However, the introduction of a dedicated add-on framework
for Enterprise and Corporate-tier subscribers marks a strategic pivot. While many features remain standard, new official add-ons are designed to provide premium, pre-built functionalities that are not available in the community version. These include high-priority custom feature requests and specialized tools tailored for large-scale operations, ensuring that the most demanding business environments have the specific capabilities they need without bloating the core open-source codebase. The Rise of AI-Powered Native Add-ons
Perhaps the most significant "new" additions to the Zammad suite are its native AI features, many of which are reaching full maturity in the Zammad 7.0 release cycle. These are not mere external plugins but deeply integrated functional modules that act as force multipliers for support agents: AI Writing Assistant
: This tool allows agents to rewrite, polish, or translate replies directly within the ticket interface, ensuring consistent communication quality. AI Ticket Summaries
: To reduce the time spent catching up on long email threads, this module provides instant context, open questions, and customer sentiment analysis. Intelligent Routing
: Leveraging AI to auto-detect languages and customer intent, Zammad now automatically routes conversations to the appropriate specialized teams, eliminating manual triage. Expanding Through the Package Management System
Zammad’s architectural support for "Packages" remains the primary gateway for both community-driven and specialized add-ons. The Zammad admin area includes a dedicated package management section where administrators can install external modules to extend the system's core logic. This has enabled a vibrant community to develop niche solutions, such as: Automate Support Workflows with Zammad, n8n and Local AI
The Future of Helpdesk Automation: Exploring New Zammad Addons and Integrations
As organizations scale, the need for a highly customizable helpdesk becomes paramount. Zammad has long been a favorite for its open-source flexibility, and the landscape of Zammad addons is evolving rapidly to meet modern demands. Whether you are looking for premium enterprise features or community-driven enhancements, the ecosystem is expanding to offer more than just standard ticketing. 1.2.1, 1.4.3 What’s New in Zammad Addons?
The term "addon" in the Zammad world is shifting. While many features are integrated directly into the core to keep the platform stable, there is a growing trend toward premium addons and third-party marketplace solutions. 1.2.1
Enterprise-Tier Addons: Zammad now offers specific addons for Enterprise and Corporate subscribers. These currently include high-priority custom feature requests and are moving toward pre-built premium features that won't be available in the community version. 1.2.1
WHMCS Integration: A significant new development is the Zammad Ticket System integration for WHMCS, which entered beta in early 2025. This allows hosting providers to manage Zammad tickets directly within the WHMCS client area, featuring robust CSRF handling and sensitive data management. 1.4.9, 1.4.10
AI-Powered Workflows: Recent shifts emphasize using low-code tools like n8n as a "super-addon." By connecting Zammad to n8n, users can create custom AI agents that summarize tickets or automate complex response chains without modifying the core Zammad code. 1.4.5, 1.4.6 Essential Community and Custom Addons Released: March 2026 Forget copy-pasting into ChatGPT
The community continues to bridge gaps with specialized packages. Some notable recent community-driven developments include: 1.3.1
Rolfs-Telnyx Integration: A package for Telnyx SMS notifications, allowing for more diverse communication channels. 1.3.1
OpenSVC Addon: A specialized addon that introduces selectable customer priority and support contract types for organizations—features often requested for B2B support models. 1.4.8
One Tab Only: A productivity-focused addon designed to limit the Zammad interface to a single tab to streamline agent focus. 1.3.1 Latest Platform Improvements (Zammad 6.5 & 7.0)
While not "addons" in the traditional sense, the latest version updates act as the foundation for new extensions: 1.2.4, 1.5.2
Enhanced Webhooks: Version 6.5 improved security by ignoring redirects, ensuring that custom integrations remain secure against malicious administrative exploits. 1.2.4
Modern Tech Stack: Zammad has reimagined its documentation and internal tech stack, making it easier for developers to understand how to build and maintain their own extensions. 1.2.3
Zammad 7.0 Previews: With the major release of Zammad 7.0 on the horizon, the focus is on "Structured, Reliable Support," hinting at more built-in modules that were previously handled by external addons. 1.5.2 How to Extend Your Zammad Instance
If you are looking to add new functionality today, you have three primary paths:
Standard Integrations: Check the official Admin Documentation for built-in connections like Slack, GitHub, and various CTI (Phone) systems. 1.2.5
API & Webhooks: Use the REST API to build custom bridges to your internal tools. This is often more stable than installing unverified community packages. 1.5.3
Community Packages (.zpm): Explore the Zammad Community Forum for .zpm files that can be installed to add niche features like custom buttons or specialized headers. 1.3.1, 1.5.6
This paper outlines the current state and latest developments for Zammad addons (often referred to as "Packages" or "Integrations") as of early 2026 1. The Addon Concept in Zammad Zammad distinguishes between core integrations addons/packages Download Zammad Integrations:
Features built directly into the Zammad codebase (e.g., LDAP, GitHub, Zabbix). Addons/Packages:
External extensions that can be uploaded via the "Packages" area in the Admin documentation. Historically, these have been rare and lacked official documentation. Zammad Community 2. New & Notable Developments (2025–2026) Zammad 7.0 Release (March 2026): This major version introduced significant AI writing assistants bubble menu for text formatting. Premium Addon Strategy:
As of early 2025, Zammad GmbH began prioritizing "Addons" as high-priority custom feature requests or pre-built premium features reserved for Enterprise-tier subscribers. Deprecations: With version 7.0, older native integrations like and the legacy Slack integration were deprecated or removed in favor of modern Database Transition: Zammad has moved toward supporting PostgreSQL exclusively , deprecating MySQL. 3. Key Integration Categories
Integrations are Zammads "plugins"/"extensions"/"addons" right?
In Zammad, "addons" are officially called Packages. Creating a new package involves building a .zpm (Zammad Package Module) file that contains your code, assets, and metadata. 1. Prerequisites and Setup
To develop packages, it is recommended to use a standard Debian/Ubuntu installation rather than Docker, as Docker environments do not natively support package development tools.
Tools Required: You will need git and pnpm for asset management.
Repo Access: Clone the Zammad repository to use as a development base:git clone https://github.com/zammad/zammad.git. 2. Create the Package Structure
A Zammad package must follow a strict naming convention: Vendor-FeatureName (e.g., MyCompany-ThemeCustomizer).
Initialize Project: Create your directory and initialize a Git repository: mkdir Vendor-NewAddon && cd Vendor-NewAddon git init ``` Use code with caution. Copied to clipboard Compatibility: Works with Zammad 6
Add Metadata (SZPM): Create a Source Zammad Package Module (.szpm) file. This file acts as a manifest, defining the package name, version, and the files it includes.
Pro Tip: Many developers use a helper script like git zammad-new-szpm to generate this template. 3. Adding Components
You can inject various elements into Zammad via your package:
Database Migrations: Place these in db/addon/ to add new fields or settings.
Frontend Assets: CSS files should be placed in app/assets/stylesheets/addons/. Zammad also supports SCSS.
Custom Gems: If your addon requires external Ruby libraries, create a Gemfile.local within your package folder. Zammad will automatically include these in the bundle. 4. Build and Install
Once your files are ready, you must compile them into a single .zpm file.
Build the ZPM: Use a command like git zammad-create-zpm 1.0.0 to generate the JSON-based package module.
Upload: Log in to your Zammad instance and navigate to Admin → Packages. Click "Upload" and select your .zpm file.
Finalize: Run the following commands on your server to apply changes:
zammad run rake zammad:package:post_install systemctl restart zammad ``` Use code with caution. Copied to clipboard Development Tips
Avoid Overwriting: It is best practice to avoid overwriting core Zammad files, as this can break updates. Instead, use hooks or add new files in the addons directories.
Testing: You can trigger package migrations manually for testing using the Rails console: Package::Migration.migrate('YourPackageName'). If you'd like, let me know: Are you looking to add new database fields? Do you need to change the UI (logo, colors, etc.)? Are you integrating an external API?
I can provide specific code snippets or folder structures for any of those goals. How to build custom packages - Development - Zammad
Title: Supercharge Your Help Desk: Exploring New Zammad Addons for 2026
Slug: zammad-addons-new-2026
Meta Description: The Zammad ecosystem is growing fast. Discover the newest official and community addons for reporting, automation, security, and AI that will transform your open-source help desk.
If you are running a customer support team, you already know the power of Zammad. As a leading open-source help desk, it offers ticketing, automation, and knowledge management out of the box.
But the real magic happens when you extend it.
The Zammad ecosystem has exploded with new Zammad addons over the last 12 months. Whether you need enterprise-grade analytics, WhatsApp integration, or AI-powered response generation, there is now an addon for that.
Let’s dive into the newest addons you need to install right now.
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: