Flow Click-by-Click

Flow Click-by-Click (formerly Automation Studio) is the ServiceNow flow-building module of Code Copilot. It generates flows, subflows, flow actions, and migrations — backed by your choice of AI model — and can deploy genuinely runnable Flow Designer flows straight onto your instance. This page documents the module exactly as it appears on screen.

What is Flow Click-by-Click

The module has two complementary jobs:

Author & plan — describe a flow and the AI returns a validated definition plus a precise, click-by-click implementation guide. Nothing is written to your instance — you create the flow yourself in the ServiceNow Flow Designer builder using the guide (change 2026-08-01: drafts are no longer auto-created). This is Create New Flow.
Deploy ready-made — clone a curated, pre-tested golden template into a brand-new, published, runnable flow on your instance. This is Deploy Runnable Flow (and its blue-green sibling, Replace with Runnable Version). Both are admin-only features.

In short Use Create New Flow for anything custom (you get a build guide), and Deploy Runnable Flow when a template already matches what you need (it deploys, no manual building).

Page layout & tabs

The page is one centred column. Usage-tier accounts see three tabs — Flow, SubFlows and Flow Actions; admins also get Migration Tools and Legacy Workflows. The demo shortcuts live in the composer itself — Flow Demo, SubFlow Demo and Flow Action Demo buttons under the description field — and the View Documentation link that opened this page sits at the right end of the Create New Flow | Update Flow sub-tab row.

Tab	What it contains
Flow	Create New Flow \| Update Flow (a sub-tab pair) · and, for admins, Deploy Runnable Flow · Replace with Runnable Version cards
SubFlows	Create SubFlow · Update SubFlow (reusable components)
Flow Actions	Create Flow Action with input/output mapping
Migration Tools (admin)	Business Rule → Flow · Workflow → Flow conversion
Legacy Workflows (admin)	Create Legacy Workflow (deprecated, backward-compatibility only)

Collapsible cards Within a tab, each card has a header you click to expand/collapse. On the Flow tab, Create New Flow and Update Flow are a pair of sub-tabs (Create New Flow opens by default — click a sub-tab to switch); the admin-only deploy cards start collapsed — click a card header to open it.

Execution Mode

Inside the Create New Flow sub-tab, the ⚙️ Settings panel (collapsed by default, just below the composer) holds the Table / Trigger / Template / Connection / AI Model chips together with the Execution Mode and Verification dropdowns. Execution Mode controls how many AI models work on your request and what context they can read. Verification (2026-08-01) always runs as one direct AI call using the section's AI Model selection — never Master-Mind, never a rule-based score — with an automatic AI fallback chain if that model fails; when the whole chain fails the result is marked UNVERIFIED rather than showing a fabricated score. Execution Mode has three modes:

Single 1 model

Uses each card's own AI Model selector and the fast structured generator. Best for quick, routine work.

Quick 3 models

Multi-model consensus via Master Mind, using the context you attach below the selector.

Full 4 models

Four-model consensus via Master Mind — highest quality for complex or high-stakes flows.

In Quick/Full mode you can attach context for the models to read via the composer's Upload Files button (images, code, XML, JSON, PDF, text). Admins additionally get a 📎 Local AI Context panel with Local File Paths and read-only Filesystem Access (MCP).

Don't expose secrets Never connect a folder (MCP) or upload files that contain credentials, API keys, or private keys — the AI models read them on-demand.

Connect a ServiceNow instance

Deploying or creating a draft on the instance needs a connection. You set it once in the Create New Flow card and the deploy/replace cards reuse it.

Open Flow Click-by-Click, Flow tab, Create New Flow sub-tab. In the settings row under the composer, open the Connection selector (it reads Not connected until you fill it).
In ServiceNow Instance URL, enter your host, e.g. https://dev301293.service-now.com.
Enter the Username and Password of an account with admin / flow-designer rights.

Admins Admin users see an "Using organization ServiceNow credentials" notice instead of the credential fields — the connection comes from environment configuration, so there's nothing to type.

Permissions The account needs rights to create flows and commit update sets (typically admin on a PDI). Credentials are used server-side only and are never stored in the page.

1 · Create New Flow Live

Describe a flow and get back a click-by-click implementation guide document that tells you exactly how to build it in Flow Designer. Nothing is written to your instance — you create the flow manually from the guide (2026-08-01: draft shells are no longer auto-created).

Click-by-click

Open the Flow tab. The 📝 Create New Flow sub-tab is selected by default (its sibling, ✏️ Update Flow, sits to its right).
Flow Name — type a clear name, e.g. Incident Assignment - Auto-Assign.
Description — describe what the flow should do, in plain English. The more specific you are, the better the generated guide. The 🛠 Builder button under the description opens the free Prompt Builder, which turns a rough goal into full, well-written requirements; the Flow Demo / SubFlow Demo / Flow Action Demo buttons beside it fill the matching form with sample data (the SubFlow and Flow Action demos switch to their tab first).
Table — enter the trigger table, e.g. incident. (Flow Name and Table are required.)
Trigger Type — choose Record Created, Record Updated, Record Created or Updated, or Scheduled.
Template (Optional) — leave None - Start from scratch, or pick a starting pattern: Approval Process, Multi-Channel Notification, Record Automation, REST Integration, or Data Transformation.
AI Model — pick the model for Single mode (default GLM-5.2 (Cloud)). In Quick/Full mode this is handled by the consensus instead. The same selection is used to verify the generated artifact. (No ServiceNow connection is needed here — generation never writes to the instance.)
Click Create Implementation Guide. A loading spinner with an elapsed-time counter appears.

The result — your Click-by-Click document

When generation finishes, the result panel shows a Success card containing:

A summary table — Flow Name, Description, Table, Trigger, and a Verification row: PASS/FAIL with a score out of 100, AI-verified by the section's selected model (an "AI-verified — <model>" badge names it; UNVERIFIED appears if the whole AI fallback chain failed).
A Show Flow Definition button — click it to reveal the implementation guide: numbered, click-by-click steps with the exact trigger, actions, field values, conditions, and any scripts needed to build the flow.
A 📥 Download Files button (a ZIP with the flow JSON and a ..._Manual_Configuration.md copy of the guide).

This guide IS the click-by-click document "Create New Flow" doesn't compile a finished flow — ServiceNow has no public API to do that. It produces a precise, copy-paste-ready build guide; you create the flow yourself in Flow Designer (see case 3).

2 · Deploy Runnable Flow Live Admin only

Clone a curated golden template into a brand-new, genuinely runnable, published flow — no manual building required.

Click-by-click

Make sure your instance connection is filled in under Create New Flow first (Deploy reuses it).
On the Flow tab (admin accounts only), click the 🚀 Deploy Runnable Flow card header to expand it. The template list loads automatically.
Template — pick one, e.g. Approval (record-triggered) or Reminder Notification (record-triggered). The line beneath shows its base table and trigger.
Target Table (only for cross-table templates) — if a Target Table dropdown appears, choose where the flow should trigger, e.g. incident. The trigger and actions are rebound to your choice (fields resolve by table inheritance). Single-table templates don't show this field.
New Flow Name (required) — type a clear name, e.g. My Reminder Flow.
Description (optional) — what the flow does.
Activate on deploy? — leave No — deploy inactive (recommended) to review first, or choose Yes — publish active to go live immediately.
Click Deploy Runnable Flow. A progress panel appears while the update set is committed on your instance (this can take a minute or two).
On success the result panel shows ✅ Runnable, the target table, and a link to open the flow in Flow Designer.

Activate later If you deployed inactive, open the flow in Flow Designer and click Activate when ready. If you deploy active, confirm the result panel shows the flow as active, then create/update a record on the trigger table to verify it fires.

Cross-table example The Approval template is built on task and can deploy onto any table that extends it — incident, change_request, problem, sc_task, sc_req_item — because every field it references exists on those tables by inheritance.

3 · Build a Flow in ServiceNow from scratch Live

Take the implementation guide from case 1 and assemble the real flow, step by step, in the ServiceNow Flow Designer builder.

Click-by-click (in Flow Click-by-Click, then in ServiceNow)

Run Create New Flow with Template = None - Start from scratch. Click Create Implementation Guide.
In the result panel, click Show Flow Definition and keep it open — this is the build guide you'll follow. Optionally click 📥 Download Files to keep the _Manual_Configuration.md copy alongside.
In ServiceNow, open Flow Designer (All → Process Automation → Flow Designer) and click + New → Flow. Give it the name, description, and application scope from the guide. (2026-08-01: the module no longer creates a draft shell for you — you create the flow record yourself.)
In Flow Designer, click Edit flow. Under Trigger, click + Add a trigger and set it to match the guide's Trigger Type and Table (e.g. Created on incident), plus any trigger condition the guide specifies.
For each numbered action in the guide, click + Add an Action, Flow Logic, or Subflow, choose the action type named in the guide (e.g. Ask for Approval, Update Record, Send Email), and fill its fields with the exact values the guide lists.
For any branch, add Flow Logic → If / Else and set the condition from the guide (e.g. branch on the prior approval's outcome).
Paste any scripts from the guide into the corresponding script steps verbatim.
Click Save, then Activate to publish the flow.
Test it: create or update a record on the trigger table and confirm the flow fires (check Flow executions / the flow context). Adjust against the guide if anything differs.

Why build it by hand? Arbitrary flow logic must be compiled by the Flow Designer builder, which has no public API. The guide gives you a correct, exact plan so assembling it is mechanical. (If you want a flow with no manual building, use a matching Deploy Runnable Flow template instead.)

Name it from the guide Create the flow with exactly the name, description, and trigger table the guide lists — the guide's steps reference them verbatim.

Replace with Runnable Version Live Admin only

Blue-green update: deploy a new runnable version of a flow that already exists, retire the old one, with one-click rollback.

Confirm your instance connection under Create New Flow.
On the Flow tab (admin accounts only), expand the ♻️ Replace with Runnable Version card.
Target Flow to Replace — enter the existing flow's sys_id or exact name.
New Version Template — choose the template for the replacement. It must trigger on the same table as the flow you're replacing.
New Version Name — e.g. My Reminder Flow v2; add a Description if you like.
Activate new version + retire old? — Yes (recommended) deploys active and instantly cuts over; No deploys inactive and leaves the old flow active.
Click Deploy New Version + Retire Old. On success the new version is live and the old flow is deactivated + renamed "(retired)" as a rollback point.

Same-table only A replace keeps the same trigger table. To move a flow to a different table, use a cross-table Deploy Runnable Flow and retire the old flow manually.

Update Flow Live

Change an existing flow's name, description, or active state — with impact analysis.

On the Flow tab, select the ✏️ Update Flow sub-tab (to the right of Create New Flow).
Enter the Flow Sys ID or Name. You may attach the flow's XML as a local reference, but the update action itself uses only the fields you enter on the form.
Set a New Name, New Description, and/or Active Status (No change / Active / Inactive).
Click Update Flow and review the impact report.

SubFlows · Actions · Migration · Legacy

SubFlows tab

Build reusable components. Create SubFlow takes a name, description, and AI Model and generates a subflow you can call from other flows. Update SubFlow revises an existing one with impact analysis (optional XML upload).

Flow Actions tab

Create Flow Action builds a custom action with input/output mapping — provide a name, description, category, and optional script, then generate.

Migration Tools tab (admin only)

AI-assisted migration of legacy automation to Flow Designer: Business Rule → Flow (name, table, when, script, or upload XML) and Workflow → Flow (paste or upload workflow XML). Always review and test the converted flow before deploying.

Legacy Workflows tab (admin only)

Create Legacy Workflow exists for backward compatibility only. Legacy Workflows are deprecated in ServiceNow — use Flow Designer for new automation.

How it works

Create New Flow → implementation guide

The module asks the AI for two things: a validated flow definition and a precise, step-by-step manual configuration guide (exact field values, conditions, variable names, scripts). Nothing is written to your instance (2026-08-01 — draft shells are no longer auto-created): ServiceNow has no public API to compile a flow's snapshot anyway, so you create the flow and assemble the trigger/actions in the builder using that guide. The generated artifact is then verified by one direct AI call with the section's selected model (automatic AI fallback chain; never a rule-based score).

Deploy / Replace → runnable clones via update-set commit

A flow only runs if it carries a compiled snapshot, which ServiceNow generates inside the builder. Templated deploys carry a real captured flow and transport it the supported way — load it as a retrieved update set, preview, and commit. The clone gets fresh sys_ids; the flow-local ui_ids are kept so the snapshot stays valid. Cross-table deploys rewrite only the trigger/action table binding (field pills resolve on the target by inheritance), then re-verify no source-table reference remains.

Execution modes

Single uses the fast structured generator with the card's selected model. Quick (3 models) and Full (4 models) run a multi-model consensus through Master Mind, optionally reading the local files, MCP folder, or uploads you attach.

Troubleshooting

Symptom	Cause & fix
"Please fill in Flow Name and Table"	Both are required on Create New Flow. Enter them and retry.
No Sys ID / ServiceNow URL in the result	Expected since 2026-08-01 — generation never writes to the instance. Build the flow manually from the guide (Show Flow Definition). See case 3.
Verification row shows UNVERIFIED	The selected AI model and every fallback model failed to return a trusted verdict. No score is shown (fail-closed) — re-run generation to verify, or pick a different AI Model.
Target Table picker doesn't appear on Deploy	That template is single-table. Only cross-table templates show it.
"Table mismatch" on Replace	The replacement template's table must equal the existing flow's table. Use a cross-table Deploy to move tables instead.
Deployed flow doesn't fire	It deployed inactive — open it in Flow Designer and Activate (active deploys auto-refresh and fire immediately).
"A flow with internal_name … already exists"	Choose a different flow name — internal names must be unique on the instance.

FAQ

Does Create New Flow build a finished, runnable flow?

No. It produces a click-by-click implementation guide (and writes nothing to your instance). You create and build the flow in Flow Designer using the guide. For a flow that's runnable on deploy, use Deploy Runnable Flow.

Is a deployed flow really runnable, or just a draft?

Really runnable. Templated deploys carry a compiled snapshot and are committed via update set. After commit, the result panel reports the flow's status, snapshot presence, trigger/action counts, and active state so you can confirm it's ready.

Will deploying overwrite an existing flow?

No. Deploy creates a brand-new flow (fresh sys_ids). Only Replace with Runnable Version touches an existing flow, and it retires (never deletes) the old one.

Which AI model is used?

In Single mode, the model picked in the AI Model selector in the settings row (default GLM-5.2 (Cloud); Claude Fable 5, Claude Opus 5, Claude Sonnet 5, Gemini, and others are available). Quick/Full modes run a 3- or 4-model consensus via Master Mind. Verification always uses the same AI Model selection via one direct call — never Master-Mind — with an automatic fallback chain.

What happens to my credentials?

They're used server-side for the deploy/draft only and are never persisted in the page or logs.

Author: iDevOpsLLC · Flow Click-by-Click — Documentation · For deeper architecture notes see docs/flow-designer/ in the repository.