> ## 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.

# Remnawave Imports to Flow

> Disassemble the existing route, approve the observed scheme and prepare a managed Flow.

Import restores the scheme of the existing route via the connected API
Remnawave. It stores an observed image that you can study and then
Subscription URL and CDN account are not required.

## Create an observable Flow

1. Open Flow Studio (`/new/connection-units`) in the right project and run it.
   Import from Remnawave.
2. Select the user and the host available to them. Availability is determined
   Remnawave data, including client templates and hosts groups.
3. Answer questions about ambiguous regions: DNS matching with IP nodes
   It helps to find the server, but does not confirm ownership of it.
4. Check the canvas and press "Approve." No Connection Unit is created before this step.

The panel disassembles inbounds, orderly routing rules, exit by
default, outbounds, balancers, and proxy chains. Unknown terms and
Profile secrets are not returned to the browser.

Before approval, the source is reread. If the settings or matching
Addresses with nodes changed, API returns `409`: repeat analysis with saved
You can answer them and check the diagram again without answering the mandatory questions.
The claim atomically retains the graph, the source, and the observed version; the configuration of the servers and Remnawave remains the same.

## Clarify or begin management

Approved imports have two actions:

| Action | Result |
| - | - |
| "Disassemble / clarify" | Re-read the saved source with the same answers and a new observed version of the same Flow |
| "Make Full Flow" | New editable draft in the same Flow; the original image remains in the history of |

Observed imports cannot be modified via autosave, Compile or Apply.
After conversion, open blocks with the status of `incomplete` / `action_required`.
Confirm inputs and configure managed resources.
Compile, Plan Verification and Apply.

When converting, the client chain of the template is replaced by connections of a single gateway.
Customer rules, balancers and backup paths
are stored in the lock and import history.
Configure in managed Flow; auto-save behavior
There is no guarantee of any arbitrary client template.
Outbound/endpoint pairs are folded into network connections to save the original data.

## Boundaries

The conversion doesn't switch traffic and doesn't install anything.automatic.
Cutover, constantly monitoring discrepancies and reading arbitrary configurations
Nginx/Caddy/HAProxy has not yet been sold through Agent.
The type of external service specified by the operator is stored as its response, and not
As a result of the Agent's inspection.

## Verification

Make sure that the canvas shows the selected entrance and the desired route branches.
Once refined, check the source version and the answers.
Open all blocks requiring action, check client routing
And prepare an application plan. The draft doesn't confirm the path is working.

## Rollback

Before approval, close the wizard: Flow has not yet been created. Approved import.
It doesn't change the servers. If you turn it into a manageable draft, the original
The image remains in history, but the automatic reverse transformation does not
Until Apply, the traffic stays on the original configuration.
After Apply, use the [Flow](https://docs.axottle.com/en/connection-units/lifecycle.md) rollback order.

Capabilities depend on the installed build; live network run within this reconciliation was not performed.


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