AI Workflow Assistant v2

The AI Workflow Assistant works inside the Workflow Designer. It can inspect the current design, discover the Flowgear contracts needed for a solution, test and diagnose the Workflow, and propose a change for you to review.

The assistant requires Site Administrator access. If your role is missing a required permission, the assistant identifies it when you try to use the feature.

Upcoming changes

An upcoming Flowgear release changes where the assistant works, what it can access and what it can do, both in the Workflow Designer and in Chats. The rest of this article describes the assistant as it works today.

Any Environment

The assistant will no longer be limited to the Test Environment. A chat will belong to its Site rather than to an Environment, and the assistant picks the Environment for each action. When you don't name an Environment, it works in the first Environment in the Site that its access allows; name another Environment in your message to work there.

When the assistant saves a Workflow, it saves it in the Site's first Environment. On a Site with release management, ask the assistant to promote the Workflow to move it on from there. In the Workflow Designer, proposed changes can only be applied, and a chat about a new Workflow started, in the Site's first Environment.

Assistant access

You choose which Sites and Environments the assistant may use, with no access, read, or read and write for each Environment. This setting applies to all your chats and does not expire. Until you change it, the assistant has read and write access to the first Environment you can use in the open Site.

The setting can only narrow your own permissions; it never adds to them. When it refuses an action, the chat offers to change the assistant's access. When your own permissions refuse an action, it stays a denial, and changing the assistant's access does not help.

Workflow logs are not separated by Environment. Read access to any Environment in a Site includes that Site's logs from every Environment.

Permissions

Site Administrator access will no longer be required. Each action the assistant takes checks your own permissions for that action, in the Site and Environment the action uses. The assistant can do what you can do in the Console, within its access setting.

Chats and Workflows

Each chat follows the Workflow it is working on, which is the Workflow the assistant last read or saved. One chat can move between v1 Runtime and v2 Runtime Workflows. Actions that change an existing Workflow, such as saving, enabling or promoting it, apply only to the Workflow the chat is working on.

The assistant in the Workflow Designer can continue any of your saved chats for the Site. Sending a message moves the chat to the open Workflow.

v1 Runtime Workflows

The assistant can find and read v1 Runtime Workflows, their Nodes, logs and folders as well as v2 Runtime Workflows. Values longer than 1,000 characters are returned only when the assistant asks for that value, and secrets and binary values are not returned. In the v1 Runtime designer, the assistant can set simple text or number Property values on the open Workflow, and you save the change. Otherwise, it explains the change and links the Workflow so that you can make it.

Changing, debugging, enabling and promoting Workflows remain available for v2 Runtime Workflows only.

New actions

You can ask the assistant to:

Promote a Workflow to the next Environment on a Site with release management.
Enable a Workflow in an Environment where it is published, and check whether a Workflow is enabled.
Create and update Connections with their non-secret values. The chat then links the Connection page, which opens in a new tab, where you enter passwords, keys and certificates.
Create Connection folders, and move Workflows, Connections and folders between folders.

Secrets and options

The assistant is instructed never to ask you to type passwords, API keys, tokens or certificates into the chat. Instead, it links the Console page where you enter them: the Connection page for Connection credentials, the API Keys screen, or the Key/Value Management screen.

When the assistant asks you to choose an option, you can type your own answer instead.

Open the assistant

Open a Workflow in the Workflow Designer.
Click Assistant in the action bar on the right.
Describe the result you want the Workflow to produce.

A useful prompt is:

Create a Workflow that receives a customer ID, retrieves the customer from our CRM Connection, and returns the customer's name and status. Ask before choosing between multiple Connections.

Include the source system, expected input and output, important constraints, and whether an operation may change external data. The assistant will ask for information it cannot safely infer.

You can also open Chats from the main navigation for a Site conversation outside the designer. Use the designer Assistant when you want to review and apply a proposal to the open Workflow.

What the assistant can do

The assistant can:

Read the current Workflow definition and its Folder and Cluster context.
Discover installed Nodes, exact Methods and versions, templates, mapping functions, and schema contracts.
Ask you to choose between implementation options.
Ask you to select a compatible Connection. The assistant cannot see credentials, but it can use the Connection in a Workflow after you select it.
Build and validate Workflow YAML.
Run the Workflow in Debug mode, inspect Workflow logs, retrieve detailed Step Parameters, Return Values, and Errors for selected entries, and repair a failed test.
Search the public web when current external information is needed and provide source links with the answer.
Propose a complete replacement for the current canvas.
Assist in migrating Workflows from v1 Runtime.

When the assistant creates a child Workflow, it uses the current Workflow's Folder and Cluster as defaults unless you request another location.

Review interactive requests

The assistant pauses when it needs a decision that should remain under your control.

Choose an option

The assistant explains why it needs a choice and displays one or more options. Select the required option, then click Confirm. Click Cancel when none of the choices is suitable and explain what you want instead.

Choose a Connection

The Select a Connection request lists compatible Connections and explains how the selected Connection will be used. Search the list, then select a Connection.

If no suitable Connection exists, click Create a new Connection. The Console opens the Connection page in a new tab and carries the current Workflow's Cluster into the new Connection flow. Return to the assistant after the Connection is ready.

The assistant receives a Connection identifier and contract, not its protected credential values.

Review a proposed Workflow

The Review a Proposed Workflow panel is the final approval point for a canvas change.

Click Open Code in New Tab to inspect the proposed YAML separately.
Click Accept to apply the proposal to the current design as one undoable canvas change.
Click Reject to leave the canvas unchanged. Tell the assistant what to refine before it proposes another version.

Accepting a proposal does not save it as a Workflow revision. Run the accepted design, review Logs and Problems, then click Save when you are satisfied.

Continue working while it runs

The assistant can continue while its view is closed. Its action-bar status shows when it is working, needs input, has new activity, or encounters an error. Reopen the view to continue the same conversation; its transcript remains available for the current designer session.

Click Start again when you want a clean conversation for a different task or after the Workflow context has changed substantially.

The conversation survives an Environment switch within the same Workflow, but sending and editing through the assistant remain restricted to Test. Finish or reset an active request before switching if the Environment control is unavailable. Opening a different Workflow or Site starts a new session.

Understand the safety boundaries

The assistant uses discovered product contracts instead of inventing Node versions, schema fields, identifiers, or Connection keys. It does not reveal Connection values or secrets.

Web searches use public search terms. Do not put credentials, protected Connection values, or private business data in a prompt.

You remain responsible for choosing Connections, approving the proposed Workflow, reviewing operations that change external systems, and saving the accepted design. A proposal that passes client validation can still expose a compilation or Runtime problem when you run or save it, so test the final design before releasing it.