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
Zammad has recently evolved from a standard helpdesk into an AI-powered support platform with the release of Zammad 7.0 in March 2026. This major update introduces native AI features that act as internal "addons" to streamline support workflows without compromising data privacy. Latest Core Features & AI "Addons" (Zammad 7.0) zammad addons new
Zammad now includes built-in intelligent support tools that function as advanced addons for your daily work:
AI Integration: Features like automatic summary generation and message drafting are now available, allowing you to use language models while retaining full control over your data.
Enhanced Knowledge Base: For teams managing extensive documentation, the Knowledge Base now supports "long paper" formats and rich-text editing, making it a more powerful internal wiki.
Public/Internal Notes: Admins and agents can now attach internal or public notes when adjusting settings or performing bulk actions to provide context for workflow changes. Third-Party Integrations & Updates
Facebook Channel 2026: A new integration for "Facebook Login for Business" has been introduced. Note that personal and business integrations are now handled as distinct parameters within the app setup.
Advanced SSL Verification: Since version 6.2, administrators must manually enable SSL verification for all channels and webhooks. You can now add custom CA certificates directly through the UI.
Custom Object Attributes: You can create your own "addons" by adding custom fields to tickets, users, or organizations. These now support more granular permissions and better ordering. Technical Compatibility & Security
System Migration: Versions before Zammad 7.0 require MySQL/MariaDB users to migrate to PostgreSQL to continue receiving updates.
Security Releases: The latest security patches for both version 7.0 and 6.5 (back-ported) were released in April 2026 to address critical vulnerabilities.
OS Support: Legacy operating systems like CentOS 7 and Ubuntu 18 are no longer supported for newer Zammad versions.
For detailed configuration of these new features, refer to the Zammad Admin Documentation or check the latest Release News on the official Zammad website. Zammad Addons New - 13.208.242.202
Introduction
Zammad is a popular open-source helpdesk software that provides a comprehensive platform for managing customer support requests. While the core software offers a robust set of features, users can further extend its functionality with add-ons. In this paper, we will explore new and innovative Zammad add-ons that can enhance the user experience and provide additional value to organizations.
Background
Zammad is a web-based helpdesk software that allows organizations to manage customer support requests, incidents, and issues. It offers features such as ticket management, customer management, and reporting. However, as with any software, there may be gaps in functionality or specific requirements that are not met by the core software. This is where add-ons come into play.
Types of Zammad Add-ons
There are several types of Zammad add-ons available, including:
New and Innovative Zammad Add-ons
Some new and innovative Zammad add-ons include:
Benefits of Zammad Add-ons
The benefits of using Zammad add-ons include:
Conclusion
Zammad add-ons offer a powerful way to extend the functionality of the core software, providing organizations with a competitive edge in customer support. New and innovative add-ons, such as AI-powered chatbots and advanced reporting and analytics, can enhance the user experience, improve performance, and drive business success. As the Zammad ecosystem continues to evolve, we can expect to see even more innovative add-ons emerge, further solidifying Zammad's position as a leading helpdesk software solution.
Recommendations
Based on the analysis of Zammad add-ons, we recommend:
By following these recommendations, organizations can unlock the full potential of Zammad add-ons and take their customer support to the next level.
What it is: An enhancement to Zammad’s basic SLA module. The "New" Difference: Standard Zammad tracks first response time and close time. New Dynamic SLA addon adds:
Zammad out of the box is fast, beautiful, and functional. But Zammad with the right new addons is unstoppable.
Whether you need AI to draft replies, a two-way sync with your CRM, or an SLA clock that respects weekends, there is now a stable, modern addon waiting for you.
Your Next Step: Log into your Zammad admin panel. Navigate to Admin > Addons (or Marketplace). Search for "GPT," "SLA," or "Teams." Start your 14-day trial today. Your agents—and your customers—will thank you.
Are you using a new Zammad addon we didn’t mention? Email us or drop a note in the official Zammad community forum to keep the conversation going.
Keywords integrated naturally: Zammad addons new, new Zammad addons, Zammad AI addon, Zammad Teams integration, Zammad marketplace 2025, Zammad migration tools.
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
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. In Zammad, "addons" are officially called Packages
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.
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.
Why it matters: Previously, advanced automation required Ruby knowledge or custom scripts. The new breed of addons brings visual workflow builders into Zammad. Integration Add-ons : These add-ons enable integration with