Overview

Backends that speak the FlowDrop API — ready-made servers you can run instead of building your own.

FlowDrop is a frontend editor: it needs a backend that serves node definitions, stores workflows, and runs executions (see the frontend–backend contract). You can build that backend yourself — the Backend Implementation guide covers the exact REST endpoints — or you can run one of the ready-made server implementations documented here.

Just need a backend to build a client against? Run the example Express server — the recommended backend for local development.

Available implementations

Drupal

A full FlowDrop backend as a Drupal module: node definitions, workflow storage, execution, triggers, and authentication.

flowdrop-rs

A standalone Rust server implementation of the FlowDrop API. Planned — documentation to follow.

Build your own instead

If none of these fit, any backend that implements the FlowDrop REST contract works. Start here:

• Backend Implementation — the endpoints FlowDrop calls
• Authentication Patterns — wiring an AuthProvider
• API Reference — the full OpenAPI specification