When workflows stay simple, configuration is enough. But modern Drupal systems deal with orchestration, external services, and long-running processes. At that point, rules become invisible logic. FlowDrop rethinks workflows as executable systems, making orchestration explicit, inspectable, and built for modern Drupal architectures.
Basic Site-building capabilities with Drupal is minimum requirement. If you can write code and create a simple Drupal Plugin, then you are awesome and can make the most out of the session.
When we talk about workflows in Drupal, most of us immediately think in terms of rules, conditions, and configuration. We wire things together, save the config, and hope the execution path matches what we had in mind.
And most of the time, it works.
Until it doesn’t.
At some point, workflows stop being simple automation and start becoming orchestration. They involve external services, asynchronous steps, retries, state, long-running processes, and decisions that evolve over time. At that point, configuration-driven rules begin to hide more than they reveal.
What usually breaks first is not the code. It is our understanding of what is actually happening.
FlowDrop started from that exact frustration. I was not trying to build a new workflow tool. I was trying to understand and reason about complex execution logic in Drupal without constantly reverse-engineering configuration, logs, and side effects.
In this session, I want to show you what happens when we treat workflows as first-class, executable systems instead of implicit configuration. I will walk you through how FlowDrop rethinks workflow modeling and orchestration in modern Drupal, what architectural decisions made that possible, and what this approach unlocks for complex, AI-ready, service-oriented systems.
This is not about replacing everything you already use. It is about expanding how we think about workflows in Drupal, and what becomes possible when execution logic is explicit, inspectable, and designed for change.
After this session, attendees will be able to:
- Understand the architectural differences between traditional Drupal workflow systems and modern orchestration engines
- Model workflows and execution state using Drupal entities in a scalable and debuggable way
- Use Drupal’s plugin system to build extensible, node-based execution logic
- Expose complex orchestration behavior through a usable visual UI without excessive custom code
- Evaluate when Drupal is a good fit for workflow and orchestration problems and when it is not
- Apply lessons learned from FlowDrop to their own custom modules and platforms
