05 Connectivity Orchestration with Workflows
Up to this point, connectivity has been described as a sequential connector chain: one (datapoint) is called, its output is passed forward, and the connector ends when the last datapoint returns.
This approach is intentionally simple and works well for linear interactions, but it becomes limiting as soon as a connectivity pattern requires branching or iteration behavior.
This section introduces Connectivity Orchestration with Workflows. Instead of embedding orchestration logic in a single connector sequence, we model the connectivity as an explicit workflow executed by a workflow engine that OLIVE provides.
Workflows provide a structured way to coordinate multiple datapoint calls, manage intermediate values, and control execution with constructs such as do (sequential steps), set (workflow variables), switch (conditional routing), and for (iteration).
Each workflow remains callable like any other connectable element via a standard HTTP endpoint through the Data-Orchestrator.
The following chapters define the JSON-based workflow format used in OLIVE, highlight key differences to the full Open Workflow Specification, and provide practical examples ranging from minimal single-call workflows to multi-step orchestrations with conditional model selection.
Resources
Here is a collection of resources, providing more information on the workflow engine and examples.
| Description | Link |
|---|---|
| Open Workflow Specification Doc | https://open-workflow-specification.org/](https://open-workflow-specification.org/) |
| Open Workflow Specification DSL Specifications - Github | https://github.com/open-workflow-specification/specification/blob/main/dsl.md |
| Open Workflow Specification DSL Examples - Github | https://github.com/open-workflow-specification/specification/tree/main/examples |
| Temporal Platform Documentation | https://docs.temporal.io/ |
Subpages
Use the following pages to navigate to the relevant topics: