AiHummer
English▾
Sign inAccount
v1.6.x▾
{ }Swagger

Plugins, marketplace, connections & secrets

v1.6.x · updated 2026-11-13

This page covers four related Web UI screens that extend the instance and hold credentials: Plugins/Marketplace, Connections and Secrets.

Install a plugin in 4 steps

Plugins are channel connectors, services, integrations and skills. Installing is a single click:

  1. Open the “Plugins” screen and go to the “Catalog/store” block.
  2. Find the plugin you want (there is search and filters by kind and state). Official modules carry an Official badge and come first.
  3. Click “Install”. What you’ll see: the card shows a progress bar and refreshes itself until the plugin turns “online”.
  4. Click “Configure” — a form built from the plugin manifest opens (e.g. a token field for a channel connector). Fill it in and save.

What’s next: after install a channel connector appears on the Channels screen, and an integration/connection on the “Connections” screen. Until installed, a plugin does not appear on those screens.

[!NOTE] Community plugins. Besides the official catalog, you can add third-party (community) sources in the “Sources” block: enter a catalog name and URL, enable it and sync. Plugins from such sources are verified against the instance trust-store — on first load the operator approves the author’s key. Details: Install & updates.

Plugins / Marketplace

The “Plugins” screen is the single install surface for all modules: channel connectors, services, OpenAPI integrations, skills and MCP are installed only here. Until a plugin is installed it does not appear on the “Channels” and “Connections” screens; once installed, its configuration shows up there.

  • Installed (shown first) — cards with logo, name, a kind badge and a status (online / error / deploying / blocked). Actions: Configure (a form built from the plugin manifest), Update to latest (when the catalog has a newer version), Uninstall (with confirmation; except built-ins). Modules with no visible settings fields — Einstein, for one — have no Configure button at all; only the update action is available. Banners may appear for “needs a public URL” and “not available on your plan”. The Einstein memory plugin is built-in: it is listed among the installed modules with a “Built-in” badge, never offered in the store and cannot be uninstalled.
  • Catalog/store — the full catalog, channel connectors included: official modules first, the rest sorted by installs. There is a search box and filters by kind (connector / service / integration / skill / MCP) and state (installed / not installed). A module not available on the current plan stays visible — instead of “Install” it shows an “Upgrade to unlock” link (the server answers HTTP 402, see Licensing).
  • During install/update the card shows a progress bar and the screen refreshes itself every few seconds until it settles.
  • Sources — the official source is pinned; private sources can be added (name + URL), enabled/disabled, removed and synced.

Details in Marketplace & plugins.

For the paid Marketplace plugin Web Widget 1.2.0 with Core 1.5.33 or newer, open Plugins → Web Widget → Configure. The existing public server address and the installation’s current workspace are filled automatically. In Websites connected to this chat, enter one full website origin per line, for example https://example.com; select the active agent for website visitors from this workspace. Scheme and non-default port must match the site; default ports and international domain names are normalized. An empty list disables external websites, and wildcards are rejected.

Use the colour picker and the button text, shape, size and position controls, then set the window theme, title, subtitle, greeting, input hint, width, height and corner rounding. The live preview shows the actual button and window and displays sample messages without running an agent or spending the model budget.

Save, reopen Configure, and copy the generated embed code into your website before </body>. Reload an allowed website and send a message. Visitors use the existing anonymous session limits and safe tools; an unlisted website cannot open a chat. If activation fails after saving, the settings remain saved and the plugin reports its failed status.

Connections (OAuth, multi-account)

The “Connections” screen is a personal store of external-service credentials.

  • My connections — service logo, format, label, status; a disconnect button.
  • Available — catalog entries scoped “personal”: OAuth services start authorization via redirect (on first use they ask for client_id/secret, which go into the vault); token services show manifest-declared fields (for example e-mail and token) and are saved as credentials.
  • + account — multi-account: each label is a separate connection of the same service.
  • A Devices block — the status of iOS device bridges.

More in Connections & OAuth.

Secrets (vault)

The “Secrets” screen is a write-only store: secret values are never read back. “+ New secret” is a modal with fields: scope, name, value (password). The list shows scope, name and a “set” badge plus delete. Secrets are used by plugins and agents without ever being revealed in the UI.

If it didn’t work

  • An “Upgrade to unlock” link instead of “Install” — the module isn’t available on your current plan (the server answers HTTP 402). Change plan or pick another module, see Licensing.
  • The card is stuck installing/errored — an install counts as successful only after the plugin’s health check; a broken plugin is not counted. Try reinstalling, details in Install & updates.
  • The plugin isn’t in the catalog — check the filters (kind/state) and search; for a third-party plugin, add and sync its source in the “Sources” block.
  • Can’t find an installed plugin’s settings — they appear after install: for channels on the Channels screen, for connections on “Connections”.

Next