Zammad — Addons

Zammad addons are typically Ruby on Rails engines that hook into the core application. They interact with the system via defined APIs and can modify the database schema, user interface, and backend logic.

Key Characteristics:

Do not install addons for fun—install them to solve pain points.

Zammad is a phenomenal core system, but "Zammad addons" are the secret sauce that turns it from a ticketing system into your business's operating system for customer happiness. Explore the official docs, check out GitHub repos tagged zammad-plugin, and start extending today.

Have you developed or used a specific Zammad addon that changed your workflow? Let us know in the comments below.

Zammad does not have a traditional "plugin marketplace" or "app store" like WordPress or Jira. Instead, the platform is designed to be extensible through Packages (ZPM), Webhooks, and a robust REST API. 1. Zammad Package Manager (ZPM)

ZPM files are the closest thing to a traditional "addon." These are community-developed packages that modify the Zammad source code to add new features or UI elements. zammad addons

How they work: You upload a .zpm file through the Zammad admin interface (System > Packages).

Where to find them: Most are hosted on GitHub. Popular community contributors include D-Fens and Pragmatic Industries. Common Examples:

Advanced LDAP Sync: Enhanced user synchronization beyond the core features. Custom UI Themes: Minor adjustments to the look and feel.

Extended Reporting: Specialized dashboards for specific KPIs. 2. Built-in Integrations

Before looking for an external addon, check the Integrations section in your Admin panel. Zammad includes many native "addons" that just need to be toggled on.

Communication Channels: WhatsApp (via Twilio/MessageBird), Telegram, Facebook, and Twitter. Zammad addons are typically Ruby on Rails engines

Authentication: Google, Microsoft 365, GitHub, and LinkedIn SSO. System Tools:

Checkmk / Nagios / Icinga: For automated ticket creation from server monitoring alerts. Elasticsearch: Powering the advanced search functionality.

Slack / Rocket.Chat: Pushing notifications from tickets to team chat. 3. API & Webhook Extensions

For professional environments, "addons" are usually built as external microservices that talk to Zammad via the REST API.

Webhooks: Zammad can "push" data to an external URL whenever a ticket is created or updated. This is used to trigger external actions, like updating a CRM or sending a custom SMS.

Custom Development: Since Zammad is built on Ruby on Rails, developers often write custom scripts to automate data migration or sync with proprietary databases. Crucial Warnings for Addons Zammad is a phenomenal core system, but "Zammad

Updates: Because ZPM packages modify the core code, they can break during a Zammad version update. Always check the compatibility of an addon before upgrading your Zammad instance.

Support: Community addons are not officially supported by Zammad GmbH. If an addon breaks your database, you may have to manually roll back to a backup.

Self-Hosted vs. SaaS: Custom .zpm packages can only be installed on self-hosted (On-Premise) versions. If you use Zammad's managed Cloud service, you are limited to the built-in integrations and API/Webhooks.

Zammad is an open-source helpdesk/ticketing system (Ruby on Rails + Elasticsearch). Addons extend its functionality via integrations, plugins, and customizations. This report covers common addon categories, notable integrations, deployment/maintenance considerations, and recommended steps for evaluation and installation.

Introducing third-party code into a helpdesk environment poses inherent risks.

  • Popular community / third-party:

    • Security is paramount. The core Zammad supports basic LDAP, but the advanced SAML (Single Sign-On) and OAuth addons allow connection to Okta, Azure AD, and Google Workspace.

    When no addon exists for your workflow, build one. Zammad is built on Ruby on Rails, making it highly modular.