Plugin Development
HelpNest has a WordPress-style plugin framework. A plugin is a folder with a manifest and a provider class. It can add dashboard menu items, routes, pages, scheduled jobs, Artisan commands, database tables, and react to events or change data through hooks. All without editing core files.
This guide is for PHP developers. If you only want to use the plugins that ship with HelpNest, see Premium Plugins.
Two plugin channels
| Channel | Location | Notes |
|---|---|---|
| Legacy modules | core/Modules/* | Installed from a zip file through the admin panel. Used by the first-party SMS gateway, support ticket and similar modules. |
| Plugin framework | core/plugins/* | The framework documented here. Use it for all new work. |
Both appear on Admin → Plugins Manage → All Plugins. The legacy modules are cards with zip upload; the framework has its own Plugin Framework table.
What's in this guide
- Anatomy and manifest: folder layout,
plugin.jsonfields, the provider class. - Turning plugins on and off: lifecycle, the admin screen and Artisan commands.
- Hooks, menus and routes: extend the UI and react to events.
- Hooks reference: every action and filter explained, plus Laravel events and how to fire your own hooks.
- Assets, settings and permissions: CSS and JS, stored options, admin permissions.
- Build your first plugin: a complete working example.
- Testing: how the framework is covered by tests and how to test your plugin.
The first-party plugins in core/plugins (Analytics Pro, CRM Sync, Integrations Hub, Knowledge Sources, Privacy Pack, Store Import) are real examples of every pattern described here. Reading their provider classes is the fastest way to learn.