How the AI Generate Buttons Work (Scripts, Workflows, and Playbooks)

CloudRadial AutomationAI includes an AI Generate button in three places: the Designer (to generate a script), the Workflows page (to generate a whole workflow), and the Playbooks page (to generate a playbook). Each button turns a plain-language prompt into a working result, but the quality of that result depends heavily on what the AI can "see" in your workspace when it runs. This article explains, for each button, what it does, what context it relies on, and how to set yourself up for a good generation. It is written for workspace users who build automations.

• Generate a Script (Designer)
• Generate a Workflow (Workflows Page)
• Generate a Playbook (Playbooks Page)
• Model, Timing, and Limits
• Getting the Best Results

Generate a Script (Designer)

In the Designer, the Generate Script action turns a natural-language prompt into a single script in the language you choose — PowerShell, Python, or C#. You can also use it to refine a script you already have.

What It Relies On

When it generates a script, the AI is given:

• Your prompt
• Any installed Extensions you select — the AI reads each selected extension's usage guidance and the names of the secrets that extension needs to authenticate. Select every integration the script should use.
• The input variables available at that point in the workflow — the binding tokens from the trigger and from earlier steps (for example, trigger.ticketId or nodes.fetch-tickets.output.results)
• The current contents of the script, when you are refining an existing one
• The runner contract for the language you picked — the AI is taught exactly how a Runner reads inputs, loads and validates secrets, writes outputs, calls AI from inside the script, and reports logging and failures

Tips and Caveats

• If you select no Extensions, you get a generic script with no integration guidance
• Only reference Extensions you have actually installed. A made-up integration will fail at run time when the Runner cannot load its secret.
• Refine iteratively — generate a first draft, then ask for specific changes rather than rewriting the prompt from scratch

Generate a Workflow (Workflows Page)

On the Workflows page, the AI Generate button turns a prompt into a complete multi-step Workflow, plus a plain-language summary of what it built. The AI both writes the Workflow and checks its own work before returning it.

What It Relies On

When it generates a Workflow, the AI is given:

• Your prompt and an optional Workflow name
• The script language you chose, which is applied to every script step
• Every Extension installed for your workspace — marketplace and custom — including each one's description, usage guidance, and required secrets
• Your available agents — both installed catalog agents and custom agents
• Your knowledge folders
• The full vocabulary of Workflow step types — start, PowerShell/Python/C# script, AI prompt, agent, knowledge write, knowledge consolidate, condition, for-each, and end — along with each step's options such as timeouts, retries, and parameters
• The data-binding patterns used to wire one step's output into the next step's input (for example, {{ nodes.fetch-tickets.output.results }})
• The runner contract, so any script steps it writes are runnable

After drafting the Workflow, the AI runs a review-and-repair pass — it validates the result, and if it finds problems it repairs and re-checks, up to three rounds, before returning the finished Workflow.

Tips and Caveats

• The more relevant Extensions and agents you have installed, the better grounded the result
• Everything the AI references — every agent, Extension, and knowledge folder — must be real. Invented references either fail validation or fail when the Workflow runs.
• Only published Workflows are visible to the AI. Drafts are not included as building blocks.

Generate a Playbook (Playbooks Page)

On the Playbooks page, the Generate with AI button turns a prompt into a complete, goal-directed Playbook — a sequence of "plays" that launch Workflows and run agents toward a goal. On success, the generated Playbook is saved as a Draft, exactly as if you had imported it.

What It Relies On

When it generates a Playbook, the AI is given:

• Your prompt, an optional Playbook name, and an optional home knowledge folder
• Your published Workflows, by name and description — drafts are excluded
• Your saved agents, by name and description
• Your knowledge folder names
• The Playbook structure — the Goal, Steps, Repeat, and Finish model; the play types (Workflow, agent, wait, approval, and reflect); per-play options such as what to do on failure and what to capture to knowledge; the template bindings for referencing earlier plays, the goal, the briefing, and the trigger; the repeat modes; and the finish rules

Like Workflow generation, Playbook generation runs a validate-and-repair loop of up to three rounds. If it succeeds, it saves a Draft Playbook. If it cannot produce a valid Playbook, it returns a clear error and saves nothing.

Tips and Caveats

• Publish the Workflows you want the Playbook to use before you generate. Draft Workflows are invisible to it.
• Every Workflow name and agent the Playbook references must match a real one exactly
• A home knowledge folder name must match exactly, or you can leave the Playbook company-wide

Model, Timing, and Limits

All three buttons share the same underlying behavior:

• Generation uses your region's active AI model on Azure AI Foundry, run at a low temperature so the output is focused and consistent
• When you start a generation, the work runs in the background and the page shows live progress — grounding, generating, reviewing, and repairing — while it polls for the result. A Workflow or Playbook that goes through repair rounds can take a minute or more.
• Generation consumes AI usage, which counts toward your workspace's Usage Credits
• Content-safety filtering can occasionally block a repair step. When that happens, you receive the best result produced so far, with any remaining issues noted.

Getting the Best Results

The single biggest factor in generation quality is what real building blocks the AI can see. Before you generate:

• Install the Extensions the automation should use, so the AI knows the available integrations and their secrets
• Publish the Workflows and save the agents you want a Workflow or Playbook to build on
• Write a specific prompt — state the trigger, the systems involved, and the desired outcome
• Review and test the result. Generated scripts, Workflows, and Playbooks are a strong starting point, not a substitute for verifying the automation before you rely on it.