Addons — Zammad
Zammad addons — Report
Summary
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.
Many users search for addons for things Zammad already does natively if you enable them in the settings: Zammad Package Best Practices - Development zammad addons
3. Cloud vs. Self-Hosted Reality Check
- Zammad Cloud users: You can ONLY install Marketplace addons. You cannot install custom Ruby Gems. You are limited to the official/approved list.
- Self-Hosted users: You can install anything, but you are responsible for security patches and debugging conflicts.
- Custom triggers and schedulers (Zammad’s automation + extended scripts)
- External workflow engines (n8n, Node-RED) via API
Suggested priority addons (typical deployments)
- Authentication (SSO/LDAP) — high priority for enterprise.
- Channel connectors needed by support teams (email, chat, WhatsApp) — medium–high.
- Telephony integration if calls are core — medium.
- Reporting/BI connector — medium.
- Backup/monitoring tooling — high.
Meanwhile, a separate addon called Auto-Responder+ , which Lena had installed as a companion, didn't just send a canned "we got your email" reply. It analyzed the error log attached to the ticket, recognized the firmware signature, and sent a personalized message: “We’ve identified a conflict with GPS sync on firmware v2.1. A patch is being deployed. Your drone will auto-update in 2 hours. Here’s a 20% discount code for your trouble.” Zammad addons — Report Summary Zammad is an
The "Slack Alerts" Addon
Zammad sends email notifications, but your team lives in Slack. Zammad Cloud users: You can ONLY install Marketplace addons