> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Flow Constructor

> Flow tabs, block settings, transports and the first route on canvas.

Open **Infrastructure → Configurations → New Flow → Regular Flow**, name and complete the wizard. For the reused site, select [pool transit nod](https://docs.axottle.com/en/connection-units/transit-pools.md).

## Tabs of regular Flow

| Tab | Content |
| - | - |
| **Review** | Draft, applied version, health and route summary. |
| **Holst** | Block and Link Editor. |
| **Components** | List of blocks and their settings. |
| **Settings** | Name, description, client settings, mode, balancing and data collection about inaccessible sites. |
| **Verification** | Static configuration linter. |
| **Failure Lab** | Calculation of consequences of selected failure. |
| **Restoration** | Flow Guard: Automation policy, manual launches and its plans. |
| **Health** | Live checks, diagnostics, logs and event history. |
| **Versions** | Used images and restoration to draft. |

## Blocks and connections

| Block | Appointment |
| - | - |
| **Gateway** | Start of circuit; leads to input node directly or via CDN. |
| **Input node** | Accepts client connection. |
| **Transit node** | Managed transition cascade; in its settings you can select Pool Node. |
| **External transit node** | Outbound connection via external VLESS key. |
| **WARP** | Exit via WARP on a node that sends traffic to it. |
| **External proxy** | Outbound connection to a given proxy. |
| **CDN** | Area in front of input node. |
| **Internet** | Direct exit. |
| **Blackhole** | Traffic blocking. |

Gateway cannot be connected directly to the Internet. A CDN must lead to one input node; an input node and a transit node can lead to the next transit or to the exit; rings are not allowed.

The routing condition is set in the communication dialog. For a normal input or transit unit, leave one output for all the rest of the traffic, and set the additional branches with conditions. Balanced alternatives within the pool are described by [separately by](https://docs.axottle.com/en/connection-units/transit-pools.md).

## Node tuning

Tap the block twice. Select the physical node or available pool, set up the connection template, transport, security, sniffing and optional settings. Check JSON Preview and validation messages.

The available settings depend on the role and template. The supported transports are TCP, WebSocket, gRPC and XHTTP; for XHTTP, use the permissible combinations of mode and parameters from the constructor. REALITY and TLS parameters must correspond to the selected transport and the actual server configuration.

For SelfSteal, prepare the domain, DNS, certificate and service itself in the [node card](https://docs.axottle.com/en/nodes/control-panel.md). The choice of masking in the draft does not prove its readiness on the server.

For TLS and SelfSteal, select the [managed node domain](https://docs.axottle.com/en/nodes/domains.md). It defines the address, SNI, and certificate paths. When you change the node, the choice is reset; no other binding is accepted by the server. Schemas without an explicit choice use the main domain.

## First route

**1. Add in.**

Add the input node and connect it to the Gateway, assign a physical node and set up the connection.

**2. Add an exit.**

Connect the login to the Internet without a condition. Later, you can add a transit, a pool, or conditional branches.

**3. Save and check.**

Wait for the canvas to be saved. Open Check and remove the blocking remarks.

**4. Look at the plan.**

Click "Apply Changes." The panel will assemble a plan and show you errors, warnings, and confirmations you need.

**5. Apply.**

Apply the plan viewed, then open Health and check the customer connection.

Changing the canvas, route parameters or pool used after the plan is assembled may require re-checking.Details - [Application and versions of](https://docs.axottle.com/en/connection-units/lifecycle.md).

## Verification

The plan is assembled without blocking errors, the necessary nodes are assigned, the conditions lead to the expected outputs, after application, a fresh check of the working version is received and the connection is confirmed by the client.

## Rollback

Before applying, use "Reset draft." After applying, restore the working version using the [rollback instruction](https://docs.axottle.com/en/connection-units/lifecycle.md#откат).

Check the availability of features in the installed version in the panel; this reconciliation does not confirm the deployment on the servers.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.