Skip to content

Home

Introduction

Development

IDEs

Services

Service manager

API Explorer

Importing Integrate packages

Packages can be exported in TORO Integrate. The ZIP archive produced by the export process can be used by other developers in order to obtain a copy of the package in another instance. This makes it easy to build your integrations on top of what others have already done. These ZIP files are simply your packages, as they were in the file system, but compressed. A single ZIP file can contain multiple packages.

From the file system

To import a package, you must have the ZIP file for it. This guide assumes that you already do. In order to launch the Package import wizard, follow the steps below.

Importing a package

  1. Right click the instance which will be receiving the copy of the package, select Import > Integrate Package from the appearing context menus. This will make the wizard pop out.
  2. Fill out the following details in the wizard:
    • Integrate Instance - the instance where the package will be copied to; this, by default, is the instance you did a right click on
    • File - the archive file of the package
    • Start on import - a checkbox indicating whether the package, if successfully imported, should immediately start up or not.
  3. Click Finish to begin the import process.

Importing a package Drag and drop the package ZIP archive from your file system manager to any blank space in the Coder Navigator view.

From the Marketplace

The TORO Marketplace is TORO's official platform for sharing integrations and the like — packages included. To import packages from the TORO Marketplace, do the following:

Steps on how to import packages from the Marketplace dialog

  1. To launch the Marketplace dialog, click the Marketplace icon from the toolbar. It's the fifth icon from the left. It's also possible to access the Marketplace dialog under the Help menu.
  2. Select Integrate Package from the dropdown menu to show only Integrate packages.
  3. Optionally, you can use the search bar to help you filter the packages shown in the window.
  4. Select the package(s) you want to import using checkboxes.
  5. Select the instance where you want the selected packages to be installed.
  6. Click the Install button at the bottom of the dialog. Another dialog for configuring your installation items will pop-up. Since only scripts and API schemas are configurable, we won't need to do anything; just click Finish.

Give TORO Integrate a good few seconds to install your packages. If all goes well, you should be able to see your newly imported package(s) in the Coder Navigator view. However, it's also possible for your installation to fail. When this happens, a pop-up dialog will be shown to let you know what went wrong.

Steps on how to import packages from the Marketplace dialog

  1. To launch the Marketplace dialog, click the Marketplace icon from the toolbar. It's the last icon from the top.
  2. Select Integrate Package from the dropdown menu to show only Integrate packages.
  3. Optionally, you can use the search bar to help you filter the packages shown in the window.
  4. Click the green Install link of the package you want to install.
  5. In the appearing dialog, configure your package import settings and once done, click the Finish button.
  6. Repeat steps #4 and #5 until you've been able to install all the packages you want.

Give TORO Integrate a good few seconds to install your packages. If all goes well, you should be able to see your newly imported package(s) in the Coder Navigator view. However, it's also possible for your installation to fail. When this happens, a notification will be shown to let you know what went wrong.

A modal showing the TORO Marketplace items available for you to download

  1. Click the inbox icon located on the top-right side of the UI. This will launch a modal showing the extensions and plugins available for you to download.
  2. Select a package you want to install and click the Download button.

Namespace conflicts

Be wary of namespace conflicts. A namespace conflict occurs when two files (including those from different packages) have the same file extensions and namespace, regardless of character case.

If you try to import a package that will induce namespace conflicts, that package will be disabled and will remain disabled until the namespace conflicts have been resolved.