Project on Drupal.org
The official module page — releases, downloads, and the issue queue.
Full Drupal documentation
Installation, node reference, execution modes, triggers, and developer
guides on the canonical Drupal docs site.
How it maps to FlowDrop
Everything you learned in Concepts carries over — the Drupal module is the backend that gives those workflows meaning:| FlowDrop concept | In the Drupal server |
|---|---|
Node definitions (GET /nodes) | 25+ built-in node processors (data, control flow, entity operations, HTTP, AI), defined as PHP plugins |
| Workflow storage | Workflows are Drupal configuration entities — exportable to YAML, versionable in git, deployable with drush cex/cim |
| Execution | Runs every workflow the editor produces, recording results per node |
| Authentication | Standard Drupal permissions and session/token auth behind an AuthProvider |
What it adds on top
Beyond the core contract, the Drupal server brings backend-side capabilities the editor surfaces but does not itself implement:- Execution modes — Synchronous (in-request), Asynchronous (queue-based background), and StateGraph (checkpointed, resumable).
- Triggers — start workflows automatically on entity changes, user events, or cron.
- Human-in-the-loop — pause execution for confirmations, choices, or free-text input.
- Pipelines and jobs — every run produces a pipeline record with one job per node for monitoring and debugging.
- Node Types — pre-set node variants site builders configure without code.