- Custom nodes — new building blocks that appear in the flow editor, alongside the built-in ones. Use them in flows and co-workers just like any other node.
- Integrations — a secure connection to an external service. Connect it once in your workspace settings and the plugin’s nodes can act on that service on your behalf.
- Triggers — start flows automatically when something happens in an external system.
- Knowledge-base sources — pull documents from systems Noxus doesn’t cover out of the box into your knowledge bases.
Safe by design
Each plugin runs in its own isolated environment, separate from the rest of Noxus. That means a plugin can bring whatever it needs to do its job, a misbehaving plugin can’t affect the rest of your platform, and plugins only reach your data through controlled, permission-scoped interfaces. Credentials you connect stay per workspace — each workspace connects its own.Getting a plugin
Plugins are installed by an administrator, once per deployment, and then become available across it. You can install one from:- the public marketplace of Noxus plugins,
- a Git repository, or
- a package upload.
Learn more
Build your first plugin
A step-by-step tutorial: scaffold, develop, package, and install.
How plugins work
The developer overview: components, the manifest, and the sandboxed runtime.