Drupal is a registered trademark of Dries Buytaert
Protected Pages 3.0.0 Major update available for module protected_pages (3.0.0). Commerce Core 3.3.8 Minor update available for module commerce (3.3.8). Search API HTML Element Filter 1.0.7 Minor update available for module search_api_html_element_filter (1.0.7). Layout Builder Reorder 2.0.1 Minor update available for module layout_builder_reorder (2.0.1). Ban 1.1.0 Minor update available for module ban (1.1.0). Field Formatter Range 2.0.0 Major update available for module field_formatter_range (2.0.0). Field Formatter Range 8.x-1.8 Minor update available for module field_formatter_range (8.x-1.8). Varbase Media Header 9.2.1 Minor update available for module varbase_media_header (9.2.1). Search API Solr 4.3.11 Module search_api_solr updated after 14 months of inactivity (4.3.11). Provus Mega Menu Module provus_mega_menu crossed 1,000 active installs.

This project provides a basic user interface for building simple event-driven automation workflows within Drupal. It allows you to define events and then chain actions and conditions to them.

A user interface for ECA solely built on top of Drupal core and ECA core.

Important notes

  1. Please do not use this modeler unless you have no other option. Better modelers are available and can be found on the project page of ECA. Once there is a better modeler available that is usable for screen readers, support of this module will considered to be dropped entirely.
  2. Please do not see this as a Rules UI equivalent. This is a completely different mechanism because ECA is not an equivalent to Rules (see usage section).

This is a very basic low-level modeler tool

Important note: This modeler may be sufficient for creating very simple processes. But usually with ECA, complex processes will be created, where this modeler falls short. In general, using a more powerful modeler such as BPMN.io is recommended to be used instead of this one.

The Classic modeler directly exposes the structure of an ECA configuration, and does not add its own structures on top of it. Therefore this solution can be seen as a "low-level" modeling tool, that may fit well for creating simple execution chains. This makes it also suitable as a fallback, just in case something is wrong with a more powerful modeling tool.

How to use

Have a look at the README regards how to install it.

Once installed, you can create a new "classic" model at /admin/config/workflow/eca/add/core.

  1. In that model form, you first need to create an event.
  2. Then you can create an action, and optionally a condition.
  3. Finally, you need to connect the action (and condition) as a successor to the event, by navigating back to the created event, and add the successor at the bottom of the event configuration form. You must click on the save button in order to persist your configuration changes.

Connecting the components between each other is the main key to define the execution chain with ECA. When you create more actions that need to be executed after a certain event or action, don't forget to add it as successor.

Activity

Total releases
3
First release
Sep 2025
Latest release
9 months ago
Releases (12 mo)
3 ▲ from 0
Maintenance
Slowing

Release Timeline

Releases

Version Type Release date
1.0.13 Stable Oct 10, 2025
1.0.12 Stable Oct 4, 2025
1.0.11 Stable Sep 28, 2025