Drupal ECA Adds In-Context Automation Templates for Form Customisation

Workflow automation in Drupal’s ECA ecosystem is moving toward contextual configuration interfaces with a new in-context customisation system designed to reduce the learning barrier for non-technical users.

The feature was outlined by Jürgen Haas in a blog post published on 27 May 2026. The update adds contextual “lightning bolt” actions beside compatible Drupal form fields, allowing users to apply predefined automation templates directly from editing interfaces instead of navigating separate configuration screens or working inside the full Workflow Modeler.

The change expands the Drupal ECA project’s ongoing work around low-code workflow configuration. According to Haas, the team identified interface complexity rather than technical capability as a primary obstacle for many site builders and content administrators. The new interface attempts to abstract ECA’s event-driven architecture behind task-oriented actions embedded within existing editing workflows.

Under the new system, users editing forms can open contextual menus containing automation templates tied to individual fields. Examples described in the post include changing field labels based on user role, setting default values, adding validation rules, hiding fields conditionally, and configuring notification workflows. Users configure only the exposed parameters, while the system automatically generates the underlying ECA model.

The implementation relies on three components: reusable templates, contextual awareness, and token resolution. Templates are standard ECA models flagged for contextual reuse. The system determines relevance based on the editing context, such as form or node interfaces, while token handling converts internal placeholders into selectable configuration values exposed through simplified menus.

Haas described the interface as both an onboarding layer for non-technical users and a rapid starting point for experienced ECA users. Models created through the contextual interface can later be opened inside the Workflow Modeler for additional modification. The post notes that many advanced users already use templates as scaffolding for larger automation workflows.

Current support focuses on form-related workflows through the eca_form submodule. Planned roadmap items mentioned in the post include login and logout scenarios, redirect management, content rendering customisation, Commerce checkout workflows, and Views-related display modifications.

The article also outlined a broader template-library strategy aimed at agencies and large organisations. Haas suggested agencies could maintain reusable collections of automation templates for recurring client requirements such as registration handling, publication notifications, and form submission workflows. The approach positions templates as reusable operational assets rather than isolated site-level configuration.

The interface was developed with UX research support from Emma Horrell and Mark Dodgson. According to Haas, usability testing focused on whether first-time users could successfully apply automation templates without prior ECA knowledge or documentation.

The original post, titled “For Everyone: In-Context Customization Without the Learning Curve,” also describes a longer-term vision for community-contributed template libraries and marketplace-style distribution models for reusable ECA workflow patterns.