Concepts
What a workflow is, how a graph is wired, and the JSON the editor and your backend exchange.
The vocabulary the rest of this documentation assumes, and the data model both halves of FlowDrop agree on. None of it is specific to a backend.
What is a workflow?
The mental model, and the contract between the editor and your backend.
Thinking in graphs
Grow a familiar shell command into a workflow graph.
Architecture overview
How the modules, components, stores and services fit together.
Port system
Ports, data types, compatibility rules and gateway branches.
The data model
A workflow is JSON. These pages are the format, field by field.
- Workflow structure — the top-level document
- Node structure — nodes, metadata and config values
- Edge structure — connections and handle IDs
- Workflow interface — a workflow's public inputs and outputs
- Glossary — every term, defined once
The normative rules live in the FlowDrop Workflow Specification, which is a sibling of this site rather than a section of it.