Skip to main content

Installing Plugins

This article outlines how to download and configure a plugin on Informer 5. Plugins must be downloaded and configured on the server hosting the Informer deployment. The first time you install a plugin you also log in to Entrinsik's npm repository; contact Support for the repository credentials.

Check compatibility first

Before installing any plugin, contact Support at i5support@entrinsik.com to verify compatibility with your target Informer version.

Windows​

Stop the Informer service and any Node.js processes still running. Then open an elevated PowerShell window and change to the Informer application directory.

Version Differences
  • For Informer 2026.1.x and higher, the default application directory is C:\Entrinsik\Informer5 Server\runtime\app
  • For Informer 2025.2.13, 2025.2.14, and 2025.2.15, the default application directory is C:\Entrinsik\Informer5\i5.
  • For Informer 2025.2.12 and earlier, the default application directory is C:\Entrinsik\Informer5.

The first time you install any plugins, log in to the repository:

npm config set registry https://docker.entrinsik.com/repository/npm/
npm adduser --registry https://docker.entrinsik.com/repository/npm/

When prompted, enter the credentials Support provided.

Then install the plugin:

npm install <plugin name> --legacy-peer-deps -E

To install a specific plugin version, add it to the npm install command, replacing x.y.z with the version:

npm install <plugin name>@x.y.z --legacy-peer-deps -E

Afterward, edit the config.json for the Informer deployment and add a definition for the plugin.

Version Differences
  • For Informer 2026.1.x and higher, the config.json is found in C:\Entrinsik\Informer5 Server\data
  • For Informer 2025.2.15 and earlier, the config.json is found in C:\Entrinsik\Informer5

The end result after making this change should look like:

{
  "db": {
    ...db information...
  },
  "elastic": {
    ...elastic information...
  },
  "redis": {
    ...redis information...
  },
  "plugins": {
    "<plugin-name>": {}
  }
}

For example, to add the Salesforce plugin:

"plugins": {
  "@entrinsik/salesforce": {}
}

If the plugin's documentation says it takes options, add those as well:

"plugins": {
  "<plugin name>": {
    "<option>": "<value>"
  }
}

Finally, restart the Informer Windows service.

Linux (Docker)​

Edit the config.json for the Informer deployment and add a definition for the plugin:

"plugins": {
  "<plugin name>": {}
}

For example, to add the Salesforce plugin:

"plugins": {
  "@entrinsik/salesforce": {}
}

There may be additional details to set in config.json, as described in the plugin's documentation.

After making any required changes, restart the Informer containers.

If your custom plugin requires special repository access that the default Informer user does not have, see Custom NPM user for plugin access.

If the plugin does not load​

  • Check the logs. There is one file per role, and a plugin that fails to load says so there.
  • A plugin stopped loading after an upgrade. If this is on a Windows deployment, confirm the plugin folder is still nested in the application files. If the upgrade laid down a fresh runtime, install the plugin again and restart the service.

As always please contact support at i5support@entrinsik.com if there are any issues.