Skip to main content

Export and Import Workflows in Torq

Learn how to export and import workflows in YAML format.

Updated yesterday

Overview

Workflows can be exported and imported in YAML format, allowing you to move automation between workspaces, back up configurations, or distribute workflows across teams. This enables reuse of existing automation logic without rebuilding workflows from scratch.

In addition to manual transfer, workflows can also be shared across workspaces for real-time collaboration. Export and import are best suited for migration and version control, while sharing is ideal for maintaining a single source of truth.

When exporting a workflow, Torq includes the workflow structure along with metadata such as description, tags, and section. When importing, Torq validates dependencies and helps resolve conflicts to ensure a smooth transition.

What is included in export

Exporting a workflow packages all required components into a YAML file for reuse.

  • Workflow structure

  • Workflow description

  • Tags

  • Section

If the workflow includes nested workflows or custom components, these are handled during import as part of dependency resolution.

Conflict handling during import

When importing workflows, Torq checks for naming conflicts and existing dependencies in the destination workspace.

You can choose how to handle conflicts:

  • Keep original: Keep existing workflows unchanged. The imported workflow is added as a duplicate, and existing nested workflows are reused.

  • Override original: Replace existing workflows with the imported versions.

  • Duplicate: Create new copies of nested workflows and update the imported workflow to reference them.

By default, automated imports use the Keep original option unless specified otherwise.

Custom steps and integrations behavior

When exporting workflows that include custom steps or integrations, these components are included in the export package.

  • Custom steps and integrations are automatically created in the destination workspace during import.

  • If the same version already exists, it is reused and not duplicated.

  • If changes are detected, a new version is created.

How to use

The following sections explain how to export and import workflows, resolve issues, and migrate workflows between workspaces.

Export a workflow

You can export a workflow from either the Workflows page or the Workflow Designer.

From the Workflows page

  1. Open workflows: Navigate to Build > Workflows.

  2. Locate workflow: Find and select the workflow you want to export.

  3. Open options: Click the three-dot (...) menu.

  4. Export workflow: Select Export or Export published to download the YAML file.

From the Workflow Designer

  1. Open workflow: Open the workflow in the Designer.

  2. Open options: Click the three-dot (...) menu. in the top-right corner.

  3. Export workflow: Select Export or Export published to download the YAML file.

Import a workflow

Import workflows into your workspace from a YAML file.

  1. Open workflows: Go to Build > Workflows.

  2. Start import: Click Create > Import workflow in the top-right corner.

  3. Select file: Choose the YAML file from your device.

  4. Resolve conflicts: Select a conflict handling option if prompted:

    • Keep original

    • Override original

    • Duplicate

  5. Complete import: Confirm the import.

    If included in the export, the workflow description, tags, and section are also imported. If the section does not exist, it is created automatically.

Automate workflow import

You can automate imports using the Import a workflow step.

  1. Use the Import a workflow step in your workflow.

  2. (Optional) Set conflict mode: Configure the Conflict handling mode parameter:

    • Keep original (default)

    • Override original

    • Duplicate

Troubleshoot import and export issues

Export failures

If an export fails:

  1. Run the workflow: Use Run Workflow or Test Run to identify issues.

  2. Fix errors: Resolve any failures in the workflow.

  3. Retry export: Export again after successful execution.

Import failures

Import issues are typically caused by problems in the YAML file:

  • Invalid manual edits

  • Circular dependencies in nested workflows

  • References to non-existent workflows

To resolve:

  1. Validate YAML structure.

  2. Fix dependency issues.

  3. Re-export or use a previous version.

Migrate workflows between workspaces

To migrate workflows without using sharing, use a dedicated migration workflow (see below).

  1. Download template: Download the Migrate workflows to new workspace workflow.

  2. Import workflow: Go to Build > Workflows and import it.

  3. Configure parameters:

    • Select the source workspace integration.

    • Select the destination workspace integration.

  4. Run workflow: Execute the migration workflow to transfer all workflows.

Did this answer your question?