Importing a workflow

You can import a workflow from a JSON file that was previously exported from a workflow. This allows you to re-create a workflow configuration in a different tenant.

When you import a workflow that uses tenant-specific data, the platform checks whether the referenced data exists in the destination tenant. If the data is not available (for example, the email addresses, scripts, or protection plans from the source tenant do not exist in the destination tenant), those fields are automatically reset to their default state, and a warning is displayed. You can proceed with the import, and then update the affected fields with data from the destination tenant.

When you import a workflow, it is added to the workflow list with Draft status, and with 'Imported' in the description.

Imported workflows do not have the Propagate setting enabled.

To import a workflow

Cyber Protection administrator or Cyber Protection Cyber administrator.

  1. Go to Automation > Cyber Studio > Workflows.

  2. In the toolbar, click Import.

  3. In the dialog, browse for the JSON file or drag and drop it into the dialog, and then click Import.

The platform validates the file. If the file contains critical errors, such as invalid JSON syntax or missing required fields, an error message is displayed and the import is stopped.

If the file contains non-critical issues, such as a deprecated action or a tenant-specific parameter, a warning is displayed. You can choose to proceed with the import.