Import and export

Import and export move a workflow definition between instances, backups, or Git repos — credentials are excluded by design.

🔁 Export

1. Open the workflow.
2. ⋯ menu → Export.
3. Save the .knot.json file.

The file contains:

• Knot schema version;
• nodes, edges (source / target);
• trigger settings;
• credential references by logical ID, not secrets.

🔁 Import

1. Workflows → Import.
2. Select the .knot.json.
3. Map missing credentials to your local encrypted entries.
4. Simulate, then activate.

Attenzione

Importing a workflow from an untrusted source is like running untrusted business logic: review every HTTP and AI node before activation.

🔁 Version compatibility

Situation	Expected behavior
Same Knot version	Smooth import
Newer → older Knot	Ignored fields or explicit error
Major upgrade	Follow Knot Core release notes

Store exports in backup tooling with the Knot version when metadata is available.

🔁 Best practices

• One file = one business workflow (avoid monoliths).
• Version .knot.json in team Git (no secrets).
• Document required credentials in an internal README.

🔁 Public templates

Knot Core examples/*.knot.json use only fictional data (Demo Industries, @example.com). Ideal for learning without customer data leaks.

Next steps

• Create a workflow
• Activate a workflow