Skip to main content
Plugins let you add new capabilities to Noxus without waiting for them to be built into the platform. A plugin is a small package, installed into your deployment from a Git repository, a file upload, or the public marketplace, that brings its features along with it. A single plugin can add any of the following:
  • 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.
Noxus renders every plugin’s settings and configuration forms automatically, so plugins feel native — there is no separate app to learn.

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.
Once installed, a plugin’s nodes, integrations, triggers, and sources are ready to use.

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.