Zammad Addons [verified] Online

The "interesting story" behind Zammad add-ons is rooted in its open-source philosophy: major features often start as paid custom add-ons for specific clients and eventually graduate into the standard free version for everyone. The Evolution of Add-ons

Zammad’s development model often turns private needs into public tools:

The "Success Story" Cycle: Companies like SER Solutions once found specific functions missing in Zammad. They paid to have them developed as custom add-ons. Instead of keeping them proprietary, Zammad integrated these features into the core software so the entire community could benefit.

Community-Driven "Packages": In the community, add-ons are often referred to as "packages". While official documentation for creating them is sparse, power users in the Zammad Community share custom-built integrations, such as: Telnyx SMS Notification: Integration for SMS alerts. One Tab Only: A utility to manage browser tab behavior. TableSearch: A tool to search database tables via REST. The Shift to Built-in Power (AI & Beyond)

While traditional "add-ons" exist, Zammad's strategy has shifted toward building powerful integrations directly into the core or using webhooks:

AI Revolution: With Zammad 7.0, high-demand "add-on" style features like Ticket Summaries, Sentiment Analysis, and AI Agents were added as modular core features.

n8n & Local AI: Users are now "extending" Zammad without traditional coding by using n8n as a bridge. This allows for complex workflows—like using local AI models (e.g., Ollama) to automatically route tickets to IT or Sales based on content.

Third-Party Authenticators: Zammad natively supports over ten "add-on" style login providers, including Microsoft 365, Google, and GitHub, making external authentication seamless. Customization Options zammad addons

If you can't find a ready-made add-on, Zammad provides professional services to build what you need:

Feature Development Workshops: Zammad offers Implementation Workshops to help companies design custom integrations or extensions that fit their specific tech stack.

API-First Approach: Because Zammad is "API-first," many users build their own "add-ons" externally by polling the Zammad REST API to sync data with ERP systems or custom dashboards. Place to browse addons? - Lobby - Zammad - Community

7. Conclusion

Zammad addons are a powerful mechanism for tailoring the helpdesk system to specific organizational needs. While the core system is sufficient for general ticketing, the addon ecosystem is essential for advanced ITSM workflows, external system integration, and security compliance.

However, the open nature of the ecosystem requires diligent management. Organizations must balance the desire for feature-rich environments against the maintenance overhead of keeping third-party packages compatible and secure.

End of Report

Webhook Expansion

• Trigger: Ticket create/update
• Send to: Zapier, Make, n8n, custom API
• Example:

  POST /webhook-endpoint
  Body:  ticket_id, title, customer_email 
  

C. Custom Feature Extensions

These addons do not connect to external systems but alter Zammad’s behavior. The "interesting story" behind Zammad add-ons is rooted

• Custom Field Handlers: Advanced logic for processing custom object data.
• UI Themes: Skins and layout modifications for branding purposes.
• Automation Enhancements: Complex schedulers or triggers not covered by the standard scheduler module.

Conclusion: Which Zammad Addons Do You Need Today?

Do not install addons for fun—install them to solve pain points.

• Startup on a budget? Skip the paid tier. Use the Community Slack integration and GDPR Helper.
• Growing team with compliance needs? Pay for the SLA and Reporting addons to keep management happy.
• Contact center? The CTI addon is non-negotiable.
• Unique workflow? Build a Make.com automation before you build a custom Rails engine.

Zammad is a phenomenal core system, but "Zammad addons" are the secret sauce that turns it from a ticketing system into your business's operating system for customer happiness. Explore the official docs, check out GitHub repos tagged zammad-plugin, and start extending today.

Have you developed or used a specific Zammad addon that changed your workflow? Let us know in the comments below.

In the context of the Zammad helpdesk, "add-ons" generally refer to two distinct concepts: official premium features for paid subscribers and a framework for technical extensions (packages). 1. Official Zammad Add-ons Zammad recently formalized "add-ons" as a benefit for Enterprise and Corporate subscribers Current Availability : Add-ons currently take the form of higher priority for custom feature requests

or advanced features already provided in the standard software for these tiers. Future Roadmap : Zammad plans to release pre-built, premium features

as add-ons that will not be available in the community (open-source) version. 2. Technical Extensions (Packages)

For developers, Zammad supports a package system that allows extending the core functionality. : Extensions are typically distributed as (Zammad Package Manager) files. Development & Maintenance : As of late 2023, there is no official developer documentation End of Report

for building upgrade-safe modifications. Developers often have to reference existing integrations in the Zammad GitHub repository Third-Party Connections : Specialized platforms like

provide "add-on" connections to sync Zammad with external ERP or CRM systems via API. Zammad Community 3. Native "Add-on" Features (Integrations)

While not always labeled as "add-ons," Zammad includes several modular features that can be enabled to expand its capabilities: AI Integration : Features like AI Ticket Summary

and an AI Writing Assistant to help agents handle complex tickets. External Data : Integrations for GitHub and GitLab to sync issues directly into the helpdesk. Asset Tracking i-doit integration

allows linking company assets (servers, licenses) directly to support tickets. Zammad User Documentation specific functionality to add to your Zammad instance, or are you interested in developing your own extension?

Docs for plugins/upgrade-safe modifications? - Zammad - Community

4. Marketplace / Third-Party Paid Addons

| Addon | Purpose | Vendor | |-------|---------|--------| | Zammad Jira Sync | Bi-directional ticket sync | CodeSprouts | | Zammad Power BI Dashboard | Advanced analytics | Zammad Consulting Partners | | SAML SSO (Enterprise) | SAML 2.0 auth (Okta, Azure AD) | Zammad GmbH | | Zammad GDPR Tool | Auto-anonymize user data | Community premium |

Note: SAML SSO and some enterprise addons require a Zammad Enterprise subscription.

The Zammad + Make.com Hub

Using the Zammad REST API, you can build automations that behave like native addons:

• CRM Sync (Salesforce/HubSpot): When a ticket is closed in Zammad, automatically log a "Support Case" in your CRM.
• Calendar Booking: When a customer selects "Urgent" in a form, automatically book a time block in a Google Calendar (e.g., "Manager review required").
• Jira/Linear Bridge: Create a developer ticket in Jira when a Zammad ticket is tagged with "Bug."