Import and export workflows

Blokboard uses one versioned workflow file for app exports, official examples, and article attachments. Files use the .blokboard.json extension.

Download a workflow#

Open the workflow menu and choose Download workflow. The file includes its name, format version, node compatibility information, graph, parameters, canvas positions, workflow Globals, Test mode, and schedule configuration.

The export leaves out account ownership, sync metadata, run history, execution results, saved State, active schedules, and runtime deployments. Saved credentials and device-specific bindings are not portable credentials for the reader.

Review before sharing#

Look through literal parameters, Globals, HTTP headers, URLs, request bodies, and code. These can contain private values that a person typed directly. Removing credential bindings does not prove that every other value is safe to publish.

Replace private values with configuration the reader will supply and document each prerequisite. Reopen the downloaded file or attachment preview to confirm the reusable definition is complete.

Import a copy#

In the workflow library, choose Import workflow and select a file, or drag a workflow file into the import area. Imports validate the file and graph, including supported node types.

A valid import creates a new, inactive workflow. It does not overwrite the original or begin execution. Choose your own required connections and wallets, inspect any configurable inputs, check Test mode and the runtime, then run once.

If a node is unsupported, read the validation message and use a current compatible app. Unsupported nodes are not silently removed.

Copies are independent#

Changes to the original workflow do not update an exported file. Replacing an article attachment does not update a copy that someone already imported. Download and import a new copy when you want a newer snapshot.

Next: publish an article.