Exporting recipes for sharing — JSON format, deep linking, import/export between Workbench instances
Recipes are exported in a JSON format that captures every stage, configuration, and metadata. The export includes: the recipe name and description, the stage pipeline (each stage type, configuration, and ordering), input dataset references, sharing settings, tags and notes, and the recipe version history. The JSON is self-contained — another Workbench instance can import the recipe without needing access to the original datasets (it will prompt for dataset remapping).
Import a recipe JSON file via the Recipes page → Import button. The importer validates the JSON structure, checks compatibility with the current Workbench version, and presents a mapping dialog: match each referenced dataset to a dataset in the target instance. After mapping, the recipe is created in your workspace — ready to run against local data.
Every recipe has a permanent deep link URL. Sharing the URL with another user on the same Workbench instance opens the recipe directly in their browser. If they have access (via group sharing or public visibility), the recipe loads in read-only mode. Deep links use the recipe's UUID — they survive renames and edits.
Beyond export, recipes can be shared within a Workbench instance. Sharing levels: Private — only the owner can see and edit; Group — visible to all members of the specified group(s); Public — visible to all users on the instance. Shared recipes can be read-only (view and run, but not edit) or read-write (group members can modify).