Zammad Addons New May 2026

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.

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. zammad addons new

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. Since "piece" is not a standard Zammad command,

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 addons are essentially Rails Engines. You can create a skeleton plugin using the standard Rails plugin generator.

Run this inside your Zammad development folder (or wherever you keep your code):

rails plugin new zammad_addon_my_new_feature --mount-at=/my_new_feature --full

For Zammad to recognize the addon, it must be registered in app/models/setting.rb or via an initializer if it's a backend feature. Are you trying to create a specific type of addon (e

If you are creating a backend addon (e.g., a new channel or scheduler), you would add an initializer in your engine:

lib/my_new_feature/engine.rb

module MyNewFeature
  class Engine < ::Rails::Engine
    isolate_namespace MyNewFeature
# Register the addon with Zammad
initializer "my_new_feature.register_addon" do |app|
  # Zammad specific registration logic usually goes here
  # For example, adding a new channel or ticket hook
end

end
end

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+).

This is where Zammad stops being a "ticket tracker" and starts being a business intelligence tool.

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.

Released: July 2024 Templating gets a massive upgrade. Instead of one static signature, this addon uses Liquid logic.