Import and export
Backing up flows as files, moving them between locations, and the two import modes.
Both live on the Flows list.
Export
Export on a flow downloads it as a JSON file; Export all downloads every flow of the location in one file. The format:
{ "format": "novon-flows", "version": 1, "exportedAt": "2026-10-06T18:00:00.000Z", "flows": [ … ] }Each flow includes its published graph and, if present, its draft.
Import
Import reads such a file. The behaviour depends on how many flows it contains:
| File contains | What import does |
|---|---|
| one flow | upserts it by id: an existing flow with that id is replaced, otherwise it is added. If the id exists you can choose Keep both, which gives the import a new id |
| several flows | replaces the whole list of the location's flows, after a confirmation |
Imported flows that reference devices this location does not have show a Missing device badge
and should be edited before enabling. States written as labels in the file ("to": "Open") are
accepted and converted to raw tokens when you save; a state the device never reports gets an
unknown state warning.
There is a maximum file size (twice the location's flow-body limit). Flows are also included in hub backups and restored with them, so export is for moving and sharing rather than for safety.