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.

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;
• 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. Avoid changing it without a reason.
Output variable name	Optional alias 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.

Advanced configuration

This may include timeouts, headers, a technical URL, token budgets, tools, or document configuration. 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.

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