Export and Import Workflows
Workflows are saved as JSON files (a standard text format).
You can:
- Export a workflow to save a backup or share it
- Import a workflow to use a template you downloaded (or got from a teammate)
Exporting workflows
Section titled “Exporting workflows”You have a few ways to export:
Copy-and-Paste
Section titled “Copy-and-Paste”- In the editor canvas, select one or more nodes (
Ctrl + CorCmd + C). - Paste them into another canvas or file (
Ctrl + VorCmd + V). - This method is fast for sharing parts of a workflow.
Using the Editor UI Menu
Section titled “Using the Editor UI Menu”- In the workflow editor, click the menu (three dots ⋮) in the top-right.
- You’ll see options such as:
- Download – saves the current workflow as a JSON file.
- Export from URL – pull workflow JSON from a URL.
- Import from File – upload a JSON file to load a workflow.
Importing workflows
Section titled “Importing workflows”To import a workflow:
- Use Import from File to upload a JSON file from your computer.
- Or Import from URL to load a JSON file hosted on the web.
- After importing, review the node settings (especially credentials) before you run it.
Why this matters
Section titled “Why this matters”- Back up your workflows periodically by exporting them.
- Share workflow templates with teammates or the community.
- Migrate workflows between environments (development → production) by importing.
- When importing into a new system, check that any credentials or connections are valid and secure.
Best Practices
Section titled “Best Practices”- Before sharing workflows, remove or anonymize sensitive info (credentials, URLs).
- Keep backups somewhere safe (for example: a private folder, a team drive, or version control).
- After import, test the workflow manually (see Full and Partial Executions Inside the Designer) to ensure it runs correctly.
- Maintain clarity: rename nodes, clean unused nodes, add Sticky Notes to explain logic (see Sticky Notes).