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
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
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
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 zammad addons new
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
Introduction to Zammad Addons
Zammad is a robust helpdesk software that offers a wide range of features to manage customer support tickets, knowledge bases, and more. One of its key strengths is its extensibility through addons, which allow developers to customize and enhance the software to meet specific business needs. In this post, we'll explore the process of creating a new addon for Zammad.
Prerequisites
Before diving into addon development, ensure you have:
Addon Structure
A Zammad addon typically consists of the following components:
Creating a New Addon
Let's create a simple addon that adds a new feature to Zammad.
Zammad addons have matured from "nice-to-have" to "mission-critical." The new generation focuses on low-code automation, AI augmentation, and deep vertical workflows. Whether you run a three-person support team or a global enterprise helpdesk, there’s likely a new addon that fits your exact friction point — and it probably arrived in the last six months.
Want to stay updated? Bookmark addons.zammad.org and filter by “Release date – Newest.”
There is no official addon or standard package named "long paper" in the current Zammad ecosystem as of April 2026. However, your query may refer to custom development for handling long documents or a specific community-requested feature for the "long paper" format in Zammad. Zammad Addons & Customizations
Zammad does not have an official public marketplace for addons, but it supports extensibility through Integrations Custom Packages : Users can create
(Zammad Package Manager) files to add functionality. There is currently no official "cookbook," but community guides on Zammad Package Best Practices are available. AI & Productivity : In March 2026, Zammad 7.0 introduced native AI features designed to streamline support work and data handling. Knowledge Base Menus
: For users looking to manage extensive text or "long paper" formats in the Knowledge Base, Zammad 6.2+ allows for custom Public Menus and URL re-arrangement to improve navigation. Work-in-Progress Stack
: Zammad is currently transitioning from a CoffeeScript-based frontend to a new stack using Vue.js, TypeScript, and GraphQL , which may impact how new UI-heavy addons are developed. Zammad Community Managing Long Content in Zammad
If you are trying to implement or find a way to handle long reports or papers: Ticket Sidebars
: Community members have experimented with custom "Upload Document" buttons in the sidebar to integrate external document management systems via API. Automated Documentation : Zammad recently updated its own documentation tech stack
to automate screenshots and visuals, which might serve as inspiration for managing large-scale documentation. Zammad Community Could you clarify if "long paper"
refers to a specific document format, a plugin for long-form text analysis, or a nickname for a certain community project?
The new Zammad addon ecosystem marks a shift from manual code injections to a structured, modular approach that allows organizations to expand their helpdesk without compromising core stability. Historically, adding custom functionality to Zammad required deep Ruby knowledge and manual file placement, but recent developments in the community and official channels have introduced streamlined ways to integrate third-party tools. The Evolution of Zammad Customization
Zammad has traditionally been an open-source powerhouse, but its "addon" culture was often decentralized. A typical "story" of a new addon usually begins with a specific business pain point, such as a support team needing to pull live customer shipping data directly into a ticket.
The "Old" Way: Developers would create custom scripts or modify the source code, which often broke during the next Zammad update.
The "New" Way: Using the Zammad API and dedicated Integration Packages, developers can now build "Sidecar" apps or use the Package Manager to install validated extensions that persist through updates. Key New Addons and Integrations
Recent additions to the Zammad toolkit focus on automation, communication, and data visibility:
AI-Powered Summarization: Newer addons leverage LLMs (like ChatGPT) to summarize long ticket threads, allowing agents to catch up on complex cases in seconds.
Advanced Telephony (CTI): New connectors for cloud PBX systems (like Placetel or NFON) now offer deeper integration, showing customer history before the agent even picks up the phone.
Knowledge Base Enhancements: Addons that allow for "Internal Only" knowledge base articles or multi-brand documentation are becoming standard for large enterprises.
Custom Object Creators: While built-in, the new "Core Workflow" features act like internal addons, allowing admins to create conditional fields that only appear when specific ticket criteria are met. How to Find and Install New Addons
If you are looking to enhance your instance, the journey typically follows these steps:
The Zammad Community: The official community forum is the primary hub for "unofficial" but highly functional addons developed by the user base.
GitHub Repositories: Many developers host .zpm (Zammad Package Manager) files on GitHub. These can be uploaded directly via the Zammad Admin interface under System > Packages.
Third-Party Marketplace Providers: Companies like Pluspoint or Zammad partners offer enterprise-grade addons specifically for GDPR compliance, advanced reporting, or SAP integration.
The recent release of Zammad 7.0 on March 4, 2026, introduces powerful native capabilities that reduce the need for external add-ons, particularly in AI-driven ticket management. 1. Native AI Integration: The "Ultimate Add-on"
Zammad 7.0 integrates AI as a core feature, allowing you to choose your own Large Language Model (LLM) to maintain data sovereignty. This native functionality replaces several older third-party helper tools:
Writing Assistant: Enhances agent productivity by expanding bullet points into well-written sections, fixing grammar, and simplifying complex text. In Zammad, "addons" are officially called Packages
Smart Summaries: Provides lightning-fast ticket summaries, allowing agents to get up to speed on long conversations instantly. 2. Shared Drafts & Collaboration
The Shared Drafts feature has been significantly refined in recent versions (6.2+).
QA Process: Agents can now save and share drafts for internal review before a response is officially sent.
Visibility: A "📝 Draft available" indicator appears in the ticket zoom view, showing who last edited the draft.
Automatic Cleanup: Once a ticket is updated with the draft content, Zammad automatically removes the shared draft to keep the database clean. 3. Community Add-ons & Packages
While Zammad’s core is robust, the community continues to develop specialized extensions:
Communication Channels: Extensions for platforms like RocketChat and Cloudvox SMS remain popular for diversifying customer contact points.
Security Hardening: Community-driven hardening add-ons are available to further secure default settings in high-risk environments.
Custom Field Power: Zammad's native Individual Fields now support complex query classifications for tickets, users, and organizations, often fulfilling needs that previously required custom development. Shared Drafts - Zammad User Documentation
Title: Introducing Zammad Add-ons: Enhance Your Customer Support Experience
Description: Zammad is a popular open-source customer support platform that helps businesses manage their customer interactions across multiple channels. To further extend its capabilities, we're excited to introduce Zammad add-ons - a collection of integrations and plugins that can enhance your customer support experience.
What are Zammad Add-ons?
Zammad add-ons are third-party integrations and plugins that can be easily installed on your Zammad instance to add new features, functionality, and integrations. These add-ons are developed by our community of developers and partners, and can be easily installed and configured through the Zammad admin interface.
Benefits of Zammad Add-ons
Examples of Zammad Add-ons
How to Get Started with Zammad Add-ons
By leveraging Zammad add-ons, businesses can unlock new capabilities, improve efficiency, and enhance the customer experience. Whether you're a small business or a large enterprise, Zammad add-ons can help you take your customer support to the next level.
Zammad recently introduced major built-in features and "packages" (the internal name for add-ons) with the release of Zammad 7.0 on 4 March 2026
. While Zammad does not have a traditional "app store," these new capabilities function as integrated add-ons that you can enable or manage via the Zammad Admin Documentation New AI Add-on Features (Zammad 7.0)
The newest "add-ons" are primarily AI-driven tools that require an LLM (Large Language Model) configuration to activate: AI Ticket Summary
: Generates a "TL;DR" for long ticket histories, identifying customer intent, sentiment, and open questions with one click. AI Writing Assistant
: Helps agents rewrite, polish, or translate drafts directly in the ticket editor.
: Allows for the creation of background "agents" to automate routine tasks like routing and categorizing. Recent Community & System Add-ons Community developers often release add-ons as
(Zammad Package Manager) files. Recent active community projects include: Mail Date Header
: A technical assistance add-on to display the original mail "Date" header directly in Zammad (Active January 2026). Telnyx SMS Notification : Integration for Telnyx SMS. TableSearch : Enables searching database tables via REST API. Zammad Community Core Workflow & Integration Updates Nested LDAP Groups
: Added support for recursive group mapping, allowing admins to include users from subgroups automatically. Advanced Webhooks
: Now supports Bearer tokens and additional HTTP methods, enabling Zammad to trigger complex external processes or even communicate with its own API. Role-Based Reporting
: Access to specific reporting metrics can now be restricted to specific user roles.
For the latest technical updates or to learn how to build your own addon, you can check the Zammad Community Forum Zammad System Documentation specific type of integration (like CRM or telephony), or do you need help installing a .szpm package News, Updates, Releases - Zammad
2026 * Security Release. Zammad 7.0. 1 & 6.5. 4. Our latest security updates address vulnerabilities in Zammad versions 7.0 and 6. Major release: Zammad 7.0 with AI features 4 Mar 2026 —
White Paper: Extending the Reach of Modern Helpdesks with Zammad Add-ons Executive Summary
As digital service demands grow, the standard "out-of-the-box" helpdesk often falls short of specific organizational workflows. Zammad, a leading open-source helpdesk system, addresses this through a robust ecosystem of integrations and modular features. This paper explores the latest trends in Zammad add-ons—specifically focusing on AI automation, low-code integration, and specialized productivity tools—that transform it from a simple ticketing system into a comprehensive service desk. 1. The Evolution of the Zammad Ecosystem
Traditionally, helpdesks were siloed databases of customer issues. Today, Zammad emphasizes a "smooth workflow" philosophy through several core extension paths:
Built-in Productivity Features: Tools like Text Modules and Macros act as internal add-ons to speed up response times.
Third-Party Integrations: Native support for platforms like Zabbix or Checkmk allows Zammad to act as a central monitoring hub.
API-First Development: The Zammad REST API enables custom-built "Add-ons" that sync external databases or automate ticket creation. 2. New Frontiers: AI and Low-Code Automation A basic understanding of Ruby on Rails, as
The most significant "new" development in the Zammad world is the integration with AI and automation middleware:
The AI Bridge: Recent implementations use n8n and Ollama to bring Large Language Models (LLMs) into the support workflow. This "add-on" approach allows for: Automatic ticket categorization and sentiment analysis.
Drafting AI-generated responses based on previous documentation.
Core Workflows: The introduction of Core Workflows allows admins to create custom logic—such as making specific fields mandatory based on ticket ownership changes—without writing Ruby code. 3. Top New Feature Add-ons for 2025/2026
Based on the latest Zammad documentation and community roadmap, these extensions provide the highest ROI for support teams:
Advanced Time Accounting: Enables precise tracking of billable hours directly within ticket articles for better resource management.
Knowledge Base Customization: New tools for managing public menus allow the helpdesk to function as a full-scale customer portal.
Security Add-ons: Enhanced Single Sign-On (SSO) and authentication integrations protect helpdesk data while streamlining agent login. 4. Implementation Strategy
For organizations looking to develop or implement new Zammad add-ons, the following steps are recommended:
Requirement Audit: Identify if the need can be met by Core Workflows or if it requires an external API integration.
Community Consultation: Check the Zammad Feature Request forum to see if a similar add-on is already in development.
Scalable Deployment: Utilize Docker or Kubernetes to manage service restarts and ensure high availability when adding new custom scripts. Conclusion
The future of Zammad lies in its ability to be customized. Whether through native "productivity features" or external "AI-driven middleware," these add-ons are essential for teams looking to provide proactive rather than reactive support.
The development roadmaps from major vendors hint at these releases:
Zammad is no longer just a "free alternative to Zendesk." With this wave of new addons released in late 2025 and early 2026, it has become a best-in-class enterprise platform.
Did we miss your favorite new addon? Let us know in the comments below, or contribute your own module to the GitHub repository.
Ready to upgrade? Check your Zammad version (zammad --version) and start exploring the addon store today.
Disclaimer: Addon names and features are based on the current trajectory of the Zammad open-source community and roadmap predictions. Always backup your database before installing third-party packages.
Zammad Add-ons are not revolutionary. They are evolutionary. They take a solid, reliable car (Core) and add the leather seats, adaptive cruise control, and premium sound system (Add-ons). You can drive without them, but you won't want to.
Rating Breakdown:
Final Score: 8.6/10 – Highly Recommended for growing teams.
Note: I am not affiliated with Zammad. I just migrated from Jira Service Management and haven't looked back.
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
: 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
john@gmail.com and john@company.com create two profiles.What it is: A native integration with OpenAI’s GPT-4 (or local LLMs like Llama 3) that sits inside the ticket editor. New Features:
Why it’s a game-changer: This addon has reduced average handling time (AHT) by 40% in beta tests. Unlike generic browser extensions, this addon respects Zammad’s internal user roles and permissions.
