Presets, export, and import

You don’t have to build a flow from scratch: typical tasks have ready-made presets, and your own good diagrams can be exported to a file and moved to another project.

Presets: ready flows in one click

In the flow editor hit “Presets”. A gallery opens with the ready-made starters: page, sign in, registration, forgot password, change password, sign out, Telegram notification, JSON endpoint, and captcha form. A card lays the diagram on the canvas — from there you refine it like any of yours: emails, redirects, nodes.

Each preset gets its own step-by-step article — start with “Page” or pick yours in the “Presets” section on the left.

Export: a flow into a file

In the flow list every row has an “Export” button, and above the list — “Export all”. A .dynflow.json file downloads (for all — flows.dynflows.json).

The file carries everything needed for a move (a fragment of a real export of the “Service catalog” flow):

{
  "format": "dynapi-flow",
  "handle": { "slug": "katalog-uslug", "name": "Каталог услуг" },
  "routes": [
    { "path": "/katalog-uslug", "methods": ["GET"], "cache": { "defaultTtl": 300 } }
  ],
  "flow": { "version": 2, "nodes": [ "…" ], "edges": [ "…" ] },
  "queries": [ { "name": "services_list", "query": "query { services … }" } ],
  "templates": [ { "path": "katalog.liquid", "content": "…" } ]
}

The file carries everything needed for the move:

the flow diagram itself;
the routes it is bound to (paths, methods, TTL);
the library queries it references;
the page templates it draws.

CMS data (records, services, posts) doesn’t move — only the structure. That is deliberate: content is the project’s living household, the diagram can be moved safely, and data is copied with backups.

Import: a file into another project

In the other project: “Site” → the flows tab → “Import” — and pick the file. The platform carefully lays out the contents:

queries are added if the name is free (a taken one is skipped);
templates are added if they don’t exist yet;
the flow is created on a free path; if the path is taken, it is skipped with a warning — nothing gets overwritten.

This is how the templates from our site preset library work, and moves between projects: assemble a showcase site once — roll out its copies onto new clients in minutes.

Common questions

Question	Answer
The import file “won’t read”	The file is damaged or it isn’t a flow export: you need a `.dynflow.json` produced by the “Export” button.
Some templates are missing after the import	Templates with those paths already existed — import doesn’t overwrite.
The imported flow is on a different path	The path was taken: the flow was created, bind it to the taken address manually in “Paths”.

Next article: The Page preset →