Skip to main content

Importing & Exporting

Automation Hub lets you take a workspace, collection, or job out of one environment as a portable file and bring it into another. Use this to promote automations from dev to production, share a job with a teammate, or keep a backup of your work.

note

This is the Automation Hub import/export, which moves workspaces, collections, and jobs. It is separate from the Global Configurator import/export, which moves connections, variables, and other configuration records. See Global Configurator for that flow.

Every list view in Automation Hub — Workspaces, Collections, and Jobs — has Import and Export buttons in its toolbar.

Exporting​

Select Export on a list to open the export panel.

Choose Format
Pick how the export is written
Choose Records
Export the selected records or all of them
Download
Automation Hub generates the file and downloads it

Format​

The export panel asks you to Select the format:

FormatWhat you get
JSONA structured .json bundle — the format you import back into Automation Hub
CSVA .csv file, useful for reviewing the contents in a spreadsheet
ZIPA .zip archive, used when the export carries file or certificate contents that cannot fit in a flat file

Records to Export​

You also choose Records to export:

OptionWhat it exports
Selected RecordsOnly the items you ticked in the list. The label shows how many are selected
All RecordsEvery item in the current list

Select a format and a record scope, then choose Export. The file downloads with a name like job_2026-07-24.json.

Importing​

Select Import on a list to open the import panel. The panel is titled for what you are importing — for example Import Job.

What You Provide​

Import typeWhat you choose firstFile
Workspace--A previously exported file
CollectionThe target WorkspaceA previously exported file
JobThe target Workspace, then CollectionA previously exported file

Use Browse to pick the file. Automation Hub accepts an exported JSON file, or a ZIP archive for exports that bundle files or certificates. Choose Import to upload it.

If the imported items do not depend on any existing records, the import finishes immediately and Automation Hub confirms Successfully Imported.

Resolving Dependencies​

An exported job often references records that live outside it — a connection, a global variable, an API suite, and so on. When you import into a new environment, those referenced records may already exist there under different IDs. Instead of guessing, Automation Hub opens a Resolve dependencies wizard so you can link each imported dependency to an existing record.

1. Upload
You upload the exported bundle
2. Link existing records
Map each dependency to a record that already exists here
3. Confirm & import
Run the import with your links applied
note

This is a linking flow, not a skip / overwrite / rename flow. You are telling Automation Hub which existing record each imported reference should point to — you are not choosing whether to replace anything.

How Linking Works​

The wizard groups the conflicts by type (connections, variables, API suites, and so on). For each imported dependency it shows:

  • The source record from the bundle — its name and any identifying details.
  • A list of candidate existing records that could match it, each shown as a selectable option with its name and date. Where several records match, you select one per item to link. A show older matches toggle reveals additional candidates when there are many.

A progress indicator at the bottom tracks how many items you have linked — for example 3 of 5 linked. You must link every dependency before you can finish: the Confirm & import button stays disabled until all items are resolved.

Finishing​

Once every dependency is linked, choose Confirm & import. Automation Hub imports the bundle with your links applied, so the imported job points at the correct existing records in this environment, and confirms Successfully Imported.