Manage workflows

A EI-Flow workflow, once published, is like a program that, when run, receives JSON input, typically—but not necessarily!—processes it and always produces a JSON output.

One of the simplest and most used workflow can analyze text written in a given language using a predictive model: the input is a JSON containing the text to analyze and the output is a JSON containing the result of the analysis.
EI-Flow, however, allows building much more complex workflows, as mentioned in the introduction to this manual, and nothing prevents you from building workflows that do not use predictive models at all, if you deem it useful.

EI-Flow users can build as many workflows as they need using the graphical editor, but until a workflow is published in a runtime, it is only a blueprint, like the source code of a program.
With publication, the workflow becomes like a program loaded in the memory of a computer and ready to run on demand, that is, when an input to be processed is submitted to it via API or test UI.
When a workflow is not needed anymore, it can be unpublished, so freeing computing resources for other programs.

Learn more about the inner workings of workflows in the article dedicated to the topic.

Workflows can be public or project-based.
Public workflows are visible to everyone, while project workflows are visible only to the project owner and any users with whom the project has been shared.
The ability to manage public workflows depends on the user's role, while project workflows, aside from the project owner who has full powers on them, depend on the permissions with which the project was shared.
The main page for viewing and managing public workflows is Workflows, while project workflows are viewed and managed in the Workflows tab of the project workspace.

The following articles describe all the workflow management procedures.