CloudRadial AutomationAI lets you move a workflow between workspaces as a portable .yml file. You export a workflow from the Designer and import a .yml file from the Workflows page as a new workflow. This article is for workspace users with the Admin role or higher.
Exporting a Workflow
Open the workflow in the Designer and select Export in the toolbar. AutomationAI downloads the workflow as a shareable .yml file. The file captures the workflow definition so it can be re-created in another workspace.
Importing a Workflow
On the Workflows page, select Import and choose a workflow .yml (or .yaml) file. AutomationAI creates a new workflow from the file.
If the file contains node types that this version of AutomationAI does not recognize, those nodes are dropped and the rest of the workflow is imported. A warning reports how many were skipped and which types, in the form "{count} node(s) of unknown type were skipped: {types}." Review the imported workflow in the Designer and rebuild any skipped steps before you publish or deploy it.
What Is Not Carried in the File
A share file describes the workflow itself, not the workspace around it. Attached companies are deliberately left out: a pinned company points into the exporting workspace's own company registry, so carrying it would leave an imported step aimed at a company the receiving workspace has never registered.
On export, AutomationAI drops any pinned company from Agent, script, and For Each nodes. On import it does the same, so a file written by an older build or edited by hand cannot reattach a company either. Company behavior that does not name a specific company is preserved, including a step set to iterate companies or to include all companies.
After importing a workflow that used company scoping, open it in the Designer and pin the companies you want before you publish it. For more on company records, see the article on managing companies and per-company credentials.
Comments
0 comments
Please sign in to leave a comment.