Use the Workflow Assistant v2

Use the assistant inside the designer to discover exact contracts, propose a design, and help test or repair it while you retain control of Connections, Canvas changes, save, and release.

Before you start

Use a Test Environment and confirm that you have Site Administrator access. Decide the Workflow's input, expected output, systems, and whether it may change external data.

To start a new design, open Workflows, click New Workflow in the required folder, and rename the Workflow for its business outcome. Open Assistant from the action bar on the right. If you want to learn the designer manually first, complete Build a Workflow.

Start with a request

  1. Open or create a Workflow in the Test Environment.
  2. Open Assistant.
  3. Describe the outcome, input, output, systems, permitted Connections, trigger type, and any operation that changes external data.
  4. Ask for the smallest runnable path first.

For example:

Build an HTTP Workflow that receives an order ID, reads the order through an existing ERP Connection, and returns its ID, status, and total. Discover the exact Methods and schemas, ask me to choose a Connection, and test only read operations.

Do not include credentials. The assistant can discover compatible Connection identities but cannot read protected values.

Respond to assistant requests

When the assistant presents options, review the reason and select only the choices that match the intended contract. For a Connection request, choose an existing compatible Connection or open Create Connection in a new tab, configure it, and return.

Connection choices are filtered by required Node and current Workflow Cluster. If the right Connection does not appear, check its runtime, Node version, and Cluster placement before selecting a substitute.

Review the proposal

  1. Read the proposed Workflow summary and warnings.
  2. Click Open Code in New Tab when you need to inspect the complete YAML separately.
  3. Check Node versions, Methods, schemas, Connections, triggers, mappings, mutation scope, and logging.
  4. Click Accept to apply the proposal as one undoable Canvas change, or Reject to leave the design unchanged.

Accept does not save or publish the Workflow.

Test and iterate

Resolve Problems, run with small representative input, and inspect Logs. Tell the assistant the specific failed Step or diagnostic and ask for the narrowest repair. Review and accept each new proposal before rerunning.

When the Workflow succeeds, save it with a clear revision message. Review publish and Environment-specific status separately before exposing a trigger.

Use Start again when the task or design context changes substantially. Closing the Assistant view preserves the current designer-session conversation and does not stop background work.

First exercise without an external system

For a small first exercise, use this request:

Create a Workflow with a String input named message and a String Return named echo. Map echo from message. Use Hello Flowgear as the test input. Do not add an external Connection or trigger. Validate and Debug the proposed Workflow, and show me the result before I accept it.

Review the proposed Parameters and Returns and confirm that the reported echo is Hello Flowgear. After accepting, run the Workflow yourself with another message and confirm that echo changes to match. This gives you a small contract to inspect before introducing external reads or writes.

Complete decisions and verification

When the assistant requests an implementation decision, review the explanation, select an option, and click Confirm. Cancel and clarify your requirements if none is suitable. If you reject a proposed Workflow, explain the smallest correction and let the assistant propose again.

The assistant can validate and Debug a proposal before presenting Review a Proposed Workflow. Review both its explanation and test outcome, then verify the accepted design yourself. Check Problems, Logs, Parameters, Step results, Returns, and any external side effects. Confirm the Environment, Cluster, Connections, and final YAML before clicking Save and entering a useful revision message.

See AI Workflow Assistant for the feature's capabilities and boundaries.

For a conversation outside an open Workflow, use Chats. Its Site context and conversation lifetime are explained separately from the designer flow above.

See also

See Assistant Pane, Troubleshoot with the Assistant, and Test a Workflow Safely.