For the complete documentation index, see llms.txt. This page is also available as Markdown.

Export and Import Workflows

AI Workflow Studio supports a new job-based export and import process for workflows, powered by App Sync. Resource connections and mappings are handled automatically, and dependencies are configured before an import is finalized.

To export Workflows:

  1. In the Aisera Admin UI, navigate to AI Automation > AI Workflow Studio.

  2. Do one of the following:

    1. Open a specific workflow, select the More Options menu, then select Export.

    2. Select one or more workflows from the list view, then select Actions > Export.

  3. Navigate to Settings > Jobs, then and wait for the export job to complete.

  4. Select the Link to download in the Output field of the completed export job to download the exported workflows

To import Workflows:

  1. Switch to the target app and navigate to AI Automation > AI Workflow Studio.

  2. From the Workflows List page, open the Import dropdown and select Import.

  3. Select the exported workflow file from your local machine. A Pre-Import job will start automatically.

  4. Navigate to Settings > Jobs and wait for the Pre-Import job to complete.

  5. Navigate back to AI Automation > AI Workflow Studio and select Configure Imported Resources at the top of the page to open the Resource Configuration Mapping Wizard.

  6. Review and configure any integration or data source mappings, then select OK to confirm.

  7. Monitor the final import job in the Job List page.

  8. Once complete, navigate back to AI Automation > AI Workflow Studio to verify the imported workflows.

If no mappings appear in the Resource Configuration Mapping Wizard, select OK to proceed directly to the final import job.

Imported workflows are set to Published status by default. Testing and any additional configuration should be completed before putting them into use.

Workflow Export/Import Includes Sub-Flows

The Workflow Export/Import feature now allows you to include sub-flows within your export/import package.

NOTE: After importing, you must publish each sub-flow before publishing the parent flow.

Last updated

Was this helpful?