Import/export

Any workflow can be exported to a single JSON file and imported back - to back it up, move it between accounts or instances, or hand it to someone else.

Export

From the editor menu, Export downloads a <workflow-name>.pipory.json file containing:

• the workflow's name,
• every node (id, type, name, canvas position, and its config),
• every edge (source, target, and which handles they connect),
• a format marker and version number.

Exporting always reads the latest persisted state from the server (never a stale client-side copy), so the file always matches what's actually saved.

Credentials are never included. Each node's credentialId is stripped and replaced with a credentialType marker naming which kind of credential the node needs - so the exported file is safe to commit, share, or hand off without leaking a secret's id or value.

Import

Import reads a .json file and recreates it as a new workflow (or, when re-importing into an existing one, replaces its graph). The importer validates:

• the format marker and version, rejecting arbitrary or incompatible JSON early with a clear error, and
• every node's type against the registered node catalog, rejecting unknown or tampered node types.

Nodes that had a credential on export come back with the credentialType placeholder intact - open each one and pick (or create) a matching credential to reconnect it. See Credentials.

Round-tripping

Export a workflow, delete it, import the file back, and it runs identically (once credentials are reconnected) - the same round trip the Templates gallery uses internally to instantiate a template as a fresh workflow. See Templates.

Related

• Templates - the same document shape, pre-built and credential-free by design.
• Credentials - reconnecting credentials after an import.