Converting an AI Playground run into a workflow

The AI Playground answers questions and completes goals as a one-off, ad-hoc assistant. When a run does something you want to repeat (on a schedule, from a webhook, or as part of a larger automation), CloudRadial AutomationAI lets you convert that run into a new draft workflow in one step, keeping the goal, model, and extension access the run used. This article is for workspace users who build automations (Admin or Owner Role).

The AI Playground was previously called Ask AI. Existing links to /ask-ai still work and redirect to the new location.

• When to Convert a Run
• Converting from the AI Playground History
• What Carries Over
• What You Get
• Editing the New Workflow

When to Convert a Run

The AI Playground is the fastest way to try something, but each run stands alone. Convert a run into a workflow when you want to keep it: run it on a schedule, trigger it from a webhook, add steps around it, or hand it to a runner as a deployment. Converting saves you from rebuilding the goal and re-selecting the same extensions by hand.

Converting from the AI Playground History

Open AI Playground > History (/ai-playground/history) to see your past AI Playground runs. You can start a conversion two ways:

• Use the Convert to workflow action on a run's row in the history grid
• Open a run to view its detail, then choose Convert to workflow in the run detail panel

Either way, AutomationAI opens the new-workflow dialog with a suggested name already filled in from the run's goal. Pick a folder, adjust the name if you like, and confirm. The new workflow opens in the Designer.

The history list shows AI Playground runs only. Runs that came from a workflow, a playbook, or a designer node test are not listed here and are not convertible.

What Carries Over

The new workflow is seeded from the run so it behaves the same way:

• Goal: the instruction the run was given becomes the agent step's goal
• Model: the same AI model the run used
• Extensions: the exact set of extensions the run was allowed to use. If the run had access to every tool, so does the workflow; if it was scoped to a specific set, that same scope is applied; if it used no tools, none are enabled.

You can review the extension scope on the run's detail before converting, so you can confirm what the workflow will inherit.

What You Get

Conversion creates a new draft workflow version with a minimal, valid graph: a Start node, an Agent node seeded from the run, and an End node. Nothing is published or deployed automatically. The workflow is a draft you can shape before it runs anywhere.

Editing the New Workflow

Once the workflow opens in the Designer, treat it like any other: rename it, edit the agent's goal or model, add nodes before or after the agent, then publish a version and create a deployment when you are ready. See Creating your first workflow in the Designer for the full authoring flow.