A workflow is a readable graph

A workflow is read from left to right. Each message in Semantics Chat starts a new execution at Start, follows one route, and produces an answer or action.

One path, several outputs

100 %

• After success
• After failure
• Data or result

Dashed boxes represent data, services, or results.

Drag to move. Use + / − to zoom, arrow keys to move, and Home to reset.

Key points:

• position is visual; links control execution;
• one conversation turn equals one graph traversal;
• a condition can provide multiple outputs and an Else case;
• outputs from a block can be consumed by downstream blocks on the same route;
• blocks connected to contextual ports prepare sources or tools before the block that uses them;
• the draft is applied only when saved.

Recommended build order

1. Add the required blocks from the palette.
2. Give each block a clear business name.
3. Connect them in execution order.
4. Configure required fields first.
5. Select actual references with the {{ helper.
6. Connect failure branches.
7. Check the problems panel.
8. Save and test each route.

Anatomy of a block

Basic information

Field	Purpose
Name	Label shown on the canvas; use a clear business name.
Identifier	Technical name used in references by default, such as http-1. It is read-only.
Version	Version of the block in use, displayed read-only in basic information.
Output variable name	Optional alias, available depending on the block, that makes references more readable, such as documents. It must remain unique.

Useful names include Search HR documents, Prepare RAG instruction, Final LLM answer, and Load Microsoft 365 tools.

Avoid vague names such as test, block 1, api, or prompt.

Configuration

The main section contains fields required for normal use. Start here and only open advanced configuration when your use case requires it.

Depending on the block, some fields are prefilled or read-only, and others offer a list of values. Fill in the editable fields that match your use case.

Advanced configuration

Depending on the block, this may include token budgets, tools, document configuration, or messages replacing expired results. Do not change a prefilled value unless you understand its impact.

Output links

• After success selects the next block when the action succeeds.
• After failure selects a fallback when it fails.
• After “label” selects the next step for a business output, when the block offers one.

Connect every potential failure to a clear message or an alternative route.

Source and tool connections

When present, the Contextual ports section connects a source or MCP tool provider to the block. The provider stays outside the main path and prepares its data before that block runs.

Use Connect block or Connect blocks to select a compatible provider. Follow the connection guide to configure sources, MCP servers, and links.