Visual and Python Workflows

Modern EKB workflows come in two builder styles. You can create them yourself on the Tools canvas, or ask Autopilot (Build mode) to author them for you. This page covers how the two styles differ, how Autopilot fits in, and how to read the flowchart and summary views. For the classic V1 vs V2 product lines and migration, see Workflows overview and Workflow Builder V2.

​

Visual vs Python at a glance

A Python badge on a workflow in the Tools list means it is a code-mode (v3) workflow.

​

Creating a workflow

​

Build with Autopilot (recommended for either style)

1. Open your project (not the read-only Autopilot system project).
2. Use Autopilot in Build mode, or open Tools and start Build workflow with AI / the Autopilot create flow.
3. Describe what the workflow should do (you can attach files for context).
4. The create dialog shows whether Autopilot will build a Workflows v3 / Python or Workflows v2 / Visual workflow by default.
5. Autopilot plans, asks clarifying questions as needed, builds the workflow, and you can keep chatting to refine it.

Who controls Visual vs Python for Autopilot creates?
A Super Admin setting — Default new Autopilot workflows to Workflows v3 — chooses the default:

• On — Autopilot creates Python / code mode workflows by default
• Off — Autopilot creates Visual (v2) workflows by default

Manual blank workflow creation stays on the Visual builder.

​

Create manually (Visual)

1. Go to Tools.
2. Use New Flow / create a blank custom tool.
3. Add a trigger, drag nodes onto the canvas, connect them, run, then publish.

Details: Workflow Builder V2.

​

Autopilot-built workflows

When Autopilot builds a workflow in Build mode it typically:

1. Clarifies the trigger, steps, apps, and outputs
2. Creates the workflow in Visual or Python mode (per the platform default above)
3. Configures steps / Python source
4. Validates and tests where applicable
5. Hands you a summary of what was created

You can continue in the same chat: refine steps, fix failures, or switch to Agent mode to run or reason about the result without further authoring. See How Autopilot Works.

​

Docked Autopilot in the editor

For Python (code mode) workflows, Autopilot stays docked on the editor canvas so you can describe changes while watching the flowchart and (in Developer view) the source update. For Visual workflows, use Autopilot chat / “create with AI” flows to author and iterate; the canvas remains the place you drag and configure nodes.

​

Flowchart and summary views

​

Flowchart (Python workflows)

Python workflows render as a readable flowchart:

• Plain-English step labels (not only raw code identifiers)
• Connected apps called out on the flow
• Collapsible loop and branch cards for complex control flow
• Overview vs Developer detail: Overview emphasizes the business flow; Developer exposes the Python source alongside the graph

The same flowchart is used when inspecting a past run, with per-step status overlaid so you can see what executed, skipped, or failed.

​

Summary (Visual and Python)

Both Visual and Python workflows support a summary view — an at-a-glance description of what the workflow does, with structured steps. Summaries are generated/updated in connection with publishing; if you change the workflow after publish, the summary may need a fresh publish to stay current. Super Admins can configure which model writes workflow summaries and step notes (platform model settings).

​

When to use which

​

Related

• Workflows overview — V1 vs V2 product lines
• Workflow Builder V2 — Visual canvas how-to
• Autopilot overview — what Autopilot can build
• Autopilot Modes — Agent vs Build
• EKB as MCP — Builder — same build surface from Claude / Cursor
• 2.4.0 changelog — release note for Visual and Python Workflow Builder