Build deterministic flows

• Structured user interfaces
• Conditional branches
• Agentic workers
• Other flows
• Human approval
• Model interactions
• HTTP requests
• MCP capabilities
• Installed extension steps

Canvas

The visual workspace containing the process steps and their connections.

Step

One defined unit of work, such as displaying a card, evaluating a condition or calling a worker.

Connection

The path from one step or outcome to the next.

Variables

Values passed into, between and out of process steps.

Run Demo

The interactive preview used to test the current draft.

Issue indicator

A count showing that part of the project may require attention before deployment.

Validation

The readiness check performed before continuing toward deployment.

A flow uses only the capabilities its process actually requires. Many useful flows contain no AI step at all.

• Customer-facing flow: ACME Customer Service Main Menu
• Agentic worker: ACME Support Process Router
• Controlled process: ACME Late Delivery Resolution

Customer opens the support menu
              ↓
Chooses an option or enters an open question
              ↓
Agentic Worker classifies the request
              ↓
Conditional Branch evaluates the result
              ↓
Go to Flow starts the approved process
              ↓
Deterministic resolution steps

• Confirm that the correct workspace is active.
• Define one clear business outcome for the flow.
• Identify the information the process receives.
• Identify the information it must return or display.
• List the important decisions and branches.
• Decide which actions must remain deterministic.
• Identify any human approvals that are required.
• Confirm which workers, tools or other flows are available.
• Prepare fictional test data for each important route.

Enlarge

1. 1Open Designer Home.
2. 2Select New project.
3. 3Enter a clear project name.
4. 4Select Flow.
5. 5Review the project-type description.
6. 6Select Create.
7. 7Describe the process when the Flow Editor opens.

The other project types in this dialog are covered in the Getting started guide.

Enlarge

AI design conversation

Describe what the process should achieve, what it should collect, which decisions it makes, which workers or flows it calls, what it must not do and which outcomes it presents.

Visual canvas

Inspect the complete process, select steps, add or remove steps, review connections, reorganise the layout and fit a large process into view.

Run Demo

The interactive experience produced by the current draft, shown beside the canvas.

Create a deterministic flow called [name].

Purpose:
[One clear business outcome]

Inputs:
- [Input 1]
- [Input 2]

Process:
1. [First step]
2. [Validation or decision]
3. [Approved action]
4. [Completion]

Branches:
- If [condition], go to [outcome]
- If [condition], go to [outcome]

The flow may:
- [Approved actions]

The flow must not:
- [Prohibited actions]

Demo requirements:
- Use fictional embedded data
- Do not call external systems
- Show realistic forms, choices and outcomes

1. 1Describe the business outcome.
2. 2Name the required inputs.
3. 3List the main process steps.
4. 4Define the important branches.
5. 5State any approval or escalation requirements.
6. 6State what the flow must not do.
7. 7Ask Designer to generate the first version.
8. 8Inspect the complete canvas before making another request.
9. 9Make focused follow-up changes one at a time.

Save

Save the current draft.

Variables

Open the project’s data and variable controls.

Run Demo

Preview the current experience.

Deploy

Begin the readiness and deployment journey.

Additional project actions

Open version, layout, import and export controls.

• Fit view
• Zoom in
• Zoom out
• Minimap
• Canvas movement

Enlarge

Steps

Built-in process capabilities provided by the Designer.

Extension steps

Additional steps exposed by installed extensions.

1. 1Open the Add Step control.
2. 2Search for the required step.
3. 3Choose between built-in and extension steps.
4. 4Select the step type.
5. 5Give the new step a meaningful name.
6. 6Complete its required settings.
7. 7Connect it to the appropriate previous and next steps.
8. 8Run the affected path before continuing.

Enlarge

Step name

The name used to identify the step on the canvas and during design.

Agent

The Agentic Worker the step invokes. This field is required in the shown interface.

Conversational

Off returns one response and the flow continues. On keeps the conversation with that worker open until it ends, then the flow proceeds.

1. 1Add an Agentic Worker step.
2. 2Select the step on the canvas.
3. 3Enter a meaningful step name.
4. 4Select the required worker.
5. 5Decide whether the interaction should be single-response or conversational.
6. 6Connect the step to the incoming path.
7. 7Connect its output to the next decision or action.
8. 8Test the worker directly.
9. 9Test it again from inside the flow.

Open customer message
        ↓
Agentic Worker step
        ↓
Structured classification
        ↓
Conditional Branch
        ↓
Go to Flow
        ↓
Controlled resolution

1. 1The customer-facing flow receives an open-text message.
2. 2The Agentic Worker step sends it to the process router.
3. 3The worker returns a stable classification result.
4. 4A Conditional Branch evaluates the result.
5. 5A Go to Flow step starts the relevant deterministic process.
6. 6The called flow collects information and performs the approved resolution steps.

detected_intent
confidence
clarification_question
called_process
suggest_human_support

These field names are an example from the ACME demonstration. They are not mandatory Greentic fields, and not every worker returns JSON. The designer defines the contract required by the receiving flow.

Worker configuration is covered in the Agentic workers guide.

1. 1Identify the data the flow receives.
2. 2Give each value a clear stable name.
3. 3Pass only the information required by each step.
4. 4Map step outputs deliberately.
5. 5Avoid storing credentials or secrets in ordinary flow variables.
6. 6Define what the flow returns when it completes.
7. 7Include fallback values or paths for missing information.

1. 1Save the current draft.
2. 2Open Run Demo.
3. 3Start from the beginning of the interaction.
4. 4Select an available menu option or enter an open question.
5. 5Complete every required input.
6. 6Confirm that the expected branch starts.
7. 7Confirm that cards and messages contain the correct information.
8. 8Repeat the test using alternative wording.
9. 9Test missing and invalid information.
10. 10Reset the interaction before testing an independent scenario.
11. 11Correct the canvas and run the scenario again.

A complete test approach is described in the Testing and troubleshooting guide.

Enlarge

Version history

Review versions recorded for the project.

Save as version

Create a named or recorded project version before significant changes or release.

Auto-layout

Rearrange the canvas automatically.

Import flow

Import supported flow content.

Export flow

Export the flow using the supported Designer format.

Export to GitHub

Export supported project content to a connected GitHub destination.

1. 1Save the draft.
2. 2Complete a representative Run Demo test.
3. 3Open the project actions menu.
4. 4Select Save as version.
5. 5Record a meaningful version description where requested.
6. 6Continue editing in the draft.
7. 7Use Version history when reviewing previously saved states.

Enlarge

• A successful result states that no issues were detected.
• The summary may include the number of cards and process steps.
• Let’s go continues the publishing or deployment journey.
• The counts shown belong only to the ACME demonstration.

1. 1Save the current draft.
2. 2Run representative tests.
3. 3Resolve the visible issue count.
4. 4Continue to the deployment readiness check.
5. 5Review the validation result.
6. 6Return to the Editor when an issue remains.
7. 7Continue only when the project is technically ready and the business test has passed.

The next stage is covered in the Publishing and deployment guide.

• The flow has one clear business outcome.
• The start and completion states are clear.
• Inputs and outputs have stable names.
• Important decisions use explicit branches.
• Agentic workers are used only where interpretation is required.
• Worker outputs follow a stable contract.
• Every called flow exists and is available.
• Sensitive actions use human approval where required.
• Only approved external capabilities are used.
• Every important branch has been tested.
• Missing and invalid inputs follow a controlled path.
• Customer-facing text and cards are understandable.
• The draft has been saved.
• A meaningful version has been recorded.
• The project passes the readiness check.