ECA Crosses 20,000 Reported Drupal Site Installations

Adoption milestone shifts attention from workflow growth to maintainer responsibility
Discover Drupal graphic titled “ECA Crosses 20,000 Reported Drupal Site Installations” with text reading “Jürgen Haas says the milestone brings new responsibility around commits, APIs and compatibility promises.” The ECA logo appears beside an illustrated portrait labeled “Jürgen Haas” and the LakeDrops logo.

Automation module ECA: Event - Condition - Action has crossed 20,000 reported Drupal site installations, according to a LinkedIn post by Jürgen Haas, co-founder and Drupal specialist at LakeDrops. Drupal.org currently lists 20,056 sites reporting use of the module.

The milestone gives the Drupal automation project a measurable adoption marker. ECA lets users model workflows, business rules, approvals, content behaviour, integrations, and AI-powered processes without writing custom code. The project builds on Drupal events, actions, queues, workflows, forms, and APIs, with models stored as configuration for import, export, and deployment.

Drupal.org’s usage statistics page explains that weekly figures count sites reporting use of each project version for the relevant week. The latest visible weekly table entry lists 20,056 reporting sites for the week starting 28 June 2026. The count may differ from earlier weekly entries because Drupal.org usage statistics depend on sites that report project version data.

In a written response to The DropTimes, Jürgen said the number changes how he views maintenance responsibility for the project.

ECA isn't simple. It's not something people stumble into. So 20,000 sites means 20,000 deliberate choices, which also means 20,000 expectations I'm now responsible for. That changes how I think about every commit, every API decision, every compatibility promise.

–Jürgen Haas, co-founder and Drupal specialist, LakeDrops

Jürgen’s response frames the milestone as a maintenance obligation rather than a promotional count. For Drupal site builders, the milestone points to sustained interest in configuration-based automation that can reduce custom glue code while remaining inside Drupal’s extension model.

For readers new to the project, ECA stands for Event - Condition - Action. In practice, it allows a Drupal site to respond when something happens, check whether defined conditions are met, and then run an action. That pattern can support tasks such as sending notifications, changing content values, assigning roles, triggering workflows, or connecting with other services without writing a custom module for each process.

Reference: LinkedIn (6 July 2026)

Disclosure: This content is produced with the assistance of AI.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.

Related Organizations

Upcoming Events