Skip to main content

Install Putki plugins

Putki's own plugins (connectors such as HubSpot, Shopify and Actito, and tools such as Autodoc) are published on forge.putki.io. You can install them in Hop GUI from the Putki Marketplace, from the command line, or by hand from a zip. All three need a forge.putki.io account with access to your Putki subscription.

Most of these plugins are already in the Putki plugins download (plugins-<version>.zip). The Plugins table shows which ones are not.

You add the Putki Marketplace once. New versions of the plugins appear in it as they are released, and from Apache Hop 2.20 Hop GUI tells you when one is available for a plugin you have.

Before you start​

You need:

  • Apache Hop 2.19.0, the Hop version Putki 2026.09 is built on. See Installing Apache Hop. In the steps below, <hop> is the folder Hop is installed in: the one that contains hop-gui.sh and hop-gui.bat.
  • A forge.putki.io account with access to Putki downloads. If you can open the Putki releases page while signed in, you have it. If you get "page not found", ask your Putki contact to give your account access.
  • Your Forgejo username. If you sign in with GitHub, your Forgejo username can be different from your GitHub handle. It is shown under your avatar, top right, on forge.putki.io.

1. Create an access token​

The marketplace signs in with a token, not with your password.

  1. On forge.putki.io, open Settings → Applications.
  2. Under Generate new token, enter a name, for example putki-marketplace.
  3. Under Select permissions, set repository to Read. Leave everything else at No access.
  4. Click Generate token and copy the token. It is shown only once.

2. Add the Putki Marketplace​

  1. In Hop GUI, open Tools → Marketplace…, and go to the Repositories tab.

  2. Click Import from URL… and enter

    https://forge.putki.io/putki-hop/marketplace/raw/branch/main/putki-repo.yaml

    Hop shows what it downloaded. Click Yes to add it. It is added as a repository with id putki, after the Apache repositories; installs still find Putki plugins in it.

  3. Select the putki row and click Edit.

  4. Enter your Forgejo Username, and the token as Password.

  5. Click Save.

The token is stored in hop-config.json in your Hop configuration folder. It is obfuscated there, not encrypted.

On a machine without internet access, download the file from that URL elsewhere, and use Import… instead of Import from URL….

3. Install a plugin​

  1. Go to the Plugins tab and click Refresh. The Putki plugins are listed with category Putki and source putki.
  2. Select the plugin and click Install.
  3. Restart Hop GUI. Plugins are only loaded at startup.

If no Putki plugins are listed, see Troubleshooting.

Install from the command line​

On a server, or to script the installation, use the hop launcher in <hop> (hop.bat on Windows). Set your credentials as environment variables:

export HOP_MARKETPLACE_PUTKI_USERNAME=<your-forgejo-username>
export HOP_MARKETPLACE_PUTKI_PASSWORD=<your-token>

cd <hop>
./hop marketplace repo import https://forge.putki.io/putki-hop/marketplace/raw/branch/main/putki-repo.yaml
./hop marketplace query --repo putki     # list the Putki plugins
./hop marketplace install git-input      # install one

The variable names follow the repository's id, in capitals with - replaced by _: the putki repository reads HOP_MARKETPLACE_PUTKI_USERNAME, a repository with id putki-basic reads HOP_MARKETPLACE_PUTKI_BASIC_USERNAME, and so on. The id is shown on the Repositories tab, and by ./hop marketplace repo list.

Credentials entered on the repository in Hop GUI take precedence over these variables. Restart Hop GUI, Hop Server or any running process after installing.

./hop marketplace list shows the plugins the marketplace knows are installed, with their versions.

Get new plugin versions​

The Putki Marketplace always lists the newest version of each plugin for the Apache Hop version you run. Every plugin version is published for one Hop line: the 2026.09 plugins and their patch releases (2026.09.01, 2026.09.02, …) for Hop 2.19, the next release's plugins for the next Hop version. So on Hop 2.19 you see the newest 2026.09.x version of each plugin, and never one that needs a newer Hop.

A patch release does not always change the plugins. When it does not, the plugins stay at the version they were, and there is nothing to update.

To update a plugin:

  1. On the Plugins tab, click Refresh. A plugin with a newer version shows that version.
  2. Select it and click Uninstall, then Install. Installing over an existing version leaves both in place, so uninstall first.
  3. Restart Hop GUI.

From the command line: ./hop marketplace uninstall <plugin>, then ./hop marketplace install <plugin>.

The plugins that come in plugins-<version>.zip count as installed by the marketplace: the archive carries the marketplace's record of each one (in plugins/.marketplace). You update and uninstall them like any other. A plugin you unzipped by hand from its own zip has no such record: the marketplace cannot uninstall it, and Hop does not report updates for it.

The connector plugins (Actito, HubSpot, Odoo, Shopify) share plugins/misc/rest/rest-utils-<version>.jar, and each one's record includes it. Uninstalling one connector removes that file; install the connector you are updating again, or any other one, to put it back.

Update notifications​

From Apache Hop 2.20, the bell in the top right of the Hop GUI toolbar reports new versions of the plugins the marketplace knows are installed, without any configuration. Hop checks the Putki Marketplace in the background, with the username and token you entered in step 2. A notification such as Autodoc 2026.12.01 is available tells you which version you have; update the plugin as described above.

Notifications only report: they do not install anything. To turn them off, or to change how often Hop checks, open the Configuration perspective, Notifications tab. See Notifications in the Apache Hop manual.

New Putki releases are announced by a separate feed you add once: see Get notified of new Putki releases.

Apache Hop 2.19, which Putki 2026.09 is built on, has no notifications. There, click Refresh on the Plugins tab to see whether a newer version is listed.

Install a plugin by hand​

Without the marketplace, for example on a machine that cannot reach forge.putki.io:

  1. Sign in on forge.putki.io and open the Putki releases page.

  2. Open the release for your Putki version and download the plugin's zip, for example putki-actito-2026.09.zip. A patch release that did not change the plugins, such as 2026.09.01, has no plugin zips of its own: use the zips of the release it patches (2026.09).

  3. Unzip it into <hop>. The zip already contains the plugins/… (or lib/core/…) folders, so its files land in the right place. Do not unzip it into a folder of its own.

    unzip putki-actito-2026.09.zip -d <hop>

    The connector zips (Actito, HubSpot, Odoo, Shopify) each contain the same plugins/misc/rest/rest-utils-<version>.jar. When unzipping a second connector, replacing that file is fine.

  4. Restart Hop GUI.

To remove a plugin you installed by hand, close Hop GUI and delete its folder, listed under Plugins. A plugin installed with the marketplace is removed with Uninstall on the Plugins tab, or ./hop marketplace uninstall <plugin>.

Plugins​

PluginIn plugins-<version>.zipZipFolder in <hop>
Actitonoputki-actito-<version>.zipplugins/misc/actito
Autodocyesautodoc-<version>.zipplugins/misc/autodoc
Chatyeschat-plugin-<version>.zipplugins/misc/chat
Flywayyesflyway-<version>.zipplugins/actions/flyway
Git Inputnogit-input-<version>.zipplugins/transforms/gitinput
HubSpotyesputki-hubspot-<version>.zipplugins/transforms/hubspot
Lineage Graph Exportnolineage-graph-export-<version>.zipplugins/actions/lineage-graph-export
Odooyesodoo-<version>.zipplugins/misc/odoo
RDBMS Impactyesrdbms-impact-<version>.zipplugins/transforms/rdbms-impact
REST Utilsyesrest-utils-<version>.ziplib/core (shared libraries, not a plugin)
Shopifyyesputki-shopify-<version>.zipplugins/transforms/shopify
SQL Parseryessql-parser-<version>.zipplugins/transforms/sql-parser

Troubleshooting​

No Putki plugins in the list​

The Apache Hop plugins are listed but the Putki ones are not. Hop GUI shows no error for this. To see the reason, run in <hop>:

./hop marketplace query --repo putki

and look for a line Unable to download catalog from …:

  • HTTP 401: the username or token is wrong. Use your Forgejo username, not your GitHub handle or e-mail address, and check that the token has not been deleted.
  • HTTP 404: the credentials are missing, or they are accepted but cannot read the Putki downloads. Check that the token has repository: Read (a token with only other permissions, even write permissions, is refused) and that your account can open the Putki releases page.
  • HTTP 404 on a URL with v2026.09.01: you imported the Putki Marketplace while it pointed at a release without plugins. Repeat step 2: importing again updates the putki repository in place and keeps your username and token.

Also check that no old HOP_MARKETPLACE_PUTKI_USERNAME / HOP_MARKETPLACE_PUTKI_PASSWORD or HOP_MARKETPLACE_USERNAME / HOP_MARKETPLACE_PASSWORD variables are set in your environment. They are used whenever the repository in Hop GUI has no username and password of its own. A Hop GUI started from the macOS Finder does not see variables exported in your shell; enter the credentials on the repository instead.

A newer version is not listed​

Open the putki repository on the Repositories tab and look at its Catalog URL. If it contains releases/download, you imported the Putki Marketplace before it listed every release, and Hop holds on to the versions from that import. Repeat step 2: importing again updates the putki repository in place, clears those versions, and keeps your username and token.

The plugin does not appear after installing​

Restart Hop GUI. If you installed by hand, check that the plugin's folder is directly under <hop>, as listed under Plugins, and not inside an extra folder named after the zip.