Skip to main content
Join

Osticket Plugins

osTicket plugins extend the core functionality of this open-source help desk, allowing you to add features like advanced authentication, email integration, and storage management without modifying the base source code. Essential Core Plugins

Official plugins are typically distributed as .phar files by the osTicket Team:

Authentication (OAuth2, LDAP/AD): Crucial for modern security, these allow users and agents to sign in using Microsoft, Google, or Active Directory credentials.

Storage (S3, Filesystem): Moves ticket attachments out of the database and into the local filesystem or Amazon S3 to prevent database bloat.

Audit Trail: Tracks all activity within the system, providing a historical log of ticket changes and agent actions.

Language Packs: Essential for international teams, providing localized interfaces for multiple languages. Installation & Configuration

Installing a plugin is a straightforward process involving the server's file system and the osTicket admin panel:

Download: Get the .phar file from the official download page or authorized third-party developers.

Upload: Place the file in your osTicket installation’s include/plugins/ directory. osticket plugins

Install: Log in as an Admin, navigate to Admin Panel > Manage > Plugins, and click Add New Plugin.

Enable: Once installed, select the plugin and choose Enable from the "More" dropdown menu.

Configure: Click the plugin’s name to enter specific settings, such as API keys for OAuth2 or bucket names for S3 storage. Key Maintenance Tips

File Permissions: Ensure the web server has read/write permissions for the include/plugins/ directory, or plugins may not appear in the admin list.

PHP Extensions: Some plugins require specific PHP extensions (like php-phar) to be enabled on your server to function.

Updates: When upgrading osTicket, always check for matching plugin updates. Using outdated authentication plugins after a core update is a frequent cause of login failures.

Community "Mods": Unlike official plugins, community "mods" often require manual code edits. These are harder to maintain during system upgrades compared to standard .phar plugins. Plugins issue - osTicket Forum

Installing a plugin is a manual process that involves placing files in your server's directory. the plugin (usually as a file) from a trusted source like the official osTicket downloads the file to the include/plugins folder in your osTicket installation directory. to your help desk and go to Admin Panel > Manage > Plugins Add New Plugin and select the one you uploaded to install it. osTicket plugins extend the core functionality of this

the plugin by clicking on its name in the list, setting the status to , and saving your changes. Popular Community Plugins

Beyond the core auth and storage plugins, the community has built several powerful integrations: Notifications: Microsoft Teams connectors for real-time ticket alerts. Authentication: LDAP/Active Directory and OAuth2 for modern login security. and Filesystem storage plugins to keep your database small. AI & Automation: Advanced tools like AI-driven ticket routing

that use OpenAI to categorize tickets based on subject and body. Creating Your Own Plugin

If you need custom functionality, you can build your own. Note that official documentation for newer versions (1.17+) is limited, so reviewing the official GitHub repo is the best way to learn. Plugin Structure: Every plugin needs a plugin.php

file containing metadata like name, version, and the entry point class.

Use signals (hooks) to trigger actions. For example, you can hook into ticket.create

to send a custom SMS notification when a new ticket is opened. Packaging: Once coded, plugins are often packaged as files using the PHP Phar extension to make them easier to distribute. How to create a plugin? - osTicket Forum

There is no such documentation/guides available. There used to be but the Plugin system has changed since Multi-Instance Plugins ( osTicket Forum osticket-plugin · GitHub Topics 6. Knowledge Base Auto-Suggest

osTicket plugins allow you to extend the core functionality of your help desk without modifying the primary source code. They are typically distributed as .phar files and handle tasks ranging from authentication to automated ticket management. Core & Popular Plugins

The osTicket team maintains several official "Core" plugins, while the community provides various third-party integrations. Upgrade Overview (v1.15) — osTicket 1.15 documentation

An Introduction to osTicket Plugins: Extending Your Help Desk Functionality

osTicket is widely regarded as one of the most popular open-source support ticketing systems available. It is loved for its simplicity, clean interface, and the fact that it is entirely free to use. However, many administrators find that the "stock" version of osTicket, while functional, often lacks specific features required for modern business workflows.

This is where osTicket plugins come into play. Plugins are software add-ons that integrate with the core osTicket system to extend its capabilities, bridge gaps in functionality, and streamline support operations.

9. Multi-Brand / Multi-Company

1. What are osTicket Plugins?

osTicket is a popular, open-source support ticket system. While powerful out-of-the-box, plugins extend its core functionality—adding features like SLA automation, custom reporting, integrations with external apps (Slack, Jira, CRM), authentication methods (LDAP, OAuth), and advanced notification rules.

Note: osTicket itself uses the term "Plugin" for its extension architecture (introduced in v1.10+). Some community add-ons may also be called "mods" or "patches."

Communication & Notification

6. Knowledge Base Auto-Suggest