Zammad Addons Repack

Here’s a practical guide to Zammad Addons — both official and community-driven — to extend functionality beyond the core helpdesk.

The Benefits of the Package System

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. zammad addons

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.

Key addon categories & examples

• Authentication & SSO
  • LDAP/Active Directory (built-in connector)
  • SAML / OAuth (for corporate SSO)
• Communication channels
  • Email (native), IMAP/SMTP tuning addons
  • Chat integrations (Webchat widgets)
  • Social media connectors (Twitter, Facebook via middleware)
  • SMS gateways (Twilio, Nexmo via API connectors)
• CRM / user data
  • Integrations with external CRMs (Salesforce, HubSpot) via webhooks or middleware
• Telephony / VoIP
  • Asterisk/FreeSWITCH integrations (screen-pop, call logging)
  • SIP providers via CTI connectors
• Automation & workflows
  • Custom triggers and schedulers (Zammad’s automation + extended scripts)
  • External workflow engines (n8n, Node-RED) via API
• Reporting & analytics
  • BI exports (CSV/JSON feed)
  • Dashboard extensions (Grafana / Prometheus exporters)
• File storage & attachments
  • External object storage (S3-compatible) adapters
  • Antivirus/filtration pipeline (ClamAV scanning hook)
• Security & compliance
  • Audit logging extensions
  • Data retention/encryption helpers
• UI / UX enhancements
  • Custom templates and frontend tweaks (assets & themes)
  • Custom ticket fields and dynamic forms
• Development & deployment
  • Backup/restore scripts
  • Monitoring (Prometheus exporters, healthchecks)
  • CI/CD deployment helpers (Docker/Kubernetes manifests)

For Community Ruby Gems:

Requires shell access to your Zammad server. Here’s a practical guide to Zammad Addons —

# SSH into your Zammad server
cd /opt/zammad
sudo gem install zammad-slack-integration
sudo zammad run rails r "Gem.refresh"
sudo systemctl restart zammad

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.

If you want, I can:

• produce a one-page install playbook for a specific addon (specify addon),
• audit a given addon repository for risks,
• or generate a staging test plan.

REPORT: Zammad Addons – Ecosystem, Functionality, and Strategic Implementation The Benefits of the Package System Modularity: The

Date: October 26, 2023 Prepared For: IT Management / Systems Administration Subject: Overview and Analysis of Zammad Addons (Extensions)

Deployment & maintenance concerns

• Compatibility: Ensure addon supports your Zammad version; many are version-sensitive.
• Upgrades: Custom plugins may break on Zammad upgrades—maintain a test environment.
• Security: Review third-party code; prefer signed packages or repository forks with active maintenance.
• Performance: Some integrations (especially chat and telephony) increase background job load and Elasticsearch usage—plan capacity.
• Backups: Back up database, Elasticsearch indices, uploaded files, and configuration before installing addons.
• Logging & monitoring: Enable detailed logs and monitor queue workers, Elasticsearch health, and memory/CPU.
• Support: Community addons may lack SLAs—consider commercial support for critical integrations.

1. The "CTI" Addon (Computer Telephony Integration)

Zammad’s core ticketing is ticket-centric, but the CTI addon makes it voice-centric.

• What it does: Integrates your SIP telephone system directly into Zammad.
• Key Features: Click-to-dial, automatic screen pops displaying caller history, call logging as a ticket, and voicemail transcription.
• Best For: Sales teams and high-volume support desks where voice is primary.

How to Choose the Right Zammad Addon (Without Breaking Zammad)

Adding too many plugins can slow down your ticketing system or cause conflicts. Here is a three-step filter before installing any addon:

B. Third-Party & Community Integrations

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

• Telephony (CTI): Integrations with providers like Placetel, Sipgate, or generic SIP interfaces for screen-popping and call logging.
• Monitoring (ITSM): Integrations with tools like Nagios, Check_MK, or Zabbix. These allow alerts from monitoring systems to automatically generate tickets.
• Source Control: GitHub and GitLab integrations for linking tickets to commits or merge requests.