Zammad | Addons

These are developed by partners or the open-source community to bridge gaps between Zammad and other business tools.

Sometimes, an "addon" isn't a plugin but an integration via Zapier, Make (Integromat), or n8n. Zammad has a powerful REST API, meaning you can effectively build your own addons without writing Ruby code.

Before diving into specific tools, it is critical to understand the three layers of extensibility in Zammad. zammad addons

Modularity: The primary benefit is the ability to keep the core system lean. You don't have to install features you don't need. If your company doesn't use GitHub, you simply don't install that package, reducing potential software bloat.

Updatability: Historically, modifying open-source helpdesks meant "forking" the code, which made upgrading to new versions a nightmare of merging code conflicts. Zammad’s package system separates the core code from the addon code. When you upgrade Zammad, the system handles the migration of your installed packages automatically, preserving your custom functionality. These are developed by partners or the open-source

Compliance and Security: Using certified addons (especially those developed or vetted by the Zammad team) ensures that data privacy standards, such as GDPR compliance, are maintained. This is critical for organizations handling sensitive customer data.

These modify the front-end UI.

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: