Creating your first workflow in the Designer

A workflow in CloudRadial AutomationAI is a repeatable automation you build visually in the Designer. This article walks an Admin or Owner through creating a workflow, adding and connecting nodes, and saving a draft. It covers the canvas and palette; for the configuration details of each node type, see Workflow nodes overview.

We'll follow six main steps:

1. Creating a workflow
2. Getting to know the Designer canvas
3. Adding nodes from the palette
4. Connecting nodes
5. Tidying and editing
6. Saving your draft

Step 1: Creating a Workflow

Why are we doing this? This creates the empty workflow you will build in.

Open Workflows from the sidebar and select New. AutomationAI creates an empty workflow and opens it in the Designer. To bring in a workflow someone shared with you instead, use Import and select a .yml file.

Step 2: Getting to Know the Designer Canvas

Why are we doing this? Knowing the canvas and toolbar means you are not hunting for controls while you build.

The Designer is the visual editor for a workflow. A new workflow starts with a Start node already on the canvas; the Start node is the entry point and cannot be deleted. The toolbar across the top shows the current draft version, undo and redo, and the actions you use as you build:

• Properties opens the workflow's properties, where webhook and schedule settings live
• Rearrange auto-arranges the nodes on the canvas; choose left-to-right or top-to-bottom
• Publish turns the current draft into an immutable published version
• Export downloads the workflow as a shareable .yml file
• Save changes saves the draft and returns to the Workflows list
• Cancel returns to the Workflows list without saving

Step 3: Adding Nodes From the Palette

Why are we doing this? Nodes are the steps of your automation, so this is where the workflow takes shape.

The node palette groups the available nodes into sections:

• Scripts: PowerShell Script, Python Script, and C# Script
• AI: AI Prompt and Agent
• Logic: Condition
• Flow: End

To add a node, drag it from the palette onto the canvas, or select it to drop it in place. The For Each node is also available for running a step once per item in a collection. The Start node is not in the palette because it is created for you.

Step 4: Connecting Nodes

Why are we doing this? Connections set the order steps run in, which is what turns a set of nodes into a workflow.

Each node has connection handles on its edges. Drag from a node's output handle to another node's input handle to create a link, which sets the order in which steps run. A Condition node has two outputs, true and false, so you can branch the flow down separate paths.

To change an existing connection, drag either end of it onto a different node's handle to re-target it, or drop it in empty space to delete it. A Condition branch keeps its true or false side when you re-target it. Each reconnect or delete is a single undo step.

Step 5: Tidying and Editing

Why are we doing this? A tidy canvas is easier to follow, and each node needs its settings before it will do anything.

Use Rearrange to auto-arrange the nodes without changing any settings. Select a node to open its editor, where you configure it and can test it.

Step 6: Saving Your Draft

Why are we doing this? Saving keeps your work as an editable draft; you publish later, when you are ready to deploy.

Select Save changes to store your draft as editable work. When you are ready to deploy, you publish a version. See Understanding workflow versions (draft vs. published).

If you are still having trouble, we're here to help! Submit a ticket here for assistance, and don't forget to check our status page to ensure there are no outages in your area.