This is a comprehensive technical and functional deep-dive into the Zammad addon ecosystem. It covers architecture, development paradigms, the marketplace landscape, and strategic considerations for deploying addons in a production environment.
However, with great power comes great responsibility. Developing and maintaining addons requires developer resources (Ruby/Vue.js skills) and a commitment to testing before every major Zammad upgrade. For the standard user, the Marketplace offers safe, pre-vetted tools; for the advanced enterprise, the lib directory offers a sandbox for limitless customization. zammad addons
Whether building a local or packaged addon, the anatomy remains largely the same. This is a comprehensive technical and functional deep-dive
If an addon needs an API endpoint (e.g., a webhook receiver), it mounts a route. Because Zammad uses an API-only backend for its frontend, addons often add endpoints to the api/v1 namespace. If an addon needs an API endpoint (e
⚠️ : Zammad does not have a plugin marketplace like WordPress or Jira. Most addons are either SaaS integrations, API scripts, or manually installed Ruby gems/overlays.
