Drupal Releases Modeler API 1.0.0, Paving Way for Unified Automation and UI Flexibility
Drupal officially released Modeler API 1.0.0 this week, establishing a long-awaited orchestration layer that separates complex configuration logic from user interface concerns. Announced by Jürgen Haas, the release lands alongside stable versions of ECA 3.0.0 and BPMN.iO 3.0.0, with integrations for AI Agents, the AI module, and Drupal MCP expected soon.
The Modeler API allows config-heavy modules—like ECA, AI tools, or migration systems—to connect with interchangeable UI components such as BPMN.iO, ReactFlow, or future modelers. Haas said the goal is full decoupling: developers can now build or swap UIs without impacting logic, while users can choose familiar interfaces across use cases.
This decoupling resolves long-standing limitations in earlier integrations. Previously, ECA and BPMN.iO shared UI logic, limiting flexibility and reuse. Now, Modeler API enables generic routing, permissions, menu integration, logging, and UI theming, providing a reusable foundation across modules.
The release is also a major win for maintainability. Developers can focus on either backend logic or frontend interaction—no longer both—while end-users benefit from consistency. For example, the same interface could soon support workflows, AI agents, migrations, or even Views and content modeling, reducing the need to learn multiple UIs.
Under the hood, Modeler API manages diagram rendering, theme selection, and raw data storage—whether embedded in the main config entity, saved separately, or not stored at all. Storage mode affects whether layout is retained or rebuilt. Haas encouraged testers to explore all modes during the feedback phase.
ECA 3.0.0 remains functionally stable at its core, but its UI has been overhauled to use Modeler API. This change shrinks boilerplate code, maintains backward compatibility, and allows YAML-defined ECA models to be callable by AI agents through a new “Tools” event system—available via a development submodule.
BPMN.iO 3.0.0 has been re-engineered to feel like a native Drupal experience. Gone is the external JavaScript property panel. Instead, BPMN now uses Drupal’s Form API in an off-canvas UI, includes canvas-based widgets for layout and navigation, and supports color coding, annotations, and multi-agent export. The module also leverages Drupal's new Icon API for added interactivity.
Additional improvements include schema validation for ECA plugin configuration, translatable user-facing values, and support for “Field Widget Actions”—a feature enabling AI-generated content suggestions inside Drupal forms.
Haas described the release as a turning point for Drupal. By abstracting configuration UIs and centralizing shared infrastructure, the Modeler API not only simplifies module development but also positions Drupal as a more unified platform for visual configuration, automation, and AI-driven tools.


