Skip to main content

Manage plugins

Plugins provide the job types (connectors) your Builders can use, and some provide connection types. You control which plugins are enabled for your organization and which version new jobs use.

What this solves

Builders need the right connectors available on a consistent version. Without central control, job types are missing when a workflow needs them, or jobs quietly run on versions that differ across the org.

The plugin catalog​

The Plugins area lists each plugin with its category, version, and job types. Search by name or filter by category to find one, then open it to see its details and the connection types it provides.

Enable or disable a plugin​

To enable or disable a plugin, complete the following steps:

  1. Go to Plugins and find the plugin.
  2. Use its enabled toggle to turn it on or off for your organization.

What's on by default:

  • Built-in job types (Run Command, Run Script, Wait for File), internal ones (Null Job, Workflow Container), and legacy LSAM are enabled out of the box.
  • The relay-side REST connectors — OpCon MFT, OpCon RPA and EASE — are enabled out of the box too. Enabled is not the same as usable: each also needs a relay that reports it can serve that agent type, and a registered agent.
  • External plugins (such as the SQL Database Executor) are disabled by default and must be turned on before Builders can use them.

Versions​

A plugin can have more than one version available; the default version is what new jobs pick up. Set the default when you want new jobs to move to a newer version.

Good to know
  • If a Builder says a job type (often SQL) "isn't there," the usual cause is that its external plugin hasn't been enabled yet.
  • Disabling a plugin removes its job types from new jobs. Check what's already in use before turning one off.

Related topics