Export¶
The Modeler supports exporting workflows in multiple formats. You can create portable copies of your models for backup, sharing, embedding in other sites, or generating Drupal recipes.
Accessing the export dialog¶
Click the Export button (download icon) in the toolbar to open the export dialog. If you have unsaved changes, the modeler will prompt you to save first -- exports always use the last saved state.
Permissions
The export button is only visible when your user account has the appropriate permissions. See Permissions for details.
Export formats¶
Recipe¶
Exports the workflow as a Drupal recipe -- a standardized package format for distributing Drupal configuration. Clicking Export opens the recipe generation page in a new browser tab, where the backend handles the full recipe creation process.
Use this format when you want to package a workflow for distribution through Drupal's recipe system.
Archive¶
Downloads the workflow as a compressed .tar.gz archive containing the
model's configuration files. The archive is generated by the backend and
downloaded directly to your computer.
Use this format for backups or when you need the raw configuration files.
JSON¶
Exports the workflow as a JSON file that can be used with the Standalone Viewer or imported into other tools.
The JSON export includes:
| Data | Always included | Optional |
|---|---|---|
| Model data (nodes, edges, metadata) | Yes | -- |
| Required modules list | Yes | -- |
| Configuration form schemas | Yes | -- |
| Component metadata | Yes | -- |
| Replay data | -- | Yes (checkbox) |
When Include Replay Data is checked, the exported file also contains the execution history, allowing the standalone viewer to offer full replay functionality.
The dialog also displays the list of required modules that the workflow depends on, so you know what needs to be installed on any target site.
SVG¶
Exports a visual snapshot of the canvas as an SVG image file. The SVG rendering includes:
- All node types with their correct shapes (rounded events, rectangular actions, diamond gateways, double-bordered subprocesses).
- Edge connections with labels and condition annotations.
- Annotation notes attached to nodes and edges.
- Proper colors from the current theme (light or dark mode).
Use this format for documentation, presentations, or any context where you need a visual diagram of the workflow.
Tips¶
- Save before exporting: The export always reflects the last saved state. If you have unsaved changes, save them first to include everything.
- JSON for portability: The JSON format is the most versatile -- it can be loaded in the standalone viewer, processed by scripts, or archived for long-term storage.
- SVG for visuals: Use SVG when you need a diagram for documentation or a presentation slide.