Skip to main content
The Drupal server implementation is a complete FlowDrop backend packaged as a Drupal module. It serves node definitions, stores workflows as configuration entities, runs executions, and authenticates requests — everything the frontend–backend contract expects, integrated with the entities, users, and content you already have.

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:

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.

Get started

The Drupal docs site is the source of truth for setup and reference: