Zammad Addons Link

Maximizing Your Helpdesk: The Ultimate Guide to Zammad Addons and Integrations

Zammad is a powerhouse of open-source support, but its true strength lies in its ability to grow beyond its core features. Whether you call them addons, packages, or integrations, these extensions allow you to tailor your helpdesk to your team's specific workflow.

While Zammad does not yet have a centralized "app store" or marketplace like some competitors, it offers a robust ecosystem of built-in integrations and a framework for custom-built packages. 1. Built-in "Addons": Core Integrations

Zammad comes pre-equipped with numerous integrations that function as native addons. These are maintained by the Zammad team and can be activated directly from the Admin Panel under System → Integrations.

Communication Channels: Expand how customers reach you with addons for Telegram, Facebook, WhatsApp Business, and SMS (via Twilio).

Authentication & Security: Connect your user database with LDAP/Active Directory or enable Single Sign-On (SSO) via SAML, OpenID Connect, and OAuth (Google, GitHub, etc.).

Asset & IT Management: The i-doit integration allows you to link physical and digital assets directly to support tickets, perfect for IT service desks. Productivity Tools: zammad addons

Knowledge Base: A native addon for creating internal or external documentation.

AI Writing Assistant: A recent addition that helps agents polish, shorten, or translate replies.

Calendars (iCal): Sync ticket deadlines and reminders with your personal calendar. 2. Third-Party Automation Connectors

If a native integration doesn't exist, you can use automation platforms that act as a "bridge" between Zammad and thousands of other apps.

n8n: Offers a dedicated Zammad node to connect with over 1,000 services for complex, self-hosted automation.

Integrately: Provides ready-to-use "recipes" for Zammad, connecting it to tools like Microsoft Dynamics 365, HubSpot, and Slack. Maximizing Your Helpdesk: The Ultimate Guide to Zammad

Zapier: While not explicitly detailed in every snippet, it is a standard choice for connecting Zammad to webhooks and common SaaS tools. 3. Custom Zammad Packages (.szpm)

For advanced users, Zammad supports Packages (using the .szpm format). These are custom developments that can change the interface or add entirely new backend logic. One Tab Only Addon - Development - Zammad - Community

Zammad refers to its plugins or extensions as Packages or Add-ons. While a formal marketplace or "cookbook" documentation does not currently exist, you can prepare and develop features using specific structural formats. Preparing a Zammad Feature

To "prepare" a feature for Zammad, you typically follow a specific development workflow focused on the ZPM (Zammad Package Module) format.

Define the Structure (.szpm): Create a Source Zammad Package Module (.szpm) file. This JSON-based file defines metadata like your feature's name (format: Vendor-Feature), version, and the specific locations of the files you are modifying or adding.

Develop Locally First: It is recommended to modify local files on a development system before bundling them into a package. This allows you to identify the necessary JS controllers and templates required for your specific functionality. For Official Addons (SMS

Build the Package (.zpm): Convert your source file into a Zammad Package Module (.zpm). This is a compressed, production-ready version where your code is included as base64-encoded strings within the JSON file.

Handle UI Changes: If your feature makes UI changes, ensure you run rake assets:precompile during installation so Zammad can recognize the new assets. Core Extension Methods

If you are preparing a feature that doesn't require a full package, Zammad offers several built-in ways to extend functionality: Building a custom integration - How to start? - Development

For Script-based Extensions

Place in /opt/zammad/scripts/
Make executable: chmod +x script.rb
Schedule via cron if needed

1. Check the Version Compatibility

Zammad releases major updates twice a year. An addon written for Zammad 4.0 will not work on Zammad 6.0. Always check the zammad_version requirement in the manifest.

The Hidden Gem: The "Zammad Addons" GitHub Search

If the official marketplace doesn't have what you need, the community is building on GitHub. Search for zammad-addon or zammad-plugin.

Warning: These are often "abandonware." Before installing a community addon:

Check the last commit date (look for < 1 year old).
Scan the code for hardcoded API keys or malicious scripts (a standard security practice in open source).
Read the "Issues" tab to see if other users reported bugs.

The ITSM Addon (Incident Management)

Zammad is great for standard support, but the ITSM (IT Service Management) addon adapts it for teams following ITIL standards.

Features: Problem management, change requests, and asset management (CMDB).
Best for: Internal IT helpdesks supporting employees, not external customers.

Installation best practices (concise)

Test in a staging environment identical to production.
Follow addon vendor docs; prefer package managers or Git tags over master branch.
Apply least-privilege credentials for external services.
Run load tests for high-throughput channels.
Create automated backups and a rollback plan.
Monitor after deployment for errors, queue backlog, and search degradation.

For Official Addons (SMS, Voice, WhatsApp)

No install – just configure via Admin UI → Channels

Part 1: Native vs. Community vs. Custom Addons

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