Henglos IO
Studio

Export and import

Move a workflow between instances as a .hio file.

A workflow exports to a single .hio file you can share, back up or import into another Henglos IO instance.

Export

In the Hub, open a workflow's … menu and pick Export (.hio). If it's open in the studio, the export holds what's on screen.

Import

In the Hub, press Import and pick a .hio. Henglos IO:

  1. checks the platform version it was made for is available,
  2. installs the board and components it lists — the exact versions — into your library, unless you already have them,
  3. creates the workflow. If you already have one by that name, it's renamed Name (2).

An import fails, naming the package, when one can't be installed — it was removed from its registry, it's private, or it doesn't support the platform version.

What's inside

A .hio is a zip:

FileHolds
manifest.jsonThe format version, the workflow's name and description, the platform version, and the packages it needs (npm name, version, registry)
workflow.jsonThe workflow itself — actions, configurations, wires, variables, notes, positions, platform overrides

No package code travels in the file — packages are installed from their registries on import. Registry tokens are never exported.

On this page