Open Navigation

Importing / Exporting Workflows

Overview

When building a workflow in Tray.io, once you have validated it with your test service accounts and datasets, it is possible to export it and then import into another destination workflow - either in the same Tray.io account or in another account.

This is very useful in that it allows you to test workflows before putting them to real-world use.

Three key features of imported workflows are:

  1. Authentications are synchronized. The feature works on the basis that you use test authentications with your original workflow and live authentications with your destination workflow - when importing to the destination workflow you only need to create a new authentication the first time a particular service is imported and all subsequent imports will automatically map the authentications

  2. Workflow settings (properties panel operations, parameters and workflow config) are also synchronized and the settings from the original workflow will always override the settings in the destination workflow properties panel.

  3. After a first import has been made, you can work on new versions by editing and testing in the imported workflow, before exporting and importing to the destination workflow - as many times as you need

Note: the feature does not currently work with workflows that have dependencies - i.e. it does not work with callable workflows.

Also note that there may be discrepancies between the service accounts you are accessing - e.g. your Google Sheets live account may not have the same sheet as your Google Sheets test account. In this case you will have to manually set the sheet in the destination workflow.

Exporting a workflow

Exporting a workflow is done by clicking on the ellipsis in the top left of the builder and choosing export:

elipsis-export-workflow

This will then be downloaded as a json file to your local machine:

downloaded-json

You can then import the workflow into a newly created or already existing workflow by opening that destination workflow, clicking on the ellipsis and choosing import:

elipsis-import-workflow

You can then pick up the json file of the workflow you wish to import:

upload-json-file

On the first import you will then be asked to create authentications for any of the services included in the workflow (i.e. you will have used 'test' accounts in the imported workflow and will be using 'live' accounts in the new workflow being imported to):

import-create-new-auths

Note: when importing subsequent versions of the workflow, you will not have to create the same authentications again.

Points to note about imported workflows

Alerting Workflows

If you have an alerting workflow set in your original workflow:

  • If you are importing to a workflow in the same account, it will be linked to the same alerting workflow
  • If you are importing to a workflow in a different account, you will need to create an alerting workflow in that account and manually link to it in the destination workflow settings

Undoing imports

If you mistakenly import a workflow, or need to undo for any reason, you can do so with the Rollback Workflow History function.

Importing new workflow versions

To continue testing, editing and producing new versions of your workflow, use the following procedure:

  1. Edit and test the original workflow
  2. Export the edited version of the original workflow
  3. Import the exported json file to the same destination workflow

Be sure to bear the following points in mind when working with subsequent vesions of your workflow:

  • All configuration and details set in the destination workflow's properties panel will be overwritten - i.e. the new details you have set in the exported workflow will overwrite the details of the previous version in the destination workflow
  • Service connectors will not need to be re-authenticated in subsequent versions
  • Any new service connectors not present in the previous version will need to be authenticated
Was this article helpful?
Yes
No