rafal-fryc lets workflows travel between Mike instances

A small file format turns a custom workflow into something you can hand to another team without sharing an account.

workflowintegration

rafal-fryc has added a download-and-upload path for workflows: each workflow gets a download button that packages it into a small JSON file, and the workflows page gets an upload button that reads the file back and creates the workflow under whoever is importing it. The envelope is deliberately narrow - title, type, practice area, prompt, and (for tabular workflows) the column configuration - with a version tag and a strict parser that complains loudly when handed the wrong kind of file.

Nothing changes on the server. Imported workflows are just normal workflows owned by the importer, and the existing email-based share flow is left alone. This is an additive way to move a workflow across teams, environments, or organisations where the workflow itself is the valuable artefact but the accounts hosting it aren't shared.

So what Worth a look for legal-ops leads who've built up custom workflows in one Mike instance and want a clean way to seed another - a client deployment, a sister firm, a staging environment - without setting up shared logins.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?