Appearance
Import & export projects
A whole project — its pages, its automations, its layout — can be saved to a single JSON file and imported back. Use it to move a project between accounts, keep a versioned backup, hand a starter to a teammate, or share a ready-made demo.
Export
On the dashboard, open a project's ⋯ menu → Export to file. Your browser downloads your-project.flowrunner.json.
The file is the design of the project and nothing else. It deliberately does not contain:
- Who owns it — no workspace, no account. The file belongs to whoever imports it.
- Secret values. A flow references a secret as
${secrets.STRIPE_KEY}; the value lives in a separate vault the export never reads. So an exported project is safe to share — there are no credentials in it. - Webhook tokens. Those are live, callable URLs; an export must not become a back door.
- Submissions. The design travels; the data people submitted stays behind.
Import
On the dashboard, click Import from file and choose a .flowrunner.json file. FlowRunner creates a new project from it in your current workspace and opens it.
The importer decides ownership, not the file: the new project is yours, in your workspace, with a fresh id — a file cannot be crafted to land somewhere it shouldn't or overwrite something you already have. A file that isn't a valid export is refused with an explanation.
After importing
Two things to check, because they don't travel in the file:
- Secrets. Any
${secrets.X}a flow uses needs its value set in this workspace — open Secrets and add them. Until then those nodes fail on their error port rather than running with a blank credential. - Webhook triggers. If a flow was triggered by a webhook URL, mint a fresh one from the trigger bar — the old token did not come across.
Installed components (HTTP, Email, Stripe, …) are seeded into every workspace automatically, so an imported flow's nodes work out of the box.